ZDX API Rate Limits
In Zscaler Digital Experience (ZDX) API, every endpoint is called from a specific IP address and the rate limit is dependent on the Tier Level.
| Tier Level | Number of Licenses | Requests/second | Requests/minute | Requests/hour | Requests/day |
|---|---|---|---|---|---|
| 1 | 5,000 | 5 | 30 | 1,000 | 10,000 |
| 2 | 20,000 | 5 | 60 | 3,000 | 15,000 |
| 3 | 100,000 | 5 | 120 | 6,000 | 30,000 |
| 4 | More than 100,000 | 5 | 180 | 9,000 | 60,000 |
note
All rate limits start as soon as the first call is executed. Calls can occur more than once per second, but no more than the limits for each operation type. Clients who are subject to rate limiting need to back off exponentially in order to proceed further.
ZDX sends Rate Limit headers to provide information about the current status of rate limits. Users can use the Rate Limit headers to plan ahead for their API integration to prevent reaching the rate limit and receiving an HTTP 429 response code.
The Rate Limit headers are:
x-ratelimit-limit: The rate limit ceiling that is applicable for the current API request.x-ratelimit-remaining: The number of API requests remaining for the current rate limit window.x-ratelimit-reset: The time (in seconds) remaining in the current window after which the rate limit resets.