| 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.
Creation semantics are especially important for APIs that can be retried after a lost response. If the request is not naturally idempotent, use the application's idempotency mechanism or first determine whether the resource was already created. The Location value, returned representation, and validators can be used to continue working with the new resource.
Looking for a different code? Search another status or error code.