Our API enforces rate limits to ensure system stability and prevent abuse. These limits control the number of requests that can be made within a given time frame.
General Limits
Each client can make up to 5,000 requests per hour. This limit is applied dynamically over a rolling 60-minute window.
If you exceed this limit, you will receive a 429 Too Many Requests response and must wait before sending additional requests.
Handling Rate Limit Responses
If your application surpasses the allowed request rate, the API will respond with:
- HTTP Status Code:
429 Too Many Requests - Retry-After Header: Specifies the number of seconds to wait before making another request.
It is essential to handle these responses properly to prevent disruptions in your integration.
Best Practices for Efficient API Usage
To ensure smooth operation within the rate limits, follow these recommendations:
- Optimize request frequency. Avoid unnecessary API calls and batch operations when possible.
- Respect the
Retry-Afterheader. If you receive a429 Too Many Requestsresponse, wait for the specified time before retrying. - Reduce excessive polling. Check the endpoint documentation for recommended update intervals instead of making frequent requests.
- Implement exponential backoff. If you hit the rate limit, increase the wait time progressively before attempting another request.