On November 5, 2020, Zendesk will introduce new page-based volume rate limits on the following Support API endpoints.
Endpoint |
Requests per minute |
List Tickets GET /api/v2/tickets.json
|
50 req/min above page 500 |
List Tags GET /api/v2/tags.json
|
50 req/min above page 500 |
List Users GET /api/v2/users.json GET /api/v2/groups/{id}/users.json GET /api/v2/organizations/{id}/users.json
|
100 req/min above page 10,000 |
How do the changes affect you?
The new limits are set higher than current activity on these endpoints. We foresee no immediate breaking changes. Note that the limits may need to be adjusted if there is increased service-incident risk.
What happens if you exceed the limit?
If your account sees a volume spike on one of these endpoints that activates the new rate limit and that limit is exceeded, you will receive a 429 error response with a Retry-After header specifying how many seconds you should wait before retrying.
Why is Zendesk making the change?
We’re making this change because providing reliable service to our customers is more important than ever. Ensuring the continued performance and stability of our infrastructure requires us to effectively manage traffic on our network. Processing a high number of paginated ticket or user list requests can lead to heavy loads on our infrastructure. The limits protect against that by curtailing the rate at which requests are processed.
We envision setting the same kind of limits on other endpoints in the future and will notify you when we do.
Questions or need more help?
If you foresee challenges with this based on your specific account, please reach out to us and our team will respond as soon as possible.
Tip: If you want to collect large amounts of data on an ongoing basis, use the incremental export endpoint for the resource rather than a list endpoint. The incremental exports API provides near real-time data, and you can choose to pick data with time as the index. It gives you immense precision to pick the data that you need. The incremental exports API also supports cursor pagination that allows for faster response times
0 comments