Unexpected end when deserializing object. Path 'a', line L, position N.
This message comes from Newtonsoft.Json JsonConvert on Newtonsoft.Json 13.0.3 on .NET 8.0.30. In this registry it is produced by 1 distinct mistake. Positions in the real message vary with your input; the causes do not.
Causes
What produces this message
Unclosed object — unexpected end of JSON input
Input
{"a": 1Exact message: Unexpected end when deserializing object. Path 'a', line 1, position 7.
Fix: Verify you received the whole payload. Compare the byte count against Content-Length, and check for proxy or log truncation.
Same bug, other languages
What other parsers say about the same input
If a colleague reports a different message for what looks like the same file, this is why.
| Parser | Message for the same inputs |
|---|---|
| CPython json.loads | Expecting ',' delimiter: line L column C (char N) |
| Gson | java.io.EOFException: End of input at line L column C path $… |
| Gson JsonParser (lenient off) | java.io.EOFException: End of input at line L column C path $… |
| JSON5 | JSON5: invalid end of input at 1:8 |
| JSON::PP | , or } expected while parsing object/hash, at character offset N (before "…") |
| Jackson ObjectMapper | Unexpected end-of-input: expected close marker for Object (start marker |
| JavaScriptCore JSON.parse | JSON Parse error: Expected '}' |
| Ruby JSON.parse | unexpected token at '…' |
| SpiderMonkey JSON.parse | JSON.parse: end of data after property value in object at line L column C of the JSON data |
| System.Text.Json Deserialize | '1' is an invalid end of a number. Expected a delimiter. Path: $ | LineNumber: L | BytePositionInLine: C. |
| System.Text.Json JsonDocument | '1' is an invalid end of a number. Expected a delimiter. LineNumber: L | BytePositionInLine: C. |
| V8 JSON.parse | Expected ',' or '}' after property value in JSON at position N (line L column C) |
| encoding/json Unmarshal | unexpected end of JSON input |
| hjson | End of input while parsing an object (missing '}') at line L,7 |
| json-bigint | Expected ',' instead of '' |
| json_decode | Syntax error |
| orjson | unexpected end of data: line L column C (char N) |
| serde_json::from_str | EOF while parsing an object at line L column C |
| ujson | Unexpected character in found when decoding object value |
Sources
Standards this registry is checked against
- RFC 8259 (STD 90) — The JavaScript Object Notation (JSON) Data Interchange Format, T. Bray, Ed., 2017. The IETF Internet Standard for JSON. Obsoletes RFC 7159 and RFC 4627.
- ECMA-404, 2nd edition — The JSON Data Interchange Syntax, Ecma International, 2017. Ecma’s grammar for JSON. A normative reference of RFC 8259; the two define the same syntax.
- The Unicode Standard — The Unicode Standard, Core Specification, The Unicode Consortium, current. Normatively referenced by RFC 8259 for the definition of a character.
- IEEE 754-2019 — IEEE Standard for Floating-Point Arithmetic, IEEE, 2019. Referenced by RFC 8259 §6 as the basis for its interoperability guidance on numbers.
Only standards bodies and peer-reviewed venues are cited. Error strings on this site are observed by executing each parser; the standards above define what the parser is reacting to.