201 - Created

Start Here

Use the closest compare guide, playbook, or adjacent error page to narrow the decision faster before you start changing production systems.

This page is part of the Error Reference library. Learn more about the project or report a correction.

What Does Created Mean?

201 confirms both transport success and a state change — a new resource now exists. Missing Location header or wrong response body after 201 breaks downstream resource tracking and idempotency guarantees.

Common Causes

• -Client does not receive 201 confirmation due to network timeout and retries the POST, causing the server to create a duplicate resource because the handler is not idempotent.
• -Server returns 201 but omits the Location header, so the client cannot reference the newly created resource without issuing a separate lookup request.
• -Client code treats any non-201 response as failure and does not handle 200 fallback, causing integration breaks when legacy endpoints return 200 for resource creation instead of 201.

How to Fix Created

1. 1Check whether the POST handler implements idempotency keys so duplicate requests return the existing resource instead of creating a second one.
2. 2Verify the server includes a Location header in the 201 response pointing to the canonical URI of the new resource.
3. 3Update client integration logic to accept both 200 and 201 as valid success responses for resource creation endpoints.

Step-by-Step Diagnosis for Created

1. 1Confirm the response status is 201 and inspect the Location header for the new resource URI.
2. 2Check server logs for duplicate resource creation when the same client request appears more than once within a short window.
3. 3Verify the created resource is immediately accessible via GET at the Location URI, accounting for any propagation delay.
4. 4Test the endpoint with and without an idempotency key header to confirm duplicate-safe behavior.

curl -i -X POST https://api.example.com/v1/users \
  -H 'Content-Type: application/json' \
  -d '{"name":"Alice","email":"alice@example.com"}'
# Response:
# HTTP/1.1 201 Created
# Location: /v1/users/456
# {"id":"456","name":"Alice","email":"alice@example.com"}

const response = await fetch('https://api.example.com/v1/users', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ name: 'Alice', email: 'alice@example.com' }),
});
if (response.status === 201) {
  const location = response.headers.get('Location');
  const created = await response.json();
  console.log('Created at:', location, created);
}

import requests

response = requests.post(
    'https://api.example.com/v1/users',
    json={'name': 'Alice', 'email': 'alice@example.com'},
)
if response.status_code == 201:
    location = response.headers.get('Location')
    created = response.json()
    print(f'Created at: {location}', created)

Seen in Production

Debugging Tools

• -curl -i to inspect Location header in raw 201 response
• -Network tab in browser DevTools to confirm header presence and value
• -Server access logs to detect duplicate POST requests within short time windows
• -Database audit logs to identify duplicate resource records with identical payload

How to Verify the Fix

• -Re-run the POST request and confirm 201 is returned with a valid Location header pointing to the new resource.
• -Issue a GET to the Location URI and verify the response matches the resource created in the POST body.
• -Replay the same POST with the same idempotency key and confirm the server returns the original 201 without creating a duplicate.

How to Prevent Recurrence

• -Enforce idempotency keys on all non-idempotent POST endpoints and document the expected behavior in API contracts.
• -Add contract tests that assert Location header presence and validity on every 201 response in CI.
• -Standardize client integration libraries to handle both 200 and 201 as creation success so legacy and modern endpoints are supported uniformly.

Pro Tip

Related Errors

Official References

• -RFC 9110 Section 15.3.2 - 201 Created definition
• -IANA HTTP Status Code Registry - 201 Created
• -MDN Web Docs — 201 Created
• -HTTP Official Documentation