loot.tools
429

Too Many Requests

4xx Client Error

The client sent too many requests in a given time, hitting a rate limit.

429 Too Many Requests means you've tripped a rate limit. The server should send a Retry-After header telling you how long to wait. The right response is to back off, ideally with exponential backoff and jitter, rather than hammering the endpoint - which only extends the block.

What 429 looks like on the wire

GET /api/search?q=shoes HTTP/1.1
Host: api.example.com

HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0

About 4xx Client Error

The request has a problem the client needs to fix, like a bad URL, missing auth, or invalid input.

How to fix 429 Too Many Requests

  • Honor the Retry-After header before retrying.
  • Add exponential backoff with jitter to your retry logic.
  • Cache responses or batch calls to cut request volume.
  • If you legitimately need more, ask about a higher rate-limit tier.

Tools that help with 429

Timestamp Converter
Convert a Retry-After or X-RateLimit-Reset epoch value into a readable time so you know when to retry.

Where it's defined

429 Too Many Requests is defined in RFC 6585 §4. MDN's 429 reference covers browser behavior and examples.

Looking for a different one? See the full HTTP status code reference.