hub · playground

Send anything. Inspect everything.

Pick an endpoint, tune the parameters, hit send. The raw response comes back here — status, headers, body, timing.

Endpoint

—

Response

Select an endpoint above to begin.

name	value
no response yet

—

—

—

—

—

—

—

Known limits

/redirect-chain doesn't show individual hops. The Fetch API doesn't expose intermediate Location headers; you'll see response.redirected = true and the final URL only. For a full hop trace, use curl -v.
/drip buffers the entire body before display rather than streaming it. The final bytes are correct, but you can't watch the chunks arrive. For a real streaming view, use curl --no-buffer or read the response with response.body.getReader() in your own code.
/cors-broken from this same-origin context bypasses the browser's CORS enforcement. The response comes through; the block doesn't. Send from a different origin (your own app, a JSFiddle, a local dev server on another port) to see the real failure.
Custom headers aren't editable in the form — only headers declared as parameters in the OpenAPI spec are surfaced (currently just Authorization on /auth-required). For ad-hoc headers, copy the curl command and edit it manually.
Deep-link URLs capture form values but not the request body. For /echo POST/PUT/PATCH, the path and method survive sharing, but the body is reset on load.
Non-browser clients hitting the live API (curl, PowerShell, test runners, language SDKs) may receive an edge bot-management challenge ("Just a moment…") instead of a chaos response. This is a WAF/Bot setting on the zone, not something the playground can work around. The playground itself runs in a browser so it's exempt.

Create a custom endpoint pair