JSON Validator
A single misplaced comma can make a whole JSON document invalid, and the Power Platform is strict about it. Parse JSON fails, an HTTP action returns a 400 error or a connector rejects the request. This JSON validator checks the syntax of any JSON you paste and, when something is wrong, reports the line and column of the first error so you can fix it in seconds.
Also known as: validate json online, json checker, json syntax checker, check json, json lint.
Your data is processed locally in your browser and is not uploaded to our servers.
Features
- Strict JSON syntax check
- Line and column for the first error
- No upload, checked in your browser
- Works with large pasted input
How to use the JSON Validator
- Paste the JSON, or click Open file to load a .json file.
- Click Validate.
- If the JSON is valid you see a green confirmation. If not, read the line and column in the red message.
- Fix the problem in the input box and click Validate again. Repeat until it passes, because the validator reports one error at a time.
- Use Format JSON on the same page when you want the validated result in a readable layout.
Real-world use case: building a JSON body by hand in an HTTP action
Say you call a REST API from Power Automate and type the request body yourself, mixing text with dynamic content, such as a name property that holds the trigger's title. It works in testing. A week later the flow fails with 400 Bad Request. The reason is simple: someone typed a title that contains a quotation mark, which closes the string early and makes the JSON invalid.
Validating a sample of the final request body, copied from the action's inputs in the run history, shows the problem at once. The lasting fix is to stop assembling JSON from loose text. Escape quotation marks and line breaks in dynamic values, for example with replace(), or build the body as an object so Power Automate writes the JSON for you.
The same check helps in Power Apps. When you build JSON text in a formula with the & operator or Concatenate, a missing quote is easy to make. And when you use ParseJSON on text that came from a flow, validating a sample response first shows whether the problem is in your formula or in the data.
Remember what validation covers. It confirms the syntax, not the meaning. For Parse JSON schema errors, where the JSON is valid but does not match the expected shape, compare the formatted JSON with the schema, or regenerate the schema with Use sample payload to generate schema.
Example input and output
Input: a title with unescaped quotes
{"title": "Pump "A" check", "count": 3}Result after clicking Validate (wording varies by browser)
Invalid JSON at line 1, column 18: Expected ',' or '}' after property value in JSON at position 17 (line 1 column 18)
Fixed input
{"title": "Pump \"A\" check", "count": 3}
// Valid JSON.Frequently asked questions
How do I check if JSON is valid?
Paste it into a JSON validator and click Validate. A valid document shows a confirmation, and an invalid one shows the line and column of the first problem.
What are the most common JSON errors?
Trailing commas, single quotes instead of double quotes, property names without quotes, unescaped quotation marks inside text, and comments, which JSON does not allow.
Does valid JSON always work with Parse JSON?
No. Valid syntax only means the text can be read. Parse JSON also needs the data to match the schema you gave it, so a missing property or a different type can still cause an error.
Why use PowerApps Ninja?
Request bodies and API responses often contain customer names, IDs and internal fields. PowerApps Ninja validates in your browser, so nothing is uploaded, logged or stored. Because the page is written for Power Platform work, the examples show real flow problems rather than generic textbook errors.