Mock Text endpoint returning HTTP 200
https://demo-txt-200.supercrontab.com/ answers every request with HTTP 200 OK and a small Text body. No signup, CORS enabled, nothing logged. Use it to see how your client, retry logic or cron job behaves on a 200 before it happens in production.
Live demo endpoint
Any method, any path. Returns 200 OK with Content-Type: text/plain; charset=utf-8. OPTIONS returns 204 with CORS headers.
Call it with curl
curl -i https://demo-txt-200.supercrontab.com/
Call it with fetch
const res = await fetch("https://demo-txt-200.supercrontab.com/");
console.log(res.status); // 200
const body = await res.text();What HTTP 200 OK means
- When you see it
- The request succeeded and the body holds the result. This is the normal case for GET and most POST calls.
- What a client should do
- Read the body and move on. Do not treat a 200 with an empty body as an error unless your contract says so.
- Retry?
- No
Sample response body
ok 42
Plain text, no structure. Handy for health checks and for clients that only read the status code.
Questions
Does this endpoint really return HTTP 200 every time?
Yes. Every GET, POST, PUT, PATCH or DELETE to https://demo-txt-200.supercrontab.com/ gets status 200 OK with a small Text body, whatever the path, query or headers. OPTIONS gets 204 with CORS headers so browsers can preflight.
Should my client retry a 200?
No. Retrying the same request cannot change the outcome. Read the body and move on. Do not treat a 200 with an empty body as an error unless your contract says so.
Can I get a different format, a delay or a custom body?
The same status is available in JSON, XML, CSV, 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.