204 No Content
The request succeeded and there is deliberately no content in the response body. Headers such as ETag can still be meaningful.
2xx · Success
Typical causes
DELETE endpoints, saves that return nothing, and some CORS preflight replies. Clients that always parse a JSON body fail on it.
Defined in RFC 9110, §15.3.5