Rate Limits
API requests are rate-limited per API key based on your subscription tier. Limits are applied on a per-minute sliding window.
Tier-Based Limits
Rate limits vary by subscription tier:
| Plan | Requests / Minute | Daily Limit |
|---|---|---|
| Starter | 60 | 10,000 |
| Growth | 300 | 50,000 |
| Elite | 1,000 | 200,000 |
Rate Limit Headers
Every API response includes rate limit information in the response headers:
| Header | Description |
|---|---|
X-RateLimit-Limit |
Maximum requests allowed in the current window |
X-RateLimit-Remaining |
Remaining requests in the current window |
X-RateLimit-Reset |
Unix timestamp when the rate limit resets |
Example Response Headers
HTTP/1.1 200 OK X-RateLimit-Limit: 300 X-RateLimit-Remaining: 287 X-RateLimit-Reset: 1732780800
Exceeding the Limit
When you exceed the rate limit, you receive a 429 response:
Example 429 Response
429 Too Many Requests
{
"error": {
"code": "rate_limit_exceeded",
"message": "Too many requests. Please retry after 42 seconds.",
"retry_after": 42
}
}
Best Practices
- Implement exponential backoff when you receive 429 responses
- Cache responses locally when data does not change frequently
- Monitor X-RateLimit-Remaining headers to avoid hitting limits
- Batch related operations to reduce total request count