{"id":3133,"date":"2026-11-02T09:03:13","date_gmt":"2026-11-02T03:33:13","guid":{"rendered":"https:\/\/www.smsgatewaycenter.com\/blog\/?p=3133"},"modified":"2026-11-02T09:03:16","modified_gmt":"2026-11-02T03:33:16","slug":"lossless-json-parsing-messaging-api-19-digit-ids","status":"publish","type":"post","link":"https:\/\/www.smsgatewaycenter.com\/blog\/lossless-json-parsing-messaging-api-19-digit-ids\/","title":{"rendered":"Lossless JSON Parsing for Messaging APIs: 19-Digit IDs, Mixed Types and JSON Inside JSON"},"content":{"rendered":"\n

A messaging API can hand you the same transaction ID as a quoted string on one endpoint and a bare 19-digit number on the next. Default JSON parsers in JavaScript, jq and several Java and Go setups round that number silently. Here’s how to read SMS, WhatsApp, RCS and voice responses in Python, Node.js, Java and shell without losing a digit.<\/p>\n\n\n\n

\"Abstract<\/a>
Nineteen digits in, nineteen digits out: the job of a lossless parser.<\/figcaption><\/figure>\n\n\n\n

Table of Contents<\/h1>\n\n\n\n
    \n
  1. The Short Answer<\/a><\/li>\n\n\n\n
  2. TL;DR<\/a><\/li>\n\n\n\n
  3. Why a Correct Parser Still Corrupts Your Data<\/a><\/li>\n\n\n\n
  4. The Same Field, Two Types: A Map of the Responses<\/a><\/li>\n\n\n\n
  5. What a Double Does to a 19-Digit ID<\/a><\/li>\n\n\n\n
  6. Language by Language: Where the Digits Go Missing<\/a><\/li>\n\n\n\n
  7. Python: Integers Are Safe, the Next Hop Isn’t<\/a><\/li>\n\n\n\n
  8. Node.js: Rescue the Source Text in the Reviver<\/a><\/li>\n\n\n\n
  9. Java: Read IDs as Text from the Tree<\/a><\/li>\n\n\n\n
  10. jq and Shell Scripts: Quote Before You Parse<\/a><\/li>\n\n\n\n
  11. JSON Inside JSON: Fields That Hold Strings<\/a><\/li>\n\n\n\n
  12. Reading the Envelope Without Trusting Its Types<\/a><\/li>\n\n\n\n
  13. Money and Rates: Decimal, Never Float<\/a><\/li>\n\n\n\n
  14. Timestamps: Numbers, Strings and Formatted Twins<\/a><\/li>\n\n\n\n
  15. Phone Numbers and PINs Are Text<\/a><\/li>\n\n\n\n
  16. Writing It Back: Storage, Logs and Outbound JSON<\/a><\/li>\n\n\n\n
  17. A Parsing Contract You Can Test<\/a><\/li>\n\n\n\n
  18. Decision Matrix: Which Fix for Which Stack<\/a><\/li>\n\n\n\n
  19. Implementation Checklist<\/a><\/li>\n\n\n\n
  20. Unspecified Behaviour and How to Code Around It<\/a><\/li>\n\n\n\n
  21. FAQs<\/a><\/li>\n<\/ol>\n\n\n\n

    The Short Answer<\/h2>\n\n\n\n

    Treat every identifier and phone number as text, decide that at one boundary in your code, and decide it by field name rather than by endpoint. Messaging APIs return the same concept with different JSON types: on SMSGatewayCenter, the SMS delivery report quotes uuId<\/code> as \"6358884679059916409\"<\/code> while the WhatsApp report sends uuId<\/code> as a bare number, 3917313917152021246<\/code>. A JavaScript JSON.parse<\/code>, jq 1.6, Gson into a Map<\/code>, or Go into an interface{}<\/code> turns that bare number into a double, and a double can’t hold 19 digits. You get 3917313917152021000<\/code> back, with no error.<\/p>\n\n\n\n

    The fix is small. In Python, the standard json<\/code> module already keeps integers exact; add parse_float=Decimal<\/code> for money. In Node.js 21 and newer, read context.source<\/code> inside a JSON.parse<\/code> reviver. In Java, read the Jackson tree and pull IDs out with bigIntegerValue()<\/code> or textValue()<\/code>. In shell, quote long integers before jq sees them. Then store IDs in TEXT<\/code> columns, money in NUMERIC<\/code>, epoch milliseconds in BIGINT<\/code>, and decode JSON-in-a-string fields exactly once.<\/p>\n\n\n\n

    TL;DR<\/h2>\n\n\n\n