Rate limiting is considered per api_token. API allows performing requests according to the tier.
Each of the three tiers offers different rate limiting:
|Startup||Feature not available|
|Business||60 requests per minute per api_token|
|Enterprise & Trial||100 requests per minute per api_token|
If you are exhausting your limits, you can either restructure the architecture of your integrations or upgrade to a higher tier.
Each API response is enriched with the following headers:
- X-RateLimit-Limit: The maximum number of requests that can be made by the current api_token
- X-RateLimit-Remaining: The remaining number of calls within the time window
- X-RateLimit-Reset: the number of seconds before the limit resets
Once you exhaust the request limit, any concurrent API call will return an error response HTTP code 429. You can refer back to X-RateLimit-Remaining header which will inform you when the limit will reset.
By default, only X-RateLimit-Remaining header will be sent with each response. Once the rate limit is reached, X-RateLimit-Limit and X-RateLimit-Reset headers will be sent with the response.
Was this article helpful?
Thank you for your feedback! Our team will get back to you
How can we improve this article?
Character limit : 500