429 Too Many Requests

The user has sent too many requests in a given amount of time (“rate limiting”).

Response representations SHOULD include details explaining the condition, and MAY include a Retry-After header indicating how long to wait before making a new request. For example:

HTTP/1.1 429 Too Many Requests
Content-Type: text/html
Retry-After: 3600


 Too Many Requests


 Too Many Requests
 I only allow 50 requests per hour to this Web site per logged in user. Try again soon.

Note that this specification does not define how the origin server identifies the user, nor how it counts requests. For example, an origin server that is rate limiting requests may do so based on counts of requests per resource, across the entire server, or even among a set of servers. Likewise, it may identify the user by their authentication credentials or a stateful cookie.

Responses with the 429 status code MUST NOT be stored by a cache.