API Versioning Without Breaking Existing Clients
Once other apps depend on your API, you cannot simply change it whenever you like — a change could break every integration overnight. Versioning lets you evolve the API while keeping existing clients working.
It is the professional way to improve a product over time without forcing every partner and app to update on your schedule.
How Versioning Protects Integrations
By publishing changes under a new version while keeping the old one running, existing clients carry on untouched. They move to the new version when it suits them, not when it suits you.
- Old apps keep working after improvements ship.
- Partners migrate on their own timeline.
- Breaking changes are clearly signposted in advance.
Retiring Old Versions Gracefully
Versions are not kept forever. We give clear notice, a generous window and migration guidance before an old version is finally switched off.
Not Every Change Needs a New Version
Adding a new, optional field rarely breaks anything, so it can usually go into the existing version. We reserve new versions for changes that would genuinely break existing clients, such as removing or renaming something they depend on. This keeps the number of versions you have to support manageable while still protecting your partners from nasty surprises.
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.