Rate Limits
Understand rate limiting and how to handle 429 responses.
Rate Limits
Rate limits protect the API from abuse and ensure fair usage. Limits are applied per API key on a per-minute sliding window.
Limits by Plan
| Plan | Requests/Minute | Requests/Month |
|---|---|---|
| Free | 10 | 500 |
| Starter | 60 | 10,000 |
| Pro | 300 | 100,000 |
| Business | 1,000 | 1,000,000 |
| Enterprise | Custom | Unlimited |
Response Headers
Every API response includes rate limit headers:
Rate limit headers
X-RateLimit-Limit: -amber-400">300
X-RateLimit-Remaining: -amber-400">297
X-RateLimit-Reset: -amber-400">1711900800Handling 429 Responses
When rate limited, the API returns a 429 status with a Retry-After header indicating how many seconds to wait.
429 Response
{
400">"error": 400">"rate_limit_exceeded",
400">"message": 400">"Too many requests. Please retry after 12 seconds.",
400">"retry_after": 12
}Best practice
Implement exponential backoff in your client. When you receive a 429, wait the number of seconds specified in Retry-After, then double the wait time on each subsequent retry.