Rate Limits
- Default Limit: 100 requests per minute per IP address
- Window: 60 seconds (1 minute)
Rate Limit Headers
Every API response includes rate limit information in the headers:Header Descriptions
- X-RateLimit-Limit: Maximum number of requests allowed in the window
- X-RateLimit-Remaining: Number of requests remaining in the current window
- X-RateLimit-Reset: ISO 8601 timestamp when the rate limit window resets
Rate Limit Exceeded
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
429 Too Many Requests
Handling Rate Limits
Exponential Backoff
Implement exponential backoff when you receive a 429 response:Respect Rate Limit Headers
Check theX-RateLimit-Remaining header and adjust your request rate:
Caching
Cache responses to reduce API calls:Custom Rate Limits
Contact support if you need custom rate limits for your use case. Enterprise plans may include:- Higher rate limits
- Burst capacity
- Custom windows
- Priority queuing
Best Practices
Monitor rate limit headers
Monitor rate limit headers
Track rate limit headers in your application to proactively manage your request rate.
Implement caching
Implement caching
Cache responses to reduce API calls and stay within rate limits.
Use batch requests
Use batch requests
When possible, use batch requests or combine multiple queries into a single request.
Implement exponential backoff
Implement exponential backoff
Use exponential backoff for retries to avoid overwhelming the API.
Respect rate limits
Respect rate limits
Always respect rate limits to avoid service disruption and ensure fair usage.
