204 No Content
The request succeeded and there is no body to send back.
| Class | Success (2xx) |
|---|---|
| Defined in | RFC9110, Section 15.3.5 |
| Cacheable by default | Yes (RFC 9110, section 15.1) |
Common causes
- A DELETE or PUT succeeded and there is nothing to return.
- An API endpoint intentionally replies with an empty body.
What to do
Do not send a body with 204. Clients must not expect one.
Related codes
- 200 OK: The request succeeded. What the body contains depends on the method used.
- 205 Reset Content: The request succeeded and the client should reset its document view, for example by clearing a form.
- 304 Not Modified: The cached copy is still valid, so no body is sent.