| Previous | Next |
| HTTP_STATUS_OK | HTTP_STATUS_ACCEPTED |
HTTP_STATUS_CREATED
The primary created resource should normally be identified by a Location header. The response body can describe the new resource or provide links to it.
For API clients, keep the returned identifier and validators such as ETag. Retrying a create request without an idempotency mechanism can create duplicate resources.
Operational meaning of HTTP 201 for HTTP_STATUS_CREATED
HTTP 201 (this result) is a successful response. AllStat records its meaning as “201 Created”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Verify what work the response representation says was completed; this result can still describe asynchronous or partial handling.
- use validators, location/status links, and application identifiers supplied by the server.
- do not retry a non-idempotent request merely because the client did not understand the response body.
For telemetry, record HTTP 201, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.