HTTP Request Tool
An online REST client: send GET, POST, PUT, PATCH, DELETE and more with custom headers, auth, cookies and a body. Requests run from our edge in the US, Europe or Asia — inspect status, headers, redirects and timing, then copy it as cURL.
Request
Configure a request and press Send. The default User-Agent matches desktop Chrome.
Request options
No Authorization header is added.
Sent with POST, PUT, PATCH, DELETE and OPTIONS. GET and HEAD ignore the body.
Response
Your response will land here
Body, headers, redirects, timing, a safe HTML preview and a reusable cURL command — all in one place.
Rendered in a locked-down sandbox with scripts and network access disabled.
How to send an HTTP request online
Enter the method and URL
Pick GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS and paste the endpoint. Press Enter or Ctrl ↵ to send.
Add headers, auth and a body
Use the tabs to add headers, a Bearer token or Basic auth, cookies, and a JSON, form, XML or GraphQL body.
Choose where it runs from
Send from the nearest edge location or pin it to the US, Europe or Asia to compare latency and geo-specific responses.
Inspect and reuse
Check status, timing, size, headers and redirects, preview HTML safely, and copy the request as a cURL command for your terminal or docs.
A browser-based alternative to cURL and Postman
Browsers block most cross-origin API calls with CORS, so a pure in-page client can’t reach arbitrary APIs. This tool sends your request from a lightweight edge proxy instead, then returns the full response — status, headers, body and redirect chain — exactly as the server sent it. No install, no account and no collection syncing.
HTTP status codes at a glance
| Range | Meaning | Common examples |
|---|---|---|
| 2xx | Success | 200 OK · 201 Created · 204 No Content |
| 3xx | Redirection | 301 Moved Permanently · 302 Found · 304 Not Modified |
| 4xx | Client error | 400 Bad Request · 401 Unauthorized · 403 Forbidden · 404 Not Found · 429 Too Many Requests |
| 5xx | Server error | 500 Internal Server Error · 502 Bad Gateway · 503 Unavailable · 504 Gateway Timeout |
Good to know
- Private, loopback and internal addresses (like
localhostor10.0.0.0/8) are blocked. Use a public URL or a tunnel for local services. - The default
User-Agentmimics current desktop Chrome so bot filters treat the request like a normal browser. Remove or override it in Headers. - Responses are size-limited; very large bodies are truncated and flagged.
Frequently asked questions
Is this an online cURL or Postman alternative?
Yes — for quick requests. You get methods, headers, auth, cookies, bodies, redirects and cURL export in the browser. It isn’t a full Postman workspace: there are no saved collections, environments or team sync.
Can I send requests from different countries?
Yes. Choose Nearest, US, EU or Asia and the request originates from that edge region — useful for geo-restricted APIs, CDN behaviour and latency comparisons.
Are my API keys stored?
No request history is stored in an account database. Requests pass through the edge proxy over HTTPS to reach the target. Still, prefer short-lived or test credentials when using any third-party tool.
Why can’t I call localhost?
The request runs on our edge, not your machine, so localhost would point at the edge server. Private and internal ranges are blocked for safety. Expose local services with a tunnel such as Cloudflare Tunnel or ngrok.
Why does a site work in my browser but not here?
Some sites block data-centre IP ranges, require cookies from a previous page, or use bot protection. Try another region, add the headers your browser sends, or include the needed cookies.