201
Created
The request succeeded and a new resource was created. The server returns this after a successful POST (or sometimes PUT) request that results in a new resource being stored.
What does HTTP 201 mean?
The request succeeded and a new resource was created. The server returns this after a successful POST (or sometimes PUT) request that results in a new resource being stored.
Common causes
- 1
A POST request successfully created a new resource, such as a new user account, database record, or uploaded file.
- 2
A PUT request created a resource at a specific URI that did not previously exist.
- 3
The response typically includes a Location header pointing to the newly created resource, and the body may contain the created resource.
How to fix it
- 1
No fix needed — 201 means the resource was successfully created. If your client does not handle 201, update it to treat 2xx status codes as success.
- 2
If your API returns 200 instead of 201 for creation, update the server to return 201 with a Location header for better REST semantics.
- 3
Ensure your client follows the Location header in the response if it needs to access the newly created resource.
Monitor for HTTP 201 errors
If your API endpoint creates resources and should return 201, Uptrack can validate the expected status code. Any deviation triggers an alert so you catch broken creation flows early.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free