How our limits work
- Each application has a default limit of 200 requests per minute.
- If you exceed this limit, the API will return a 429 Too Many Requests error.
- The
Retry-Afterheader in the response indicates the numbers of seconds you should wait until you can safely retry your request.
Handling rate limit errors
If your application exceeds the allowed request rate, follow these best practices:1
Check for 429 Too Many Requests Response
When you receive a
429 error, inspect the response headers for the Retry-After value, which tells you how many seconds to wait before retrying.2
Implement Exponential Backoff
Instead of retrying immediately, use an exponential backoff strategy to reduce the risk of further rate limit violations.
3
Optimize API Usage
- Reduce redundant or unnecessary API calls by caching frequently requested data
- Use webhooks instead of polling to get real-time updates efficiently