Mock YAML endpoint returning HTTP 403

Live demo endpoint

Any method, any path. Returns 403 Forbidden with Content-Type: application/yaml. OPTIONS returns 204 with CORS headers.

Call it with curl

curl -i https://demo-yaml-403.supercrontab.com/

Call it with fetch

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

What HTTP 403 Forbidden means

When you see it

The credentials are valid but this identity is not allowed to do this action, or the IP is blocked.

What a client should do

Do not retry with the same credentials. Check scopes, roles and allowlists on the server side.

Retry?

No

Sample response body

ok: true
id: 42
items:
  - alpha
  - beta
  - gamma

Used by config loaders and some infrastructure APIs. Test indentation handling and list parsing.

Questions