This page contains information about the rate limit we enforce and explains why it's necessary.
To ensure optimal performance and reliability of our API, we enforce an API rate limit of 1,000 requests per minute. The following information explains what this limit means, why it’s important, and how you can work within it to make the most of our API services.
What is an API Rate Limit?
An API rate limit is a restriction placed on the number of API calls a client can make to a server within a specific time period. It prevents abuse, ensures fair usage, and maintains the overall performance and stability of the API service.
Why is There a Rate Limit?
With thousands of successful requests made to our API every day, we apply rate limits to ensure our service remains:
Stable and responsive for all users
Equitable, preventing any single application from utilising all resources
Secure, protecting against unintended abuse or traffic spikes
If the limits are exceeded, the API will respond with a 429 - Too Many Requests error.
How to Work Within the Rate Limit
Here are some best practices to ensure you stay within the rate limit whilst efficiently utilising our API:
Optimise your queries: Ensure your API requests are as efficient as possible. Retrieve only the data you need by using appropriate filters and parameters.
Implement caching: Cache API responses where appropriate to reduce the need for repetitive calls. This is especially useful for data that doesn’t change frequently.
Rate limiting logic: Implement client-side logic to monitor and respect the limit. If your application is approaching the threshold, it can queue requests or implement exponential backoff to prevent exceeding the limit.
Monitor usage: Regularly monitor your API usage to ensure compliance with the rate limit.
If You Exceed the Rate Limit
There are several approaches you can take if you exceed the rate limit:
Implement Exponential Backoff: Wait an exponentially increasing amount of time with each consecutive failure due to a
429error response.Fixed Delay: Wait for a fixed amount of time after receiving a
429response before making the next request. This is a simple approach but not as efficient as others.Adaptive Rate Limiting: Adjust the request rate dynamically based on the frequency of
429responses received. If you’re consistently receiving429errors, we recommend reducing the request rate more aggressively.Circuit Breaker Pattern: Implement a pattern where you stop sending requests altogether for a specified amount of time after hitting the rate limit.
Want or Need a Higher Limit?
If you anticipate higher volume usage than the standard limits allow (for example, for high-traffic integrations, enterprise use, or batch processing), please contact our Support team.
Please include the following so we can appropriately assess your request: the expected or required request volume, the specific endpoints you will be using, and the business justification.
Conclusion
By adhering to the recommended rate limit of 1,000 requests per minute, you can ensure smooth and efficient use of our API services. Implementing best practices and handling rate limits gracefully will help maintain the performance and reliability of your applications while respecting the shared resources of the API.