Updated September 1, 2026
JSON Diff Change Types
JSON diffs are easiest to review when every change is tied to a path. This reference explains the change labels Utilumo reports.
Change labels
| Change type | Meaning | Review before copying |
|---|---|---|
added | The path exists only in the right JSON. | Check whether a new field is expected by the receiving API or schema. |
removed | The path exists only in the left JSON. | Confirm the removed field is not required downstream. |
changed | The path exists on both sides, but the value changed. | Compare the before and after value and look for formatting-only changes. |
type-changed | The path exists on both sides, but the JSON type changed. | Treat as higher risk because strings, numbers, arrays, and objects are not interchangeable. |
Arrays are index-basedA local JSON diff cannot always know whether an array item moved or changed. Index-based comparison is predictable, but moved items can appear as changed paths.
References
Questions
What is a JSON diff path?
It is the object key or array index where a change was found, such as $.user.name or $.items[2].
Why are type changes risky?
A downstream API or parser that expects a number may reject a string, even if the displayed value looks similar.