HTTP 429 Too Many Requests

You’ve sent too many requests in a given time. Slow down and try again later.

Too Many Requests

4xx Client errorStandardRFC 6585, section 4

You’ve sent too many requests in a given time. Slow down and try again later.

Example response
HTTP/1.1 429 Too Many Requests
Retry-After: 30
Content-Type: application/json
Date: Sun, 15 Nov 2026 09:30:00 GMT

{"error":"rate_limited","message":"Too many requests. Try again in 30 seconds."}

What 429 means

You’ve sent too many requests in a given amount of time: you’ve been rate limited. The server may say how long to wait with a Retry-After header.

When servers send it

When a client goes over an API’s rate limit or quota, and when bot protection thinks requests are coming too fast.

Common causes

  • A script or loop calling an API without delays.
  • Lots of users sharing one IP address (an office, a school, a mobile network) hitting a per-IP limit.
  • Retries without backoff, which makes the problem worse.
  • Going over a daily or monthly quota on a free plan.

How to fix it as a developer

  • Respect Retry-After: it’s either a number of seconds or an HTTP date.
  • Retry with exponential backoff and jitter (wait 1 s, 2 s, 4 s and so on, plus a random bit).
  • Read rate limit headers if the API sends them, such as RateLimit-Remaining or X-RateLimit-Remaining.
  • Cache responses and batch requests to make fewer calls.

How to fix it as a visitor

  • Wait a minute or two and try again.
  • Avoid refreshing over and over, which resets the wait on some sites.

Related codes

  • 503 Service Unavailable: The server can’t handle the request right now, usually because it’s overloaded or down for maintenance.
  • 403 Forbidden: The server understood who you are and won’t let you do this.
  • 420 Enhance Your Calm: An old rate limit code from Twitter’s first API. The standard code for this is 429.

Where it’s defined

429 Too Many Requests is defined in RFC 6585, section 4. It’s a 4xx code, the client error class: something is wrong with the request, so sending it again unchanged won’t help.

Other 4xx codes

400 Bad Request · 401 Unauthorized · 402 Payment Required · 403 Forbidden · 404 Not Found · 405 Method Not Allowed · 406 Not Acceptable · 408 Request Timeout · 409 Conflict · 410 Gone · 413 Content Too Large · 414 URI Too Long · 415 Unsupported Media Type · 418 I’m a teapot · 422 Unprocessable Content · 431 Request Header Fields Too Large · 451 Unavailable For Legal Reasons · 499 Client Closed Request

Or search them all in the HTTP status code list.

Questions people ask

What does HTTP 429 Too Many Requests mean?
You’ve sent too many requests in a given time. Slow down and try again later.
How long should I wait after a 429?
As long as the Retry-After header says. If there isn’t one, back off exponentially: wait a second, then two, then four, and so on.
What’s the difference between 429 and 503?
429 is about you: this client has sent too many requests. 503 is about the server: it can’t handle anyone right now.
Which spec defines 429?
RFC 6585 (2012), section 4. It doesn’t say how servers should count requests, only how to report the limit.
↑↓ move↵ openesc close