Why a large JSON integer can change
An order ID can be valid JSON yet change when an application turns it into a JavaScript Number. Formatting and calculating are different tasks. The example below uses 9007199254740993, deliberately one above the largest safe integer.
Input and result
JSON | {"id":9007199254740993} |
JSON.parse(...).id | 9007199254740992 |
Apps24 | { "id": 9007199254740993 } |
What the result means
JSON.parse converts this value to 9007199254740992. Apps24's formatter instead validates syntax and adds whitespace around the original tokens, so the digits stay intact. That is preservation of text, not proof that every consumer can represent the number. A green validation result checks syntax; it does not check an API schema, field types or duplicate names.
What to do next
Paste the example into the formatter and compare the ID before and after. If an ID is an identifier rather than an amount, agree a string representation with the API owner, such as {"id":"9007199254740993"}. Do not add quotes to every number blindly: that changes types and can break a schema. Check the consumer and database too.
Use the toolLimits and test conditions
Regression tests verify the exact digits, duplicate keys, exponent notation and string whitespace. The formatter neither repairs invalid JSON nor performs arbitrary-precision arithmetic. Never paste production secrets or access tokens.
References
Apps24 checks examples against the implementation and regression tests. Browser experiments state their conditions; they do not certify every device. Report an error with the page URL, input, expected result and browser. Never send passwords, private documents or personal data.