Account

What new tool do you want?

Developer Tools

API Tester (Online REST Client)

Send HTTP requests from your browser — any method, query params, headers, JSON or form body, bearer/basic/API-key auth — and inspect status, timing, headers and pretty-printed JSON. Export as cURL, JavaScript or Python.

How to use

  1. 1Choose the method and enter the URL.
  2. 2Add params, headers, a body or auth.
  3. 3Send and inspect the response, or copy the request as code.

Frequently asked questions

Why does a request fail here but work in Postman or curl?

Browsers only let web pages call APIs that allow it (CORS). Use the Code tab to run the same request with curl or from your server.

Are my tokens safe?

Requests go straight from your browser to the API; tokens are stored only in this browser's local storage.

Is there a timeout?

Yes — requests are cancelled after 15 seconds.

What actually happens when you press Send

This isn't a mock — the URL, method, query params, headers, body and auth you set are assembled into one real fetch() call that leaves your browser and hits the server directly, with a 15-second timeout. The response you get back (status, timing in ms, size, every header, and the body) is exactly what your own frontend code would receive calling the same endpoint. The last 20 requests are kept in a History panel backed by browser storage, so you can revisit a previous call without retyping it, but nothing is sent to any server of ours in between.

Why a request fails here but works in curl or Postman

Browsers enforce CORS; command-line tools and API clients like Postman don't, because CORS is a browser-only safety rule about which web pages may read a cross-origin response. If a request errors here, the most common cause isn't a bad URL — it's an API that never sends Access-Control-Allow-Origin for your origin. The Code tab sidesteps this entirely by giving you the equivalent curl or Python command to run from a terminal or server, where CORS doesn't apply.

Worked example: a GET request, decoded into curl

The default request — GET to https://jsonplaceholder.typicode.com/posts with the query parameter userId=1 enabled and an Accept: application/json header — merges into the URL https://jsonplaceholder.typicode.com/posts?userId=1 before it's sent. Pressing Send returns HTTP 200 with a JSON array of that user's posts, pretty-printed automatically because the response's content-type is JSON. Switching to the Code tab and choosing cURL produces exactly: curl -X GET 'https://jsonplaceholder.typicode.com/posts?userId=1' \ -H 'Accept: application/json' — a copy-pasteable command that reproduces the same call outside the browser.

Auth stays local, but it's still a browser

Bearer tokens, Basic credentials and API-key headers are folded into the outgoing request's headers the same way a real client would send them, and saved only in this browser's local storage between visits — not uploaded anywhere. That's convenient for iterating on a request, but it also means production secrets typed into a shared or public computer stay on that machine. For anything sensitive, test with a scoped or throwaway token rather than a live production key.

A JSON body is checked before anything is sent

The method opens on GET, with an Accept header for JSON turned on. GET and HEAD never send a body. If the body type is JSON and a body would be sent, it is parsed first. A body that is not valid JSON stops with "The JSON body is invalid" and the reason, and no request goes out. Form bodies keep only lines that contain an equals sign. Pretty printing starts on and reformats a JSON response. History keeps up to 20 calls and replaces an older row with the same method and address.

Related tools

More: Developer Tools