Free tools

HTTP 200 OK

The request succeeded. Free reference, no signup.

200 OK

MeaningThe request succeeded.
WhenThe server completed the request and is returning a body.
CausesA normal successful response.
FixNo fix. If a 200 still means failure inside the JSON, alert on that application error instead of the HTTP status.
RetryDo not retry a successful request unless you know it is safe.
Alert?No. Success is not an incident.

Runs in your browser. Nothing you enter is stored.

Most 200s are not an incident

Success is not an incident.

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 200","level":"warning"}'
Get an API key All status codes

How to use it

  1. Read what 200 means before changing a retry loop.
  2. Check the common causes against the response body and the server log.
  3. Follow the retry note. Retrying a 400 with the same body will fail again.
  4. Alert only in the cases the verdict describes.

About this tool

HTTP 200 OK means The request succeeded. Servers send it when The server completed the request and is returning a body.

Common causes: A normal successful response. The practical fix is: No fix. If a 200 still means failure inside the JSON, alert on that application error instead of the HTTP status.

Retry: Do not retry a successful request unless you know it is safe.

Alert on it? No. Success is not an incident.

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 200?

The request succeeded.

Should the client retry?

Do not retry a successful request unless you know it is safe.

Should I alert on it?

No. Success is not an incident.

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.

201 Created The request succeeded and created a resource. 202 Accepted The server accepted the request and will finish it later. 204 No Content The request succeeded and there is no body. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.