All HTTP status codes

HTTP 201 Created

Success

The request succeeded and a new resource was created. The Location header usually points at the new resource — the canonical response for a successful POST in REST APIs.

Defined in RFC 9110

Common causes

  • Successful resource creation (POST /users, PUT to a new URL)

How to fix it

  1. Nothing to fix

  2. API consumers should read the Location header instead of assuming the new resource URL

Related status codes

200 OK

The request succeeded. The response body contains the result — a page for GET, the operation outcome for POST.

204 No Content

The request succeeded and there is intentionally no response body. Typical for DELETE operations and for PUT/PATCH when the server returns nothing.

409 Conflict

The request conflicts with the resource's current state — classic cases are duplicate creation and stale optimistic-locking versions.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.