API Rate Limits and Best Practices

Understanding Our API Rate Limits

To ensure platform stability and fair usage for all customers, our API has rate limits. This article explains the limits and how to work with them effectively.

Default Rate Limits

Our default rate limit is 200 requests per minute per API key. This is calculated on a rolling basis.

How to Handle Rate Limiting

If you exceed the limit, you will receive an HTTP 429 Too Many Requests response. Your application should handle this gracefully by:

1. Checking the response headers. We include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers to help you track your usage.
2. Implementing a backoff strategy. When you receive a 429 error, pause requests for a short period before retrying. An exponential backoff strategy is recommended.

Best Practices

• Cache responses when possible to avoid requesting the same data repeatedly.
• Use bulk endpoints if available for your use case.
• Optimize your code to only make necessary API calls.