---
title: "HTTP 201 Created — What It Means & How to Fix It"
description: "HTTP 201 Created: The request succeeded and a new resource was created. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/201
---

# HTTP 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. 1  
A POST request successfully created a new resource, such as a new user account, database record, or uploaded file.
2. 2  
A PUT request created a resource at a specific URI that did not previously exist.
3. 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. 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. 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. 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

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 200 OK](https://uptrack.app/http/200)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
