API Tester

Set a method, URL, headers and body, hit send, and see the status, timing, size, headers and formatted response. Requests go directly from your browser to the endpoint — there is no proxy, so nothing passes through this site and no token you paste is ever seen by anyone but the API you are calling. The honest trade-off is CORS: a browser will not hand a page a cross-origin response unless the server permits it, so APIs that do not send CORS headers cannot be called from here, or from any browser-based tester. When that happens you get an explanation rather than a shrug, plus the same request written as a cURL command you can run in a terminal, where the rule does not apply.

Common failures

SymptomUsual cause
No response at allCORS — server did not permit this origin
Status 401 or 403Missing or wrong credentials — the request did arrive
Few response headersNot exposed cross-origin; normal
Status 0Not shown here; a blocked request never reaches this stage
Works in cURL, not hereCORS — terminals do not enforce it

When to use it

  1. Check what an API actually returns before writing code against it.
  2. Test a POST body and inspect the response.
  3. Confirm an endpoint's status code and response time.
  4. Check which headers an API sends back.
  5. Turn a request you are experimenting with into a cURL command.

How to Use

  1. Pick a method and enter the URL.
  2. Add any headers and a body, then send.
  3. Inspect the response, or copy the request as cURL.

Features

  1. All common HTTP methods
  2. Custom headers and request body
  3. Status, timing and response size
  4. JSON responses formatted automatically
  5. cURL export for endpoints CORS blocks
  6. No proxy, no storage, no tracking

FAQs

Why did my request fail with no response?

Almost always CORS. Your browser blocked the response because the server did not send an Access-Control-Allow-Origin header allowing this page. The request may well have reached the server and succeeded — the browser simply refuses to show the page the answer. It can also be a DNS failure or a refused connection; the browser deliberately does not tell the page which, because that distinction would itself leak information.

Can you add a proxy to get around CORS?

It would work, and it would mean every request and every token you paste passing through someone else's server. That trade is not worth it for a tool whose value is that nothing leaves your browser. Use the cURL export instead — a terminal has no CORS rule.

Is my API token safe?

It stays in this tab, is never written to storage, and is gone when you close the page. It does go to the server you are calling, since that is the point of sending it — so only send credentials to endpoints you trust.

Why are so few response headers shown?

On a cross-origin request the browser exposes only a small safelist — content-type, cache-control and a few others — unless the server opts in with Access-Control-Expose-Headers. The headers are there; the page is not permitted to read them.

What does the timing measure?

The whole exchange from calling fetch to having the full body, so it includes DNS, connection setup, the server's own processing and the download. It is a realistic end-to-end figure rather than server processing time alone.

Does it save my requests?

No. Nothing persists between page loads, which is deliberate — a saved request history containing bearer tokens sitting in browser storage is a liability, not a feature.

Technical Details

Requests go straight from your browser to the URL you enter using fetch. There is no proxy, which is the significant architectural decision here: routing requests through a server would make every API this tool touched — and every token pasted into it — visible to that server, and would turn a private utility into a logging opportunity. The cost of that choice is CORS. A browser refuses to hand a page a cross-origin response unless the server explicitly permits it with an Access-Control-Allow-Origin header, and when it refuses, fetch rejects with an opaque TypeError that deliberately does not say why — distinguishing a CORS refusal from a DNS failure would itself leak information about networks the page cannot otherwise see. So the failure message names both possibilities honestly rather than guessing, and explains that this is a browser rule no client-side tool can work around. Response headers are similarly limited: on a cross-origin response the browser exposes only a short safelist unless the server sends Access-Control-Expose-Headers, so a response showing few headers is usually correct rather than broken. Timing is measured with performance.now around the whole exchange, and bodies that parse as JSON are formatted while anything else is shown verbatim. Every request is also rendered as a cURL command, which runs the same call from a terminal where CORS does not apply. Nothing is stored: tokens live in the tab and are gone when it closes.

Developer Tools

Developer Tools

  • Image to Base64
  • HTML to JSX
  • SVG to JSX Converter
  • Data URI Generator & Decoder
  • SVG to CSS Converter
  • CSS Data URI Converter
  • Basic Auth Header Generator
  • Hex Dump Viewer