API deprecation and breaking change migration for providers.
Help consumers migrate when your API changes. Review release classifications and aggregate impact across connected installations while customer code stays private.
Review release classifications and aggregate impact across connected installations. Customer source and repository access remain private to each customer.
API compatibility questions
Who is the provider workspace built for?
API, product, and DevRel teams responsible for helping customers through API releases. The workspace combines specification changes, classification review, aggregate installation impact, delivery outcomes, and deprecation timelines.
What can we see about our customers?
Aggregate affected-installation counts and compatibility evidence for connected installations. Provider views do not expose customer identities, repository names, commits, or source snippets. Exact code impact stays in each customer’s workspace.
Why do some counts say fewer than five?
Small installation counts are suppressed to protect customer privacy. Counts below the threshold arrive without an exact number and are displayed as fewer than five. This is not the exact-count view available to a team for its own repositories.
Can our team review a classification?
Yes. The review queue supports approving a breaking or non-breaking classification, requesting more information, and rejecting a finding as a specification correction. Review decisions are recorded; the provider workspace is an action surface as well as an aggregate view.
Can we open fixes in a customer’s repository?
Customers control delivery modes for their repositories. Your workspace can show aggregate delivery outcomes, but provider access does not authorize writes to customer code. A supported fix must pass its validation gate before delivery.
Does impact include every customer of our API?
No. Impact reflects installations connected to paritydiff and supported usage analysis. It is not a census of your customer base. Missing or suppressed counts should not be treated as proof that nobody is affected.
How do providers get access?
Use Get a demo to send a request to Soumik, or contact him directly by email. We’ll walk through your API and release workflow, including public or private specification access authorized by your team.
Can we connect a private specification?
Yes. Upload a supported contract or connect an authorized HTTPS URL. Add credentials during setup for a private source. Preview shows the declared format and evidence; captured history retains revision and reference context. Specification credentials are stored encrypted, and private visibility is available for your API.
Can we preview the workspace before setup?
Yes. The provider preview and customer result follow one offline fixture release. Inspect the specifications, affected code, generated report, reference edit, and checks. Discuss a pilot with Soumik to review your own API and specification access.