JSON Schema Drift Detector — Catch Breaking Changes
Compare two JSON datasets and identify added, removed and changed field types.
JSON Schema Drift Detector — Catch Breaking Changes returns 7 documented output fields, including rows, summary, field, status and beforeTypes. Every field carries a declared type, a written description and an example value. 2 runs are recorded on Apify.
Run it on ApifyPay per result · no subscription
- 7
- Output fields
- 2
- Inputs
- 2
- Runs
- 2026-10-15
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| rows | string | number | boolean | array | objectnull | How many rows this item contributed. | 120 |
| summary | objectnull | Per-run counts: fields before and after, changes found, and a note on scope. | [] |
| field | string | number | boolean | array | objectnull | The field or attribute this row is about. | director_name |
| status | string | number | boolean | array | objectnull | Outcome recorded for this row. | ok |
| beforeTypes | string | number | boolean | array | objectnull | The types seen before the change. | string |
| afterTypes | string | number | boolean | array | objectnull | The types seen after the change. | string,number |
| demo | string | number | boolean | array | objectnull | Demo as recorded for this row. | [] |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"rows": 120,
"summary": "[]",
"field": "director_name",
"status": "ok",
"beforeTypes": "string",
"afterTypes": "string,number",
"demo": "[]"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| rows | arrayoptional | JSON rows to analyze. Use the example in the README for required fields. |
| datasetId | stringoptional | Optional Apify dataset ID used instead of inline rows. |
04 — run
Run JSON Schema Drift Detector on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
7 of 7 fields described
- What does JSON Schema Drift Detector — Catch Breaking Changes return?
- It returns 7 documented output fields: rows, summary, field, status, beforeTypes, afterTypes and demo. Each field declares its type, a description of what it holds, and an example value.
- What input does JSON Schema Drift Detector — Catch Breaking Changes take?
- All 2 inputs are optional and ship with usable defaults, so it runs as-is. They are listed with their types below.
- Does JSON Schema Drift Detector — Catch Breaking Changes need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run JSON Schema Drift Detector — Catch Breaking Changes?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.