Do not paste secrets, API keys, access tokens, private customer data, or production credentials into tools you do not control.
Start by proving the JSON is valid
When an API request fails, invalid JSON is one of the easiest problems to rule out. Formatting the payload makes structure visible, while validation catches syntax issues before deeper debugging.
Syntax errors
Missing quotes, extra commas, unclosed brackets, and smart quotes can break parsing immediately.
Structure visibility
Pretty formatting makes nested objects and arrays easier to inspect.
Schema mismatch
Valid JSON can still be the wrong shape for an API. Syntax validation is only the first check.
Sensitive data
Redact tokens, keys, private IDs, and personal data before sharing or pasting examples.
A JSON debugging workflow
1. Paste a minimal payload
Start with the smallest JSON sample that still shows the issue.
2. Format the JSON
Pretty-print it so nested fields, arrays, and missing separators are easier to spot.
3. Validate syntax
Fix parser errors before checking API permissions, schemas, or business logic.
4. Compare with expected schema
After syntax passes, check required fields, value types, names, and nesting.
Format and inspect your JSON
Use the JSON editor to format, validate, and inspect payloads directly in the browser.
Open JSON editor常见问题
What does it mean to validate JSON?
Validation checks whether the text follows JSON syntax, including quotes, commas, brackets, braces, and value types.
Why does JSON fail after copying from a website or API?
Common causes include trailing commas, smart quotes, comments, missing quotes around keys, or copied text around the JSON.
Is it safe to paste sensitive JSON into an online tool?
Avoid pasting secrets, tokens, private customer data, or production credentials into any tool unless you understand how it handles data.