Online API tester

A lightweight REST client in your browser. Send a request with any method, headers, authentication and body, then read the status, timing, headers and formatted response.

One header on each line, as Name: value.

Good to know: requests are sent straight from your browser, so the API must allow cross-origin requests (CORS). Public APIs usually do. Private or internal APIs often do not, and those are better tested with the cURL command shown after you send a request.

How to use the API tester

  1. Choose the method and enter the full URL, starting with https://.
  2. Add headers, authentication or a request body in the tabs if the API needs them.
  3. Click Send. Read the status code, time, size, headers and response body, or copy the request as a cURL command.

HTTP methods at a glance

MethodUsed toHas a body
GETRead a resourceNo
POSTCreate a resource or run an actionYes
PUTReplace a resourceYes
PATCHChange part of a resourceYes
DELETERemove a resourceRarely
HEADGet the headers onlyNo
OPTIONSAsk which methods are allowedNo

Common status codes

CodeMeaning
200 OKThe request worked
201 CreatedA new resource was made
204 No ContentIt worked and there is nothing to return
301, 302The resource has moved to another address
400 Bad RequestThe server could not understand the request, often because of invalid JSON
401 UnauthorizedYou are not signed in, or the token is missing or wrong
403 ForbiddenYou are signed in but not allowed to do this
404 Not FoundThere is nothing at that address
429 Too Many RequestsYou have hit a rate limit
500, 502, 503Something went wrong on the server

Why a request can fail here but work in cURL

Browsers enforce a safety rule called CORS. A web page may only read a response from another site if that site sends an Access-Control-Allow-Origin header that permits it. If an API does not send that header, the browser blocks the response and this tool can only report that the request failed. That is a limit of every browser-based client that runs without a proxy server.

The upside is privacy. Your request goes directly from your browser to the API. It does not pass through our servers, so we never see your URLs, tokens or data. Two more limits apply: a page served over HTTPS cannot call plain http:// addresses (except localhost), and browsers do not let scripts set some headers, such as Host, Cookie and User-Agent.

Related: decode a token with the JWT decoder, tidy a response with the JSON formatter, or build test payloads with the mock data generator.

Frequently asked questions

Is this a free alternative to Postman?

For quick checks, yes. It sends requests with any method, headers, auth and body and shows the full response, with no account or install. It does not have collections, environments or team features.

Why do I get “Failed to fetch”?

Usually because the API does not allow cross-origin requests (CORS), the address is wrong, or the page is HTTPS and the API is plain HTTP. Try the generated cURL command in a terminal.

Are my API keys sent to your server?

No. Requests go directly from your browser to the API. Tokens and passwords are not saved in the history.

Can I test an API on localhost?

Yes, if your local server sends CORS headers. Browsers allow HTTPS pages to call http://localhost.