HTTP 429 Too Many Requests: Meaning and Fix

429 Too Many Requests

Meaning	The client has sent too many requests in a period of time.
When	A rate limit is exceeded.
Causes	A retry storm, a loop, or a limit that is too low for the job. Trigv limits ingest to 60 requests a minute per workspace.
Fix	Slow down, honor Retry-After, and add jitter so clients do not retry together.
Retry	Retry after waiting. Use exponential backoff.
Alert?	Yes. If it is your own API, a 429 means callers are being turned away.

Runs in your browser. Nothing you enter is stored.

Get pinged when your API starts returning 429s

If it is your own API, a 429 means callers are being turned away.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 429","level":"error"}'

Get an API key All status codes

How to use it

Read what 429 means before changing a retry loop.
Check the common causes against the response body and the server log.
Follow the retry note. Retrying a 400 with the same body will fail again.
If this is your API, use the snippet to hear about it.

About this tool

HTTP 429 Too Many Requests means The client has sent too many requests in a period of time. Servers send it when A rate limit is exceeded.

Common causes: A retry storm, a loop, or a limit that is too low for the job. Trigv limits ingest to 60 requests a minute per workspace. The practical fix is: Slow down, honor Retry-After, and add jitter so clients do not retry together.

Retry: Retry after waiting. Use exponential backoff.

Alert on it? Yes. If it is your own API, a 429 means callers are being turned away.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 429?

The client has sent too many requests in a period of time.

Should the client retry?

Retry after waiting. Use exponential backoff.

Should I alert on it?

Yes. If it is your own API, a 429 means callers are being turned away.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

400 Bad Request The server could not understand the request. 401 Unauthorized The request is missing valid authentication. 403 Forbidden The server understood the request and refuses it. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.

HTTP 429 Too Many Requests