To ensure fair use and consistent performance, our API enforces rate limits at both minute-level and monthly intervals.
π Per-Minute Limit
In addition to monthly usage limits, all clients are subject to a secondary rate limit that caps the number of requests they can make per minute.
The exact per-minute limit depends on your subscription tier and is listed on the pricing page alongside your monthly quota.
If you exceed your tierβs per-minute allowance, the API will return a 429 Too Many Requests response until the rate limit window resets.
π
Monthly Quotas
Monthly request caps are based on your subscription plan. The API includes rate limit headers in each response to help you track usage:
Header | Description |
---|---|
ratelimit-limit | The maximum number of requests allowed for the current month. |
ratelimit-remaining | The number of requests left in the current monthly window. |
ratelimit-reset | Seconds until the monthly rate limit resets. |
Example headers:
ratelimit-limit: 100
ratelimit-remaining: 85
ratelimit-reset: 389503
Use these headers to proactively manage usage and avoid service interruptions.
If you anticipate exceeding your monthly limit, please contact us to discuss plan upgrades or custom limits.
π§ Best Practices
- Distribute requests evenly over time rather than in bursts.
- Implement retries with exponential backoff for 429 responses.
- Monitor your usage using the provided rate limit headers.
π€ How To Handle Rate Limiting
Want to see an example of how to handle the rate limiting?
π Check out our recipe to ss to:
- Make requests to the API using
axios
- Read rate limit headers like
ratelimit-limit
,ratelimit-remaining
, andratelimit-reset
- Handle
429 Too Many Requests
responses with retry logic
This is a great starting point to stay within usage quotas.