201 Created

What it means

The canonical answer to a successful resource-creating POST (or PUT to a new URL). Well-behaved APIs include a Location header with the URL of the new resource and often return the created object in the body.

Common causes

• A resource-creating POST/PUT succeeded
• Check the Location header for the new resource URL

Reproduce it in cURL

curl -i -X POST https://httpbin.org/status/201

Same request, no terminal: paste this into the cURL converter for native code, or straight into ReqPad on your phone.

How to debug it

If your API returns 200 instead of 201 on create, clients relying on the Location header may break.

The fastest way to pin down a 201 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.

Related codes

200 OK · 202 Accepted · 203 Non-Authoritative Information · 204 No Content · 205 Reset Content · 206 Partial Content — or the full reference.