API rate limits are separate from call capacity. CPS (calls per second) and concurrency (simultaneous active calls) limit how many calls you can run. See Why am I getting a 429 error? for those limits.
Limits at a glance
Voice API request quota
Each parent account gets a request quota for a time window. Sub-accounts share their parent’s quota.- Make Call and Add Participant are not counted against this quota. CPS, concurrency and the error budget below govern those requests instead.
- The window restarts after each accepted request. If you keep sending requests at the limit, you stay limited. Pause for the full window to clear the counter.
- Need more? Accounts with higher call capacity get a larger quota automatically. Contact support for a custom quota.
429 Too Many Requests:
429 response
Error budget on Make Call
If too many Make Call or Add Participant requests fail with a4xx or 5xx error, Vobiz briefly blocks further requests of that type. This stops a misconfigured dialer from looping on failing calls.
429 response
4xx response in a loop: it won’t succeed and it uses up your error budget.
Signup, OTP and contact endpoints
Account signup, OTP requests and the contact form are limited per client IP over a one-hour window. When you exceed the limit, the response includes aRetry-After header with the number of seconds to wait:
429 response
How to handle a 429
- Honor
Retry-Afterwhen it is present. Wait at least that many seconds before you retry. - Otherwise, back off exponentially with jitter. Wait 1s, then 2s, 4s and so on, up to about 60s, with a random offset so parallel workers don’t retry together.
- Pace requests on your side. Use a queue or token bucket so your steady-state rate stays below your quota, instead of relying on 429s to slow you down.
- Log the
api_id. Include it when you contact support.
Retry with backoff
Related
- Error handling - error format and HTTP status codes
- Why am I getting a 429 error? - CPS and concurrency limits
- Best practices - building reliable integrations