Rate Limiting
The API uses in-memory rate limiting keyed by API key ID to protect service quality.
Tiers
| Tier | Limit | Window |
|---|
| Standard | 100 requests | 1 minute |
| Elevated | 500 requests | 1 minute |
Your rate limit tier is determined by your subscription plan.
Every API response (including 429 errors) includes rate limit headers:
| Header | Description |
|---|
X-RateLimit-Limit | Maximum requests allowed per window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp (seconds) when the window resets |
Handling rate limits
When you exceed the limit, the API returns a 429 Too Many Requests response. Use the X-RateLimit-Reset header to determine when to retry.
To avoid hitting rate limits, add small delays between requests when iterating through paginated results, and cache responses where possible.