What does HTTP status code 429 Too Many Requests mean?
Quick answer
HTTP 429 Too Many Requests means a server is reporting that the client sent too many requests in a period of time; this is commonly called rate limiting. The service sets the particular limit and what it applies to. Check the response for a Retry-After value and the service documentation for instructions. The status code alone does not tell you the exact limit or when access will resume. [S1]
The question, the details, the next step.
I received an HTTP 429 response from a website or API. What does it mean?
It means the service is reporting that too many requests were sent within a period of time, a mechanism commonly called rate limiting. Exactly what counts as too many depends on that service: limits may apply broadly or to a particular resource, and may be associated with an IP address, user, or authorized application. [S1]
Read 429 as a signal to check the service’s instructions—not as a complete explanation of its rules. The status code by itself does not give you the limit, the time window, or the requests being counted. Look at the response details and the documentation for the specific service.
What should I inspect in the response before trying again?
First, note the status code and when you received it. Then check whether the response includes a Retry-After header. A service may use that header to indicate how long to wait before requesting again. [S1] Also read any response body or service-specific error details, and consult the service documentation for its rules.
Do not assume every 429 includes a retry instruction, or that the status alone tells you when to try again. If the response does not provide guidance, check the service’s documented rate-limit instructions rather than guessing a wait time.
Can you show how to read a hypothetical response without guessing what the service’s limits are?
Suppose—purely as an example—you see this abbreviated response:
HTTP/1.1 429 Too Many Requests
Retry-After: [value shown by service]
The bracketed text is a placeholder, not a real header value. The useful conclusion is that the server returned 429 and supplied retry guidance. Follow the service’s documented interpretation of that value. Do not infer an overall request allowance, how long the limit lasts, or whether it applies to other users or resources from this example.
A practical note could be: “At [time], a request to [resource] returned 429. The response included [Retry-After value or ‘no Retry-After header’]. Service documentation says [relevant instruction or ‘not found’]. Next action: [follow documented guidance].” Use placeholders rather than including sensitive request data in a note shared broadly.
What if I receive repeated 429 responses, or the response does not explain the limit?
Check the service documentation for the applicable limit and how it defines the requests being counted. A 429 might concern a particular resource or another scope; the status code does not establish which one. [S1] If the response provides Retry-After, use the service’s guidance for that value. If it does not, do not invent a wait time: look for the service’s documented guidance or support channel.
You can report that a response was 429 and describe any accompanying details. The code alone does not establish the service’s exact rate-limit policy. To make the issue easier to investigate, note the time, affected resource, and response details, while avoiding unnecessary sensitive information.
A practical checklist
Record when the 429 occurred and which resource or operation received it.
Check whether the response includes
Retry-Afterand note its displayed value.Read the response body and service documentation for applicable instructions.
Do not guess the limit, its scope, or a retry time from the status code alone.
If guidance remains unclear, use the service provider’s documented support channel.
A few more useful answers
Does 429 tell me the exact number of requests I am allowed to make?
No. It indicates that the service is reporting too many requests, but the status alone does not specify the limit or how the service counts requests. Check that service’s documentation and response details. [S1]
Does every 429 response include a Retry-After header?
No. A response may include Retry-After, but the status code itself does not guarantee that it will. Check the actual response and the service’s instructions. [S1]
Does a 429 always apply to my whole account?
Not necessarily. The scope can vary by service and may apply server-wide, per resource, or based on an IP address, user, or authorized application. The response code alone does not identify which applies. [S1]
Sources
References used for this guide.
- [S1] 429 Too Many Requests — HTTP | MDN developer.mozilla.org · Checked