🔌 API Tester

Send HTTP requests and inspect responses. A browser-based API client, like a mini Postman.

Last updated: November 8, 2026 · By the BoltQuickTools team

Note: This tool runs entirely in your browser using the fetch() API. Due to CORS (Cross-Origin Resource Sharing) restrictions, some APIs may block requests from web pages. If a request fails, the target server may not allow cross-origin requests. Public APIs and APIs with permissive CORS headers will work fine. For restricted APIs, consider using a dedicated API client or a CORS proxy.

Request History

No requests yet. Send your first request above.

Send one HTTP request and read the raw answer

When an endpoint misbehaves, you often just want to fire a single request and see the status, headers and body before writing any code. This page does that from a browser tab, which helps when you are on a machine with no API client installed and the API allows browser access.

Requests go directly from your browser to the URL you enter, using fetch(). There is no proxy in between, so the target server receives everything you send, along with your IP address.

Building the request

  1. Choose a method from the dropdown (GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS) and type the URL. If you leave off the scheme, https:// is added.
  2. On the Headers tab, click + Add Header or pick from Add common header.
  3. On the Body tab, choose JSON, Form Data or Raw. GET, HEAD and OPTIONS show a note instead of an editor because no body is sent with them.
  4. On the Auth tab, set Type to Bearer Token or Basic Auth and the Authorization header is written for you.
  5. Click Send or press Enter in the URL box. The response area shows status, time and size, with Body and Headers tabs. If you get a status you do not recognise, look it up in the HTTP status code list.

Example: copying a POST as a curl command

Set the method to POST, the URL to https://api.example.com/items, Auth to Bearer Token with abc123, and the JSON body to {"name":"Ada"}. After sending, Copy as cURL gives you:

curl \
  -X POST \
  'https://api.example.com/items' \
  -H 'Authorization: Bearer abc123' \
  -d '{"name":"Ada"}'

That command differs from what the browser sent in one way. Send adds Content-Type: application/json automatically for a JSON body, but Copy as cURL does not include it, and curl -d defaults to a form content type. Add the header on the Headers tab first and it will appear in the copied command. To turn a curl command into application code, use the cURL to code converter.

What the browser will not let you do

The numbers need care too. Time stops when the response headers arrive, before the body has finished downloading, and Size counts decoded characters, not bytes on the wire. JSON is parsed for pretty-printing, so very large integers change: a response of {"id": 12345678901234567890} displays 12345678901234567000. Copy Response gives you the original text.

Is my API key saved anywhere?

Request History is kept in your browser's localStorage and holds the method, full URL, status and timing of your last 20 requests. Headers, tokens and bodies are not saved. A key placed in the query string is part of the URL, though, and stays there until you click Clear all.

Why does clicking a history entry bring back only the URL?

Because only the method and URL are stored. Headers, body and auth settings stay as they currently are on the page, so check them before you resend.

It works in curl but fails here. Why?

curl does not enforce CORS and can set any header. If the API has no CORS headers and you cannot change the server, a browser page cannot reach it, and a command-line or desktop client is the better choice.