JsonForge · JSON errors
Unexpected number in JSON
A leading zero. JSON numbers may not have one, so 01, 007 and +1 are all rejected.
Zero-padded identifiers — postcodes, phone prefixes, invoice numbers — belong in a string, not a number.
The smallest input that causes it
{"a": 01}JSON.parse on that gives, verbatim:
Unexpected number in JSON at position 7 (line 1 column 8)
The fix
{"a": 1}That version parses.
Find it in your own document
Paste the JSON and get the error located by line and column, the document formatted, a schema inferred from it, and a diff against another version.
Open JsonForgeOther JSON errors
- Unexpected end of JSON input
- Unexpected token '<', "<html>" is not valid JSON
- "undefined" is not valid JSON
- Expected double-quoted property name in JSON
- Expected property name or '}' in JSON at position 1
- Single quotes are not valid JSON
- Unexpected non-whitespace character after JSON
- Bad control character in string literal in JSON
- Bad escaped character in JSON
- Unterminated string in JSON