HTTP Request Tester — Test API Requests Online Free

How to Use HTTP Request Tester

Choose an HTTP method from the dropdown — GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS — then type or paste the full endpoint URL including https://.
Click Add Header to include any request headers — for example Authorization: Bearer <token>, Content-Type: application/json, or Accept: application/json.
For POST, PUT, or PATCH requests, a Body field appears automatically. Paste your JSON payload, form data, or plain text.
Click Send. The response section shows the HTTP status code, response time in milliseconds, total response size, all response headers, and the full response body — with automatic JSON pretty-printing.

This free API tester is a browser-based alternative to desktop tools like Postman, Insomnia, and Bruno. It is useful for testing REST APIs, GraphQL HTTP endpoints, webhook URLs, third-party API integrations, and debugging server response headers. The default URL (https://jsonplaceholder.typicode.com/posts/1) shows a working GET request immediately so you can see the output format before testing your own endpoints.

How HTTP Request Tester Works

HTTP Request Tester sends requests directly from your browser using the fetch() API (defined in the WHATWG Fetch specification). There is no server-side proxy — your request travels directly from your device to the target server. The tool records the time between sending the request and receiving the first byte of the response, parses all response headers, and attempts to JSON-pretty-print the body if the content type is JSON. If the server does not return CORS headers, the browser blocks the response before this tool can read it — this is a browser security feature, not a bug.

Supports GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS methods
Add any number of custom request headers — Authorization, Content-Type, X-API-Key, and more
Response status badge colour-codes success (green), redirect (yellow), and error (red) at a glance
Measures response time in milliseconds and response body size in bytes
Auto-pretty-prints JSON responses for easy reading
No proxy, no logging, no sign-up — 100% browser-side using the native Fetch API

Frequently Asked Questions

Why does my request fail with a CORS error?

CORS (Cross-Origin Resource Sharing) is a browser security mechanism. When your browser makes a fetch request from this page to a different origin, the browser checks whether the server's response includes an Access-Control-Allow-Origin header that permits the request. If the API does not include that header, the browser blocks the response — you get a network error even if the server actually processed the request. CORS is enforced client-side; no proxy or request debugger running in the browser can bypass it. Workarounds include: testing from the same origin, using a server-side proxy, enabling CORS in the API's configuration, or using a browser extension that temporarily disables CORS enforcement during development.

Does this tool send requests through a proxy?

No — all HTTP requests are made directly from your browser using the fetch() API. Your request goes straight from your device to the target server without passing through any Chunky Munster infrastructure. This means no request bodies, API keys, or authentication tokens are stored or logged. It also means CORS restrictions apply in full.

What is the difference between GET and POST?

GET retrieves a resource from the server and should be idempotent and side-effect-free — it should not have a request body. POST submits data to the server (in the body) to create a new resource or trigger an action. PUT replaces an existing resource in full; PATCH partially updates a resource. DELETE removes a resource. HEAD returns only the response headers (no body) — useful for checking content type, cache headers, or file size without downloading the body. OPTIONS queries which methods and headers the server allows (used in CORS preflight requests).

How do I send a JSON body?

Select POST, PUT, or PATCH as the method. The Body field appears automatically. Paste your JSON object (e.g. {"name":"Alice","age":30}). Then click Add Header and add Content-Type with the value application/json — this tells the server how to interpret the body. The request sends the raw body text exactly as typed, so valid JSON syntax is required if the API expects it.

Explore the full suite of Network and Developer tools — including WebSocket Debugger, DNS Lookup, JWT Decoder, and 310+ other free utilities — at Chunky Munster.

HTTP Request Tester online

Send API requests and inspect responses — GET, POST, PUT, PATCH, DELETE