For API teams approaching a sunset date
“Notified” is not
“ready.”
Give every API consumer one private, irreversible readiness commitment. Keep silence visible. Freeze the exact migration standard before the old version goes dark.
No API keys, traffic logs, customer records, or private endpoints. VersionPact records declared readiness; it does not verify production traffic.
One bounded contract
The missing layer between a changelog and a shutdown.
- 01
Freeze the sunset
Lock the public migration source, old and target versions, deadline, and evidence standard.
- 02
Issue private links
Each named consumer team receives its own capability link. No account or contact upload.
- 03
Commit once
Ready or blocked, with a bounded evidence note. A commitment cannot be overwritten.
- 04
Keep silence visible
Pending stays pending. The final receipt never turns an unanswered invite into approval.
Return without an account
Rotate private workspace access.
The original paid Checkout Session proves entitlement. The current recovery key authorizes one rotation and is replaced.
VersionPact coordinates declarations. Your team still owns traffic analysis, compatibility testing, support, and the final shutdown decision.