HTTP Request Client
Send any HTTP request (GET/POST/PUT/PATCH/DELETE) with custom headers + body, see the full response, copy as curl. CORS-free via an edge proxy.
published
- [FREE]
- [NO_SIGNUP]
- [USES_SERVER]
⚠ Unlike most of the site, this tool runs one request on a server because your browser cannot make it directly. It keeps none of your input — see the tool and the privacy page.
An HTTP request client lets you fire requests at any API and inspect the full response — without CORS getting in the way and without installing anything.
Why it needs a (tiny) server
Browsers block cross-origin API calls (CORS), so a purely in-browser client can only hit APIs that explicitly allow it. This tool relays your request through a Cloudflare edge function so you can test any public API, then hands back the status, headers, and body. The request is made to answer you and not stored; private/internal addresses are refused, and a quick (usually invisible) bot check prevents abuse.
What you get
- Methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS.
- Custom request headers + body.
- Full response: status, timing, all headers, pretty-printed JSON body.
- Copy as curl for the exact equivalent command.
Related tools
- curl Converter — turn a curl command into fetch/axios/Python and back.
- HTTP Header Checker — response headers + security grade for a URL.
- Mock REST API — stand up a fake endpoint to test against.
Frequently asked questions
Why does this need a server?
A browser can't call most third-party APIs directly — the same-origin policy and CORS block cross-origin requests from client JavaScript. This relays your request through a Cloudflare edge function so you can test any public API regardless of its CORS settings, then returns the full response.
Do you store my requests or responses?
No. The request is made to produce your response and then discarded — not logged to a database by this tool. Don't send long-lived production secrets through any third-party relay as a habit; for throwaway tokens and public APIs it's fine. Cloudflare may log standard request metadata at the network layer, as any host does.
Which methods and inputs are supported?
GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, with custom request headers (one Key: Value per line) and a request body for the methods that take one. You get the status, timing, all response headers, and the body (JSON is pretty-printed).
Why is there a bot check?
Because this makes outbound requests on the server's behalf, a quick Turnstile check keeps it from being abused as an automated relay. It's usually invisible. Private, loopback, and internal addresses are always refused.
Can I export the request?
Yes — "Copy as curl" gives you the exact equivalent curl command (method, headers, body) to drop into a terminal or script.