Keep integrations running after the API is retired
A bridge accepts calls to the old API, performs them through the new one and answers in the old format. Your integration changes one URL and one credential. A coverage report shows exactly what translates, what only partly, and what does not.
EWS → Microsoft Graph
From 1 October 2026 Exchange Online blocks EWS for third-party apps unless the tenant allow-lists them; after 1 April 2027 EWS access is removed for good.
HubSpot legacy → date-based API
HubSpot’s /v1, /v2 and /v3 APIs become unsupported in September 2027; new legacy private apps stop being available in autumn 2026.
How it works
1. Point the client at the bridge
Replace the endpoint and the credential with a bridge key. Nothing else in your code changes.
2. The bridge translates
Each call is performed through the new API and answered in the old protocol, with the error codes clients already handle.
3. Honest coverage
Anything not translated gets a clear protocol error and a line in your gap report — never a silent empty success.
Privacy
The bridge keeps no message bodies, addresses, contacts or CRM records. Coverage events hold the operation name, status, reason and latency — nothing else.