Handling rate limits and errors in the Avox API
What a 429 means, how to read Retry-After, and how to use error codes to fix problems quickly.
Good API clients expect the occasional "not now". Here's how the Avox API tells you, and what to do.
Too many requests
If you send faster than your key allows, the API answers 429 with a Retry-After header: wait that many seconds, then try again. Some keys also have a daily allowance that resets at midnight UTC.
Errors you can act on
Every error response has the same shape: a stable code, a readable message, a docs_url that explains it, and a request_id you can quote to support.
A simple, sturdy client
- Retry with backoffWait a little longer after each failed try.
- Send an Idempotency-KeyRetries can never send a message twice.
- Log the request_idIt finds the exact request in API logs.
API messages don't use automation credits.
Thanks for reading
How did this land?
Was this helpful?
Try it yourself
What a 429 means, how to read Retry-After, and how to use error codes to fix problems quickly.