Requests to API v4 are rate-limited by access token. This means that after a certain number of requests using the same token in a given time period, the API will return a
429 Too Many Requests response.
All responses from the Clio API will include three headers:
X-RateLimit-Limit: the maximum number of allowed requests in a 60 second window.
X-RateLimit-Remaining: the number of remaining requests in the current 60 second window.
X-RateLimit-Reset: A unix timestamp indicating when the current window ends; after this timestamp, the rate limit resets to the value in
If the limit is exceeded, a
Retry-After header will be supplied in the
429 response indicating the number of seconds to wait until the request can be tried again.
Default Rate Limits
Clio's API has a default rate limit of 50 requests per minute during peak usage hours. Rate limits are increased during off-peak hours; the amount that they increase may differ per region.
Rate limits may change without notice. Your application should use the
X-RateLimit-* headers as described above to determine the exact rate limits at the time your request is made.
Peak hours are as follows:
- US/CA Regions: 04:00-19:00 Pacific Time, Monday-Friday
- EU Region: 07:00-22:00 GMT, Monday-Friday
- AU Region: 06:00-21:00 AET, Monday-Friday
Per-Endpoint Rate Limits
Certain endpoints may have different rate limits than the default values, which will be documented in the API Reference section for that endpoint.
Custom Rate Limits
We do not support custom rate limit increases for applications at this time.