HTTP Client
Compose a request, send it from your browser and inspect the response.
Parameters stay in sync with the URL. Untick a row to leave it out without deleting it.
Browsers silently drop some headers (Host, Cookie, Origin, Referer, Content-Length…) and may ignore User-Agent.
No body will be sent.
Cross-origin responses only expose headers the server lists in
Access-Control-Expose-Headers (plus a few safe ones).Send a request to see exactly what was sent.
About this tool
This client runs inside your browser using the fetch API, so it follows the same rules as any web page. Pick a method, enter a URL, add query parameters, headers and an optional body, then press Enter in the URL field or click Send. Long requests can be cancelled, and they are aborted automatically after the timeout.
Why does my request fail with a network error?
- CORS: a page can only read a cross-origin response if the server allows it with
Access-Control-Allow-Origin. Many public APIs do; many private ones don't. The browser hides the details, so a blocked request looks like a generic network error. Server-to-server tools like cURL are not subject to CORS. - Preflight: non-simple requests (e.g. JSON bodies, PUT/DELETE, custom headers) first send an
OPTIONSrequest that the server must answer correctly. - Mixed content: this page is served over HTTPS, so plain
http://URLs are usually blocked. - Forbidden headers: headers such as Host, Cookie or Origin are controlled by the browser and cannot be set.
Privacy
Requests go directly from your browser to the URL you enter — this site never sees or proxies them. Nothing is stored.