Rate Limits
| Limit Type | Value |
|---|---|
| Per minute | 100 requests |
| Per hour | 1,000 requests |
429 response error code.
Response Headers
The response headers describe your current rate limit status following every request:| Header name | Description |
|---|---|
X-RateLimit-Limit | Maximum number of requests allowed within a window. |
X-RateLimit-Remaining | How many requests you have left within the current window. |
X-RateLimit-Reset | Unix timestamp when the rate limit window resets. |
Retry-After | How many seconds you should wait before making a follow-up request (only included when rate limited). |
Handling Rate Limits
When you hit the rate limit, the API returns a429 Too Many Requests response:
Best Practices
Implement exponential backoff
Implement exponential backoff
When you receive a
429 response, wait before retrying. Start with a short delay and double it with each subsequent retry. This prevents overwhelming the API during high-traffic periods.Use a request queue
Use a request queue
Implement a queue mechanism to control the rate at which requests are sent. This ensures you stay within limits even during burst operations.
Monitor rate limit headers
Monitor rate limit headers
Check the
X-RateLimit-Remaining header to proactively slow down requests before hitting the limit.Cache responses when possible
Cache responses when possible
For data that doesn’t change frequently, cache API responses locally to reduce the number of requests needed.

