Most developers have experienced the frustration of a sudden API version deprecation at an inconvenient time.
Sometimes it's understandable - for instance a security risk has been found - but often it's really not. The company running the API just decided they needed to make a change and you need to deal with it...
So, as developers ourselves, we've made it our goal that our API isn't the cause of this hassle!
Our Long Term Support Commitment means we will make our best effort to always support every past version of our API.
Even when there is only a single remaining customer still converting currencies using Version 1 of our API, they won't need to change their integration unless they want to.
We'll ensure uptime on that endpoint with the same care as usual.
Because this requires quite a bit of work behind the scenes - e.g. moving old code to new infrastructure, changing caching layers to handle updated exchange rate data sources - only paying customers benefit from our Long Term Support efforts.
We're proud of our track record on this. We have never deprecated an endpoint or API version still used by a paying customer since we launched in 2010!
Unfortunately due to very high volumes of free users it isn't feasible to offer LTS for our free plans and open access endpoints. If you've ever managed legacy infrastructure or legacy code you'll know there is a real cost to keeping this sort of commitment. This is one of the reasons free APIs sometimes disappear from the internet without warning...
Our Long Term Support Commitment aims to support everything as it was when you made your integration. This includes the feature set of previous versions of our API, the endpoints associated with those versions, the actual formatting and headers of the API responses that are sent and even the original data refresh interval.
V1 (added 2010), V3 (added 2014), V4 (added 2018), V5,V6 (added 2019) and V7 (the current version) of our API are all still supported for users who integrated with these editions of our product. If you have any questions about a previous version of our API please contact support.
If you're doing a partial upgrade but leaving some code using a legacy API endpoint we have good news for you! Your API key will work with all versions of our currency converter API - no need for juggling credentials, our version-agnostic authentication makes upgrading easy.