Menu

Rate limits and retries

The rate limit, client timeouts, what to retry and how to pace a backfill.

On this page

Rate limit

Each API key may make 120 requests per minute across all endpoints. Requests with a missing or invalid key are limited to 30 per minute per IP address. Over a limit, Chambr returns 429 rate_limited with a Retry-After header in seconds.

Daily volume

An account can send a very large number of new calls per day, well beyond normal use. Past it, POST /v1/calls returns 429 daily_limit_reached with a Retry-After header until midnight UTC. Resending a call you already sent (the same external_id) still works. Contact support if your real volume needs more.

Timeouts

Give POST /v1/calls a client timeout of at least 60 seconds. Finding the rep's speaker and classifying the call type can take 30 seconds; sending transcript.rep_speaker and call_type skips both. After a timeout, retry: the request is idempotent.

Retry rules

Response Do
429 rate_limited Wait Retry-After seconds, then retry
429 daily_limit_reached Stop sending new calls until Retry-After (midnight UTC); replays of calls already sent still work
503 inference_unavailable Wait Retry-After, or resend with transcript.rep_speaker
500 internal_error, network error, timeout Retry with exponential backoff, for example 2, 4, 8 and 16 seconds, then alert
Any other 4xx Do not retry unchanged; fix the request. See Errors

Backfills

Send one or two calls per second rather than all at once. Scoring takes longer during a large backfill.