status Registered
Verified 2026-09-18 · registry updated
2025-09-15HTTP 204 No Content
The request succeeded, but there is no response body to return.
Use 204 for successful operations where the client does not need a representation in the response.
httpstatus codedeleteupdate
Response (http)
HTTP/1.1 204 No Content Cache-Control: no-store
204 No Content is useful for DELETE requests and updates where the client already has all relevant data. A 204 response must not include a message body.
If the client needs the updated resource, return 200 OK with that representation instead.
Common mistakes
- Sending JSON after a 204 status.
- Using 204 when the client needs server-generated fields or validation details.
Registry reference: RFC9110, Section 15.3.5
Sources