Adamant Solutions

HTTP request tester with CORS diagnosis

Try an API call with your own headers, read the response and find out in plain words why a browser call fails. The request is sent by your browser: it never passes through our servers, so we do not see your URLs, headers or tokens. We only count anonymous visits (no cookies, no IP).

Use test endpoints and test credentials. Only call systems you own or are allowed to test. Browsers can reach only servers that allow cross-origin calls (CORS); the curl command works for everything else.

Sent from your browser, so the browser rules apply: some headers (Host, Cookie, User-Agent, Origin and others) cannot be set, and only response headers the server exposes are visible. The page shows the first 20,000 characters of the body.

How to use this tool

  1. Choose the method and enter the URL of an API you may test.
  2. Add headers (one per line) and a body if needed, then press Send.
  3. Read the response and the diagnosis. Copy the curl or fetch command for use elsewhere.

Example

Calling an API that does not send CORS headers shows "the server is reachable but the browser blocked the response: CORS", with what the server must add. A call to a server that is down shows a network diagnosis instead.

Limits

The browser sets some headers itself (Host, Cookie, User-Agent, Origin) and shows only response headers the server exposes. Servers that do not allow cross-origin calls cannot be called from a page; use the curl command.

Privacy and security of what you enter

Requests are sent by your browser directly to the server you enter. They do not pass through our servers, so we never see URLs, headers or bodies. The server you call sees your network address, as with any request. Use test credentials. See the privacy notice.

Calls blocked by CORS or failing behind a gateway?

We configure and review API gateways (WSO2 API Manager) and API security. See the WSO2 services or the security review.

Message us on LinkedIn