Free tools

HTTP 201 Created

The request succeeded and created a resource. Free reference, no signup.

201 Created

MeaningThe request succeeded and created a resource.
WhenA POST or PUT created something new.
CausesCreating a record, file, or job.
FixNo fix. Store the Location header or id the server returned.
RetryRetry only with an idempotency key, or you may create a duplicate.
Alert?No. Creation is the expected result.

Runs in your browser. Nothing you enter is stored.

Most 201s are not an incident

Creation is the expected result.

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

How to use it

  1. Read what 201 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 201 Created means The request succeeded and created a resource. Servers send it when A POST or PUT created something new.

Common causes: Creating a record, file, or job. The practical fix is: No fix. Store the Location header or id the server returned.

Retry: Retry only with an idempotency key, or you may create a duplicate.

Alert on it? No. Creation is the expected result.

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

The request succeeded and created a resource.

Should the client retry?

Retry only with an idempotency key, or you may create a duplicate.

Should I alert on it?

No. Creation is the expected result.

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.

200 OK The request succeeded. 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.