Original (A)
Waiting for input.
Changed (B)
Differences
A text diff on two payloads is nearly useless: reformat one of them and every line changes. This compares them structurally, so key order is irrelevant and only real differences are reported, each with the path that reached it. The same comparison can be exported as an RFC 6902 JSON Patch to send to a PATCH endpoint, or an RFC 7386 Merge Patch.
Key order is ignored, so reformatting or reordering a payload is correctly reported as no change.
Each difference names the exact location inside the document, so you know where to look.
Compare arrays by index, or as unordered bags where a reordered list counts as identical.
Export the comparison as an RFC 6902 JSON Patch or an RFC 7386 Merge Patch, ready to send.
No. Two objects with the same keys and values are identical regardless of the order they were written in, which is what the JSON specification says and what a text diff gets wrong.
JSON Patch (RFC 6902) is a list of add/remove/replace operations with pointers — precise, and able to target array elements. Merge Patch (RFC 7386) is a partial document where null means "delete this key" — simpler, but it replaces arrays wholesale.
Yes, and it is the common case: paste yesterday's response and today's to see exactly what a deployment changed.