All HTTP status codes

HTTP 204 No Content

Success

The request succeeded and there is intentionally no response body. Typical for DELETE operations and for PUT/PATCH when the server returns nothing.

Defined in RFC 9110

Common causes

  • Successful DELETE / save endpoints that return no payload
  • Preflight-adjacent endpoints designed to be body-less

How to fix it

  1. Nothing to fix — clients must not try to parse a body

  2. If JSON parsing fails on an empty response, guard for 204 before calling response.json()

Related status codes

200 OK

The request succeeded. The response body contains the result — a page for GET, the operation outcome for POST.

205 Reset Content

Like 204, but additionally tells the client to reset the document view — e.g. clear the form that produced the request.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.