EAPI API calls generally include a version number, e.g.: /eapi/submission/send_sms/2/2.0

This is not a version in the sense that it is incremented each time changes are made. Rather, it is incremented only when changes are made to the API that are incompatible with previously published specifications.

Therefore, by using a specific API version, you are guaranteed that no backwards-incompatible changes will be made. However, this does not preclude new features being added to the API version that you are using, or changes being made which we deem to be compatible with published specifications.

In principle, older API versions are maintained indefinitely. We do however reserve the right to disable such old API calls as we consider to have fallen into disuse.

In the past, we used a slightly different versioning scheme, which included the use of /current in URLs. This scheme is no longer used; however, as usual, such older URLs as used to function in this format will continue to be available.