HTTP 429 Too Many Requests — Rate Limited
Critical4xx client error
Overview
HTTP 429 Too Many Requests means you have exceeded the rate limit. Wait before retrying.
Key Details
- Status: 429 Too Many Requests
- Category: 4xx Client Error
- Rate limit exceeded
- Check Retry-After header for wait time
Common Causes
- Too many API calls in a short period
- Rate limiting by the server or API gateway
- DDoS protection triggered
- Per-user or per-IP request quota exceeded
Steps
- 1Check the Retry-After header for how long to wait
- 2Implement exponential backoff in your client
- 3Cache responses to reduce API calls
- 4Request a higher rate limit if available
Tags
http-status4xx-client-errorhttp-429httpstatus-code
More in 4xx Client Error
http-400-bad-requestHTTP 400 Bad Request — What It Means & How to Fix It
Errorhttp-401-unauthorizedHTTP 401 Unauthorized — What It Means & How to Fix It
Errorhttp-402-payment-requiredHTTP 402 Payment Required — What It Means & How to Fix It
Errorhttp-403-forbiddenHTTP 403 Forbidden — What It Means & How to Fix It
Errorhttp-404-not-foundHTTP 404 Not Found — What It Means & How to Fix It
Errorhttp-405-method-not-allowedHTTP 405 Method Not Allowed — What It Means & How to Fix It
ErrorFrequently Asked Questions
Check the Retry-After header. If absent, start with 1 second and double on each retry.