What 429 Too Many Requests means
429 Too Many Requests indicates the client exceeded a rate limit for the resource. The response may include Retry-After (seconds or a date) and rate-limit headers such as RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset.
When a server should return it
- An API key exceeded its per-minute or per-day quota.
- A login endpoint throttled repeated failures.
- A crawler hit a site-wide request cap.
- A shared IP triggered a per-IP limit.
Example response
HTTP/1.1 429 Too Many Requests
Retry-After: 30
RateLimit-Limit: 100
RateLimit-Remaining: 0
RateLimit-Reset: 30
{"title": "Too Many Requests", "status": 429}Why you might see it unexpectedly
- A client retrying a failed request immediately in a loop.
- Multiple instances of a service sharing one quota.
- A proxy collapsing many users into one IP.
- A limit counted per second while the client assumes per minute.
Related status codes
503 Service Unavailable is server overload or maintenance. 403 Forbidden is permission, not rate. 408 Request Timeout is a slow client.