OPENLINKER SERVICE · INTEGRATION ASSURANCE
Your official integrations, kept working through API changes.
Marketplaces and carriers change their APIs. Integration Assurance is a contractual commitment to keep eligible official OpenLinker integrations working against supported upstream changes — so a client's channel doesn't quietly break.
What's eligible
- In the main OpenLinker repository
- Built or formally maintained by OpenLinker
- Unmodified
- On a supported release
- Named in the service order
We don't publish an "assured" list yet — eligibility comes from the product registry, per deployment.
What it doesn't cover
- Agency forks and modifications
- Community adapters we haven't adopted for maintenance
- Experimental features unless expressly included
- Unsupported versions
- Third-party provider outages
- Suspended credentials or merchant-caused rate limits
- Capabilities a provider removes permanently without a replacement
WHAT COUNTS AS A BREAKING CHANGE
What counts as a breaking change
Endpoint or field removal or rename, new mandatory validation, an authentication change, a webhook or pagination change, an API-version retirement, materially changed response semantics — any change that causes a previously supported capability to fail.
HOW WE RESPOND
How we respond
- Announced, ≥30 days' notice
- We target a compatible release at least ~10 business days before the upstream deadline — provided the vendor supplied adequate documentation, test access and enough notice.
- Less than 30 days' notice
- We start promptly and target a release before the deadline; the 10-business-day buffer doesn't apply.
- Unannounced production break
- Your chosen SLA governs the initial response and communication; a workaround and permanent fix are targets.
Response and communication are contractual. Workaround and permanent-fix windows stay targets until we have enough incident history.
Let's scope it.
Tell us which integrations are business-critical for the client and we'll match scope and level.