Skip to content

Go to production

Rate limits and volume

The per-key limits on a standard partner key, the headers that report them, and how to ask for more.

On this page

Partner traffic is a lead post, not a chatty per-attempt API. This is the same /v1 we run for agencies, and posting a lead returns after enrollment, typically well under a second. Dialing is asynchronous.

Limits on a standard partner key

BucketLimit
POST /leads120 per minute
POST /leads/batch20 per minute, 500 leads each
POST /leads/ping300 per minute
GET status, calls and artifacts300 per minute
POST /leads/{id}/pause and /resume60 per minute
Anything else a key may reach100 per minute

Ping is optional. Direct post is the default path, and ping is for publishers who already have ping and post.

Limits are counted per API key, and each bucket is independent: posting does not use up your read quota. They are enforced per API instance, in memory, so these numbers are the guaranteed floor. The MediaAlpha native route has no bucket of its own. It falls in the shared default bucket of 100 requests per minute, separate from the POST /leads bucket: see MediaAlpha native post.

Read the headers

Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (unix seconds) and X-Request-ID. Quote the request id when you contact us.

curl -i "https://api.entrovox.com/v1/leads?external_id=px-88421" \
  -H "Authorization: ApiKey $ENTROVOX_KEY"

Over a limit you get 429 RATE_LIMIT_EXCEEDED with Retry-After. Wait that long and retry with the same Idempotency-Key. See Safe retries and idempotency.

Concurrency and size

Your campaign is provisioned with its own branded caller IDs and dial concurrency. We size this with you, for example 500 leads per day or 50 thousand attempts per month.

Need more

We raise a key's ceiling per program, with no API version change and no rewrite of your integration. Ask the Entrovox contact who provisioned you.

Next steps

Plan your first volume send with the go-live checklist.

Updated Nov 7, 2026