How to Format and Validate a JSON API Response

The scenario

You call an API and get a single line of dense JSON back. The fields are there, but they are hard to scan. Before you can debug the response, write code against it, or paste a sample into documentation, you need to see the structure clearly.

The usual workflow is simple: paste the response, format it, fix any parse errors, inspect nested fields, and minify the result only when compact output is useful.

Start with a raw response

Here is a typical single-line API response from a user endpoint:

{"user":{"id":42,"name":"Ada Lovelace","email":"[email protected]","roles":["admin","editor"],"profile":{"bio":"Mathematician and writer","joined":"2024-03-15T10:30:00Z"}},"meta":{"request_id":"req_8f3a","response_time_ms":47}}

This is valid JSON, but it is not pleasant to inspect. You cannot quickly see how deeply nested the profile object is, or whether roles is an array or a string.

Format the JSON

Paste the raw response into the JSON Formatter input panel and click Format. The output appears with proper indentation:

{
  "user": {
    "id": 42,
    "name": "Ada Lovelace",
    "email": "[email protected]",
    "roles": [
      "admin",
      "editor"
    ],
    "profile": {
      "bio": "Mathematician and writer",
      "joined": "2024-03-15T10:30:00Z"
    }
  },
  "meta": {
    "request_id": "req_8f3a",
    "response_time_ms": 47
  }
}

Now the structure is visible. user has five fields, roles is a two-element array, and profile is a nested object with a timestamp. The meta block sits alongside user at the top level.

Open JSON Formatter →

Common parse errors and how to fix them

If a formatter says the input is invalid, the payload probably contains one of these problems.

Trailing commas

{"name": "Ada", "roles": ["admin",]}

The comma after "admin" is valid in some JavaScript contexts but not in JSON. Remove it.

Single-quoted keys or values

{'name': 'Ada'}

JSON requires double quotes around keys and string values. Replace single quotes with double quotes before validating.

Comments

{
  // user info
  "name": "Ada"
}

JSON does not support comments. If your source format allows comments, such as JSONC or JSON5, remove comments before validating as standard JSON.

Extra text around the payload

Response: {"name": "Ada"}
OK

Log output or debug wrappers around the JSON body will cause a parse failure. Extract only the part between the outer braces or brackets.

When to minify JSON

Minified JSON strips whitespace. It is useful when you are storing JSON in an environment variable, embedding a request body in a curl command, comparing compact payloads, or serving production API responses with HTTP compression.

Formatted JSON is better while debugging. Minified JSON is better when the structure is already known and compact output is the goal.

Related workflows

After formatting a JSON response, you might want to decode a token with the JWT Decoder, inspect an encoded field with the Base64 Decoder, compare two responses with the Diff Checker, or generate a SHA-256 hash for cache comparison.

FAQ