Mock Text endpoint returning HTTP 201

https://demo-txt-201.supercrontab.com/ answers every request with HTTP 201 Created 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 201 before it happens in production.

Live demo endpoint

https://demo-txt-201.supercrontab.com/

Any method, any path. Returns 201 Created with Content-Type: text/plain; charset=utf-8. OPTIONS returns 204 with CORS headers.

Call it with curl

curl -i https://demo-txt-201.supercrontab.com/

Call it with fetch

const res = await fetch("https://demo-txt-201.supercrontab.com/");
console.log(res.status); // 201
const body = await res.text();

What HTTP 201 Created means

When you see it
A POST or PUT created a new resource. APIs often return the new object and a Location header pointing at it.
What a client should do
Store the id or Location header from the response. Do not send the same create request again.
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 201 every time?

Yes. Every GET, POST, PUT, PATCH or DELETE to https://demo-txt-201.supercrontab.com/ gets status 201 Created 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 201?

No. Retrying the same request cannot change the outcome. Store the id or Location header from the response. Do not send the same create request again.

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.