Guide
Rate Limits
Per-tier daily request limits and how to handle 429 responses.
Per-tier limits
| Tier | Requests per day |
|---|---|
| Free | 100 |
| Basic | 1,000 |
| Pro | 5,000 |
| Business | 25,000 |
Limits apply per API key, per UTC day. They reset at 00:00 UTC. RapidAPI plans map to the same underlying limits — a RapidAPI Pro subscription gets the same 5,000 req/day cap as a direct Pro key.
Response headers
Every response (including 429) includes:
X-RateLimit-Limit: <daily quota>
X-RateLimit-Remaining: <requests left today>
X-RateLimit-Reset: <ISO-8601 timestamp of next reset>Read these headers to pace your requests and avoid surprises. The gateway also echoes RapidAPI's own X-RateLimit-* headers — both reflect the same underlying counter.
Handling 429
When you hit the limit, the API responds with 429 RATE_LIMIT_EXCEEDED. The response body includes an ISO-8601 timestamp of the next reset — wait until that time, not for a fixed Retry-After interval.
The simplest backoff strategy: sleep until X-RateLimit-Reset, then retry. Don't spin-retry — 429s don't decrement on the client side, and RapidAPI will start penalising your subscription if you do.
Bursting
Short bursts (tens of requests per second) are fine as long as you stay under the daily quota. There is no per-second sub-limit on either path today, but we may add one if we see abuse.
If you need higher throughput than Business (25k/day), contact us — we offer custom plans for data warehouse and batch-ingestion use cases.