OpenAPI Breaking Change Diff
Pricing
from $3.00 / 1,000 structured api changes
OpenAPI Breaking Change Diff
Compare two public OpenAPI JSON specifications and return an explainable, structured API change set.
Pricing
from $3.00 / 1,000 structured api changes
Rating
0.0
(0)
Developer
Guillermo Morán
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
11 days ago
Last modified
Categories
Share
Compare two public OpenAPI JSON specifications and export a deterministic, traceable API change set.
It is for API owners, SDK maintainers, QA teams, integration developers, and technical product teams that need an automatable answer to: what changed between these two API contracts?
What it does
- Fetches two public HTTP(S) OpenAPI JSON documents.
- Finds added, removed, and modified HTTP operations.
- Emits one structured Dataset item per change; identical specifications produce one
NO_CHANGESitem so automation can still consume the result. - Saves a
SUMMARYrecord with operation totals, change counts, and truncation status.
Why this Actor
- No LLM required.
- No paid API or login required.
- Deterministic comparison and explainable changed-field lists.
- Bounded output (
maxChangesis 1–500). - Useful from the Apify Console or API.
Input
{"beforeUrl": "https://petstore3.swagger.io/api/v3/openapi.json","afterUrl": "https://petstore3.swagger.io/api/v3/openapi.json","maxChanges": 10}
Both inputs must be public OpenAPI JSON URLs. YAML conversion and persistent monitoring are intentionally out of scope for this small Actor.
Output
Each Dataset row includes changeType, path, method, the old/new operation IDs, deterministic field-level details, and both source URLs. The default Key-Value Store SUMMARY record reconciles the result counts.
Privacy and limits
The Actor fetches only the two public URLs supplied in its input. It does not crawl API endpoints, collect user data, use browser automation, or retain data outside normal Apify run storage.