Two snapshots. Only the changes that matter.
Compare two JSON datasets by a unique key. Get added and removed records plus field-level changes. Reordering rows does not count as a change; duplicate keys are rejected.
See a real example result
Calculated by the same tool engine on this fixed synthetic example. No account, payment or external provider call. Use the tool page to submit your own input.
Input · JSON
{
"key": "id",
"before": [
{
"id": 1,
"price": 20
},
{
"id": 2,
"price": 15
}
],
"after": [
{
"id": 1,
"price": 22
},
{
"id": 3,
"price": 10
}
]
}Output · JSON
Reveal the result to inspect the output format before using the tool.
What you receive
- Added and removed records with original row indices
- Changed fields with before/after values and presence markers
- Summary counts and reproducible hashes
Scope & limits
- Up to 500 rows per dataset; 64 fields and 128 KiB combined input.
- Every row needs a unique non-blank string or safe integer key. Numeric and string keys differ.
- Nested arrays are order-sensitive. Missing and null differ. No source is fetched or modified.
Use it in your workflow
- Supply two JSON datasets and a unique row key.
- Review the exact price before one paid call.
- Use added, removed and field-level changes in your workflow.
API schemas and request examples are on the tool reference. Read the authentication and payment guide.
Your data & delivery
Submitted input and result bodies are not stored by InvokePort. Operational metadata and hashes may be recorded. Do not submit credentials or unnecessary personal data.
Keep your exact original JSON. New confirmed purchases support hash-verified result recovery for 30 days through Purchases, without another payment. Recovery remains subject to tool availability and execution controls.
Delivery problem? Contact support with the request ID.