Skip to main content
SiteIndex

2xx Success

201 Created

The request succeeded and a new resource was created.

Check a URL's HTTP status

What it means

Typically returned after a POST or PUT that creates something. The Location header usually points to the new resource.

Common causes

  • An API created a record, file, or account.

How to fix it

  1. No fix needed. Include a Location header pointing to the new resource.

Example response

HTTP/1.1 201 Created
Content-Type: text/plain; charset=utf-8

Worked example

A client creates an invoice with POST and receives 201 Created. The response's Location header points to /invoices/123, which the client can request to retrieve the new resource and confirm the stored representation. Treat that URI as the follow-up address rather than guessing an identifier from the request.

How to read this response

  1. Find the status line in your browser's Network panel, API client, or server access log.
  2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
  3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 201
201 Created: The request succeeded and a new resource was created.
Common causes: 201
An API created a record, file, or account.
How to fix it: HTTP 201
No fix needed. Include a Location header pointing to the new resource.

Defined in RFC 9110.

Related codes

Tools