3rd-Party API Deprecation

Risk Statement: The provider removes or changes endpoints before we migrate, breaking core functionality and causing downtime.

Triggers / Signals:

• Deprecation notices from the provider
• New major version or SDK release
• Increase in 404/410 errors or deprecation response headers
• Provider emails or roadmap updates indicating sunset dates

Likelihood: Medium

Impact: High – potential for service disruption and customer impact if not addressed.

Mitigations:

• Subscribe to provider changelogs and webhooks
• Implement abstraction layer or adapter to isolate 3rd-party APIs
• Plan and develop migration before sunset deadlines
• Use feature flags or toggles to switch between versions
• Write integration tests to monitor endpoints for breaking changes

Owner: Technical Lead / Product Owner

Residual Risk: Medium after mitigations and continuous monitoring.