204 No Content

What it means

The request worked and there is deliberately nothing to return — typical for DELETE, or PUT/PATCH where the server has nothing to add. The response must not include a body.

Common causes

• Successful DELETE/PUT with intentionally empty body
• Calling response.json() on a 204 throws in most clients — guard for empty bodies

Reproduce it in cURL

curl -i https://httpbin.org/status/204

Same request, no terminal: paste this into the cURL converter for native code, or straight into ReqPad on your phone.

How to debug it

JSON-parsing a 204 response is a classic client crash; guard for empty bodies before calling response.json().

The fastest way to pin down a 204 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.

Related codes

200 OK · 201 Created · 202 Accepted · 203 Non-Authoritative Information · 205 Reset Content · 206 Partial Content — or the full reference.