429 Too Many Requests
The HTTP429 Too Many Requestsclient error response status code indicates the client has sent too many requests in a given amount of time.This mechanism of asking the client to slow down the rate of requests is commonly called "rate limiting".
ARetry-After header may be included to this response to indicate how long a client should wait before making the request again.
Implementations of rate limiting vary; restrictions may be server-wide or per resource.Typically, rate-limiting restrictions are based on a client's IP but can be specific to users or authorized applications if requests are authenticated or contain acookie.
Status
429 Too Many RequestsExamples
Response containing Retry-After header
The following request is being sent repeatedly in a loop by a client that is misconfigured:
GET /reports/mdn HTTP/1.1Host: example.comIn this example, server-wide rate limiting is active when a client exceeds a set threshold of requests per minute.A 429 response is returned with aRetry-After header that indicates that requests will be allowed for this client again in 60 minutes:
HTTP/1.1 429 Too Many RequestsContent-Type: text/htmlRetry-After: 3600<html lang="en-US"> <head> <title>Too Many Requests</title> </head> <body> <h1>Too Many Requests</h1> <p>You're doing that too often! Try again later.</p> </body></html>Specifications
| Specification |
|---|
| RFC 6585 # section-4 |