What is HTTP Request Tester?
HTTP Request Tester is a lightweight REST client in your browser. Pick a method (GET, POST, PUT, PATCH, DELETE, OPTIONS or HEAD), enter an endpoint URL, add request headers as JSON and an optional body, then send the request. The response appears below with its status code and text, every readable response header, and the body, pretty-printed when it is JSON.
It is handy for quick checks when opening Postman or writing a curl command feels like overkill: confirming that an endpoint is up, trying a payload, or seeing which headers an API returns. Requests go straight from your browser to the API, with no proxy in between.
How to use HTTP Request Tester
- Choose the HTTP method from the dropdown.
- Enter the full endpoint URL, including https://.
- Edit the request headers JSON, for example {"Content-Type": "application/json", "Authorization": "Bearer <token>"}.
- For POST, PUT, PATCH or DELETE, enter the request body, such as a JSON payload.
- Send the request and read the status, response headers and body; if the browser blocks it, copy the equivalent curl command shown below and run it in a terminal.
Key features
- GET, POST, PUT, PATCH, DELETE, OPTIONS and HEAD methods
- Custom request headers entered as JSON
- Request body for POST, PUT, PATCH and DELETE
- Response status, timing, headers and body in one view
- JSON responses pretty-printed automatically
- Copy the same request as a curl command
- Requests go directly from your browser; nothing passes through our servers
Common use cases
- Checking that a REST endpoint is up and returns the expected status
- Trying a JSON payload against a POST or PUT endpoint before writing client code
- Testing bearer tokens and API keys in the Authorization header
- Debugging CORS configuration on your own API
- Inspecting the response shape of a public API
Technical details & standards
Requests are made with the browser's fetch() API, so they follow the browser's CORS rules: the API must allow cross-origin requests from this site (an Access-Control-Allow-Origin header), otherwise the browser blocks the response and you see a network error. Public APIs and your own development servers with CORS enabled work well; many websites do not. Custom headers and non-simple methods also trigger a CORS preflight OPTIONS request.
Only response headers that the server exposes to scripts are readable: the CORS-safelisted ones (Cache-Control, Content-Language, Content-Length, Content-Type, Expires, Last-Modified, Pragma) plus any listed in Access-Control-Expose-Headers. Bodies starting with { or [ are parsed and shown as formatted JSON.
Send the same HTTP request from code or the terminal
The tester writes the equivalent curl command under your request as you type. To repeat the request in a script instead, these send the same JSON POST to httpbin.org, a public echo service, and print the status.
curl
curl -X POST https://httpbin.org/post \
-H "Content-Type: application/json" \
-d '{"name":"Ada"}'
curl -I https://httpbin.org/get # headers onlyJavaScript (browser or Node.js 18+)
const res = await fetch("https://httpbin.org/post", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ name: "Ada" }),
});
console.log(res.status, res.headers.get("content-type")); // 200 "application/json"
console.log((await res.json()).json); // { name: "Ada" }Node.js is not bound by CORS, so a request that fails in the browser tester may still work from a server-side script.
Python
import json, urllib.request
req = urllib.request.Request(
"https://httpbin.org/post",
data=json.dumps({"name": "Ada"}).encode(),
headers={"Content-Type": "application/json"},
method="POST",
)
with urllib.request.urlopen(req) as res:
print(res.status, res.headers["Content-Type"]) # 200 application/jsonFrequently asked questions
Why do I get a CORS or network error?
The request is sent from your browser, so the API must allow cross-origin requests. If it does not send an Access-Control-Allow-Origin header that permits this site, the browser blocks the response. Test such APIs with curl or a desktop client, or enable CORS on your own server.
Why are some response headers missing?
Browsers only let scripts read the CORS-safelisted headers (such as Content-Type and Cache-Control) plus any the server lists in Access-Control-Expose-Headers. Headers such as Set-Cookie are never readable from the page.
How do I send a JSON body?
Choose POST, PUT or PATCH, keep "Content-Type": "application/json" in the headers JSON, and paste your JSON into the body box. The body is sent exactly as typed.
Is this a replacement for Postman?
For quick one-off requests, yes. It does not save collections, environments or history, and browser CORS rules limit which APIs it can reach, so for larger test suites a desktop client is still the better fit.
How do I test an HTTP request online without installing anything?
Enter the URL, pick the method, add any headers and a JSON body, and click Send Request. The status, response time, headers and body appear below, along with a curl command for the same request. Try it on a public echo API such as https://httpbin.org/post, which sends back exactly what it received.
Is my data safe?
When you request a URL, your browser sends the request directly to that destination. CodeUnpack does not proxy the request.
Does it work offline?
This tool needs an internet connection to request the target URL.