Versioning and Deprecated APIs
The services you integrate with keep evolving, and from time to time they retire old versions of their APIs. If an integration is not maintained, one of these changes can quietly break it.
This article explains what API versioning and deprecation mean and how we keep your integrations working through them.
Why APIs Change
Providers improve security and features, which sometimes means leaving older versions behind.
- New versions add features or tighten security.
- Old versions are marked as deprecated, then removed.
- Providers usually give notice before switching off.
- Behaviour can change subtly between versions.
How We Stay Ahead
A little vigilance prevents nasty surprises.
- We pin to a known, supported version.
- We watch provider announcements for deprecations.
- We test against new versions before switching.
- We schedule upgrades well before any cut-off date.
Frequently Asked Questions
How will we know an upgrade is needed?
We monitor provider notices and flag upcoming changes to you, with a clear plan and timeline before anything is switched off.
Is upgrading risky?
We test the new version alongside the old one first, so the switch is made only when we are confident it works.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.