How to Read a Minified JSON API Response (5 Methods Compared)

API responses arrive minified by default. A response that's perfectly valid JSON is completely unreadable as a single line of thousands of characters. This guide covers the five practical methods for formatting one — no fluff, no "what is JSON" preamble — just which tool to reach for and when. For most developers, a browser-based formatter is the fastest option because it requires no installation, works on any operating system, and formats the response instantly.

Key takeaways

• Zero-setup path: paste into a browser formatter — done in under 5 seconds, works for any JSON source.
• Already in the browser: DevTools Network tab → Preview auto-formats for you.
• curl workflow: pipe to jq . for colour and filtering; python -m json.tool if jq isn't installed.
• Postman is overkill for just reading a response you already have.
• Privacy matters if the response contains customer data, tokens, or PII — use a client-side tool.

Which method should you use?

Method 1 — Browser formatter (fastest, zero setup)

Copy the raw JSON string from wherever you have it — a terminal, a log file, a Slack message — and paste it into the JSON Dev Tools formatter. Click Format. Done.

Why this is the default choice: no app to install, no account to create, works on any OS, and the formatter is client-side so your JSON is never uploaded. If the response contains real customer data or API tokens, this is the only online method that doesn't expose it to a third party. The same tool validates as it formats, so you also see parse errors immediately.

Limitation: you need to have the response text to paste. If the response came from a browser request you can't easily copy, use Method 2 instead.

Method 2 — DevTools Network tab (already in the browser)

If the API request happened inside your browser (a fetch call, an XHR, a page load), the response is already in DevTools and already pretty-printed:

1. Open DevTools: F12 on Windows/Linux, Cmd+Option+I on macOS.
2. Go to the Network tab. Refresh the page or trigger the request.
3. Click the relevant request in the list.
4. Select the Preview sub-tab — the browser renders the JSON as a collapsible tree.
5. Select the Response sub-tab to see the raw text you can copy.

Why use this: no copy-paste required; the browser did the work. The tree view lets you navigate deeply nested objects without formatting at all. This is the fastest path when you're already debugging in the browser.

Limitation: only works for requests the browser itself made. Doesn't help with curl output or responses from another machine.

Method 3 — jq (best for curl + terminal workflows)

jq is a command-line JSON processor that pretty-prints by default and can also filter, transform, and query.

# Format a curl response
curl -s https://api.example.com/data | jq .

# Extract a specific field
curl -s https://api.example.com/data | jq '.user.email'

# Format a local JSON file
cat response.json | jq .

Install: brew install jq (macOS), apt install jq (Debian/Ubuntu), or download from jq's official site. Once installed, jq . is the fastest terminal command for reading any JSON.

Limitation: requires installation. If you're on a machine where you can't install packages, use Method 4.

Method 4 — Python one-liner (no install beyond Python)

Python ships with a JSON formatter in its standard library. If Python is available (it's on most developer machines and all macOS/Linux systems), no additional install is needed:

# Pipe curl output through Python
curl -s https://api.example.com/data | python3 -m json.tool

# Format a file
python3 -m json.tool response.json

# On older systems
python -m json.tool response.json

json.tool formats with 4-space indentation by default. To change it: python3 -m json.tool --indent 2 response.json. It also validates — if the JSON is malformed, it prints a clear error instead of silently mangling the output.

Method 5 — Postman (only if you're also sending the request)

Postman automatically pretty-prints JSON responses in its response panel. But Postman's value is in building and sending requests. If you already have the JSON response, opening Postman just to format it adds more steps than it removes.

Use Postman when you're already making the request from Postman. If you just have the response text from somewhere else, reach for any of the other four methods instead.

All five methods compared

What about responses that contain sensitive data?

If the response contains personal data, API tokens, or customer records, the safest online option is a client-side formatter that processes the JSON entirely in your browser — like JSON Dev Tools, where the response is never uploaded to a server. For a full explanation of how to verify whether any tool is genuinely client-side, see is it safe to paste JSON into an online formatter?