How do I fix a 429 Too Many Requests error?

Respect the Retry-After header and back off Add client-side throttling and exponential backoff Cache responses to reduce request volume Request a higher rate limit if legitimate

429

Too Many Requests

4xx · Client Error

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

What does HTTP 429 Too Many Requests mean?

The client has sent too many requests in a given amount of time and is being rate limited. The response often includes a Retry-After header telling the client when to try again.

4xx responses indicate the request was faulty: bad syntax, missing authentication, or a resource that does not exist. The fix usually lives on the client/request side.

Common causes

Exceeding an API rate limit
A client retry loop hammering the server
Bot or scraper traffic

How to fix a 429 error

Respect the Retry-After header and back off
Add client-side throttling and exponential backoff
Cache responses to reduce request volume
Request a higher rate limit if legitimate

Related 4xx status codes

400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 405 Method Not Allowed 409 Conflict 410 Gone 418 I'm a teapot 422 Unprocessable Entity

Look up and search every HTTP status code in one place.

Open the HTTP Status Code tool