429
Too Many Requests
Client errors (4xx)·RFC 6585
What 429 means
The client has sent too many requests in a given time (rate limiting).
A Retry-After header often states how long to wait. Back off and slow the request rate.
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot421Misdirected Request422Unprocessable Content423Locked424Failed Dependency425Too Early426Upgrade Required428Precondition Required431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 429
What does HTTP 429 mean?
429 Too Many Requests: The client has sent too many requests in a given time (rate limiting). A Retry-After header often states how long to wait. Back off and slow the request rate.
Which class does status code 429 belong to?
429 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 429 code defined?
Status code 429 is defined in RFC 6585 and is part of the IANA HTTP Status Code Registry.