Mock CSV endpoint returning HTTP 204
https://demo-csv-204.supercrontab.com/ answers every request with HTTP 204 No Content and an empty body. No signup, CORS enabled, nothing logged. Use it to see how your client, retry logic or cron job behaves on a 204 before it happens in production.
Live demo endpoint
Any method, any path. Returns 204 No Content with Content-Type: text/csv; charset=utf-8. OPTIONS returns 204 with CORS headers.
Call it with curl
curl -i https://demo-csv-204.supercrontab.com/
Call it with fetch
const res = await fetch("https://demo-csv-204.supercrontab.com/");
console.log(res.status); // 204
const body = await res.text();What HTTP 204 No Content means
- When you see it
- The request worked but there is nothing to return, typical for DELETE, PUT and OPTIONS preflight responses.
- What a client should do
- Treat it as success and do not try to parse a body. response.json() throws on an empty body.
- Retry?
- No
Sample response body
Empty. HTTP 204 must not carry a body, so the endpoint sends none.
A header row and three data rows. Use it to test CSV importers, exports and spreadsheet links.
Questions
Does this endpoint really return HTTP 204 every time?
Yes. Every GET, POST, PUT, PATCH or DELETE to https://demo-csv-204.supercrontab.com/ gets status 204 No Content with a small CSV body, whatever the path, query or headers. OPTIONS gets 204 with CORS headers so browsers can preflight.
Should my client retry a 204?
No. Retrying the same request cannot change the outcome. Treat it as success and do not try to parse a body. response.json() throws on an empty body.
Can I get a different format, a delay or a custom body?
The same status is available in JSON, XML, Text, HTML, YAML, RSS, JavaScript. Delays, custom headers, error rates, request logging and your own body need a personal endpoint: sign up and create one at /endpoints in a minute, free.