Versioning

API release versions

Our API code releases follow semantic versioning methodology to provide as much clarity as possible regarding API versions and backward compatibility (for more information see https://semver.org/). During the BETA phase we allow for breaking changes. After the first final release we will keep the API backward compatible as best as possible.

Examples: 1.2.3 , 2.5.8

API url versions

We use versioning in our API urls to allow for multiple api versions to evolve over time. This version number is unrelated to the API release version mentioned above. When we increase this version number this means backwards compatibility is no longer guaranteed.

URL Structure: /[product]/api/v1/some/url The v1 part represents the major version of the API.

Examples: hotelxv/api/v1, hotelxv/api/v2