Skip to main content
Rate limits protect the API from abuse and ensure fair usage for all users.

Limits by Plan

Limits are applied per API key using a sliding window algorithm.

Rate Limit Headers

Every response includes rate limit information:

Handling Rate Limits

When you exceed the limit, you’ll receive a 429 Too Many Requests response:
The response includes a Retry-After header indicating how long to wait:

Implementation Example

Best Practices

Check X-RateLimit-Remaining to proactively slow down before hitting limits.
Instead of retrying immediately, wait progressively longer between retries.
Instead of many small requests, consider batching operations.
For read operations, cache responses to reduce API calls.
Each key has its own rate limit, so separate keys for different services won’t interfere.

Need Higher Limits?

If you’re consistently hitting rate limits, consider upgrading your plan: Upgrade your plan →