HTTP 201 Created — Resource Successfully Created
About HTTP 201 Created
HTTP 201 Created indicates that a new resource has been successfully created on the server. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: Status: 201 Created. Category: 2xx Success. A new resource was created. Response includes Location header with new resource URL. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Successful POST request creating a new resource. API endpoint created a new record. File upload completed successfully. User registration or account creation. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Check the Location header for the new resource URL. Verify the response body contains the created resource. Use the returned ID for subsequent requests. Confirm the resource exists with a GET request. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
Difference between 200 and 201?
200 means general success; 201 specifically means a new resource was created.
Overview
HTTP 201 Created indicates that a new resource has been successfully created on the server.
Key Details
- Status: 201 Created
- Category: 2xx Success
- A new resource was created
- Response includes Location header with new resource URL
Common Causes
- Successful POST request creating a new resource
- API endpoint created a new record
- File upload completed successfully
- User registration or account creation
Steps
- 1Check the Location header for the new resource URL
- 2Verify the response body contains the created resource
- 3Use the returned ID for subsequent requests
- 4Confirm the resource exists with a GET request