Rate Limits
API access rate limits are applied on a per-key basis. Limits differ between environments.
Limits by Environment
Rate Limit Headers
Every API response includes headers to help you track your consumption:
Exceeding the Limit
If you exceed the rate limit, the API returns a 429 Too Many Requests response. Wait until the X-RateLimit-Reset time before making additional requests.
Implement exponential backoff in your integration to gracefully handle rate limit responses. Avoid retrying immediately after receiving a 429 status code.
Best Practices
- Cache responses where possible to reduce the number of API calls.
- Use pagination with reasonable page sizes instead of requesting all records at once.
- Monitor rate limit headers in your responses to proactively adjust request frequency.
- Implement retry logic with exponential backoff for
429responses.
