Rate limits
Each API Key has these limits.
| Requests | Rate | Burst |
|---|---|---|
| Most routes | 5 a second | 10 |
| A list over a time window: Calls, Data Sessions | 1 a second | 2 |
| A Recording | 2 a second | 5 |
A key can make 500 requests a day.
The rate lets you read a lot quickly: all your Users, Hunt Groups and IVRs, then the Calls of a day. The day limit stops polling. A webhook service that replaces polling is in work. Contact support for more about it.
When you reach a limit
Section titled “When you reach a limit”- Too many requests in a short time answer
429with therate-limitedproblem. Wait, then send the request again. Wait longer after each429. - A key that has used its day answers
429with thequota-exceededproblem until the next day (UTC).
Read less, less often
Section titled “Read less, less often”A list over a time window costs the most. Read a window once and keep the result. Do not read the same window again to look for changes: events are coming for that.
- A Leg has
recorded. Get the Recording of a Leg only when it istrue. - Data Sessions are readings of about one hour. A read more often than each hour gives nothing new.