JSON formatting: syntax, types and safe identifiers
Revised 2026-10-09 · Synthetic examples
A response can be valid JSON and still be unsafe to convert. Start with the original response body; formatting cannot decide which business value is correct.
Test input and settings
{"status":"pending","status":"paid","orderId":9007199254740993}Open the tool and follow the steps belowSeparate syntax from data conflicts
Paste the sample into the JSON viewer and choose Format. Both status members and every orderId digit should remain. Read the duplicate-key and numeric precision warnings before sending the result to another tool. A parser that keeps the last key can hide pending; a JavaScript Number can round the ID.
Repair at the source, then check the contract
Do not delete a status by guessing. Ask the producing service which value is authoritative. If the contract defines orderId as an identifier, emit it as a string at the source. Quoting an already rounded value cannot recover the original. If the value is a quantity, agree on a precision-capable consumer instead.
Choose the next check
For a syntax error, use the reported location and check the original response for an HTML error page or trailing comma. For a valid document with the wrong field type, use JSON Schema. Compare the corrected and expected documents with JSON Diff. Preserve the original bytes separately when a signature is involved.
Completion criteria and limits
Done means the producer and consumer agree on the field meanings, the schema passes, and the intended change is visible in a comparison. A green syntax check alone is insufficient.
Back to tasks and guides · Report an incorrect instruction or result