Return 201 Created with a Location Header on Resource Creation

Return 201 Created with a Location Header on Resource Creation | BeforeMerge Rules | BeforeMerge

Why this matters

HTTP defines 201 + Location as the contract for creation. It tells clients exactly where the resource now lives without a second round trip.

Bad

POST /users -> 200 OK
{ "ok": true }

Good

POST /users -> 201 Created
Location: /users/42
{ "id": 42, "email": "a@b.com" }