↑↓ to move · Enter to open · Esc to close

API Response Viewer

Point this API response viewer at an endpoint and it fetches the URL with a GET, then shows the status, the timing, the response headers, and a JSON body as a tree you can fold open.

This request runs on our server. The address, headers, and body you enter are used only for this request and are not stored.
Built and reviewed by · Updated
Request headers (optional)

Headers such as Authorization pass through our server to the address you enter. They are not stored. Host, Content-Length, Connection, Proxy-*, and User-Agent cannot be set.

Tick the box to show you are not a robot, then press Fetch.

How to use the API Response Viewer

  1. Enter the endpoint, for example https://jsonplaceholder.typicode.com/todos/1.
  2. Add a request header if the API needs one, such as Accept: application/json or an API key.
  3. Tick the robot check and press Fetch.
  4. Open nodes in the tree with a click or the arrow keys. Copy or download the raw body from the buttons above it.

How it works

Your browser cannot read most APIs on other sites directly, because they do not send the CORS headers that would allow it. So the request is made by our server instead, and the reply comes back to this page as data.

Before connecting, the server checks the address: only http and https on ports 80 and 443, and only public IP addresses, so the tool cannot be aimed at a private network. Up to five redirects are followed, each one checked the same way. The body can be up to 2 MB.

The page then looks at the Content-Type. JSON is parsed without losing large numbers and drawn as a tree. XML is indented. HTML and plain text are printed as text and never rendered.

Examples

Fetching https://jsonplaceholder.typicode.com/todos/1, a free fake API for testing, returns status 200 and this body, shown as a tree with four keys:

{"userId": 1, "id": 1, "title": "delectus aut autem", "completed": false}

A URL that redirects, such as an http address that moves to https, lists the hop under Redirects followed and shows the final URL next to the status.

An image or a ZIP file is reported as binary with its size and type, and is not printed.

Limitations

  • GET only. To send POST, PUT, or a body, use the HTTP Request Tester.
  • APIs on localhost or inside your company network cannot be reached from our server.
  • The request comes from our server's address, so an API that limits by IP or by country may answer differently than it does for you.
  • Responses over 2 MB are refused rather than cut.

Frequently asked questions

Why not just open the URL in a new tab?

You can for a plain GET, but you get raw text, no response headers, and no way to add an Accept or API key header. The viewer shows all of that in one place.

Is it safe to put an API key in a header?

The key passes through our server to reach the API and is not stored or logged. Use a test key or a key with limited scope all the same, as with any online tool.

Why does the API answer 403 here but work in my app?

Your app may send a token, a cookie, or come from an allowed IP address. Add the same header here, and keep in mind that our server's address is not on your allowlist.

Often used together with API Response Viewer.

  • JSON Viewer

    Shows JSON as a collapsible tree with search and copyable paths.

  • HTTP Request Tester

    Online HTTP client for any method with query, headers, and body, plus a matching cURL command.

  • HTTP HeadersNetwork Tools

    Status, final URL, and response headers from one GET.