DEBUGGING PLAYBOOK · REVIEWED 2026-10-08

A response changed type

A number can become a string or an empty list can become an object. Both documents still parse, but the consuming application may fail.

Sample input

{"count":1,"items":[]}

Steps and checks

  1. Load the sample into JSON A. Set JSON B to {"count":"1","items":{}}.
  2. Differences appear automatically: /count changes from number to string, and /items from array to object.
  3. Replace B with {"items":[],"count":1}. The comparison now reports equality because object property order is ignored.

Reference result

A: {"count":1,"items":[]}
B: {"count":"1","items":{}}
/count: 1 → "1"
/items: [] → {}

Avoid a misleading conclusion

Arrays are compared by index; reordering can produce multiple differences. Duplicate keys and unsafe numbers block comparison. A blocked comparison must not be interpreted as equality.

What to do next

Check each difference against the contract. Use Schema validation for required fields and value constraints; retain raw text when exact bytes matter.

Related case and technical reference · Report an error or missing edge case

Continue this workflow

Compare JSON values without confusing types →

About this tool

Compares parsed JSON values, ignoring object key order and whitespace. Arrays are compared by index; array and object types remain distinct. Syntax errors, duplicate keys and risky numeric values block comparison.

How to use

Edit JSON A and JSON B to compare. Differences appear automatically. Paths use JSON Pointer notation: / separates segments, ~1 represents a slash inside a key, and ~0 represents a tilde.

Tips & Notes

A syntax error is not an empty difference. Correct diagnostics before interpreting results. Formatting and comparison do not validate an API schema.