Learn how Partner API versions are managed and how to stay compatible.
The Partner API is versioned using a major version in the base URL.
All endpoints for a given version share the same base path.
Example base URL:
https://api.wetravel.com/v3Versioning policy
- Major versions (
v3,v4, ...) may include breaking changes, such as
removed or renamed fields, changed data types, or different behavior. - Breaking changes are never introduced within the same major version.
- Minor and patch changes are backward-compatible and typically introduce new
endpoints, optional parameters, or additional response fields. - Additive changes can occur at any time. Clients should ignore unknown
fields to remain forward-compatible.
Upgrading versions
When a new major version is released, update the base URL to the new version
and review the updated endpoint documentation for breaking changes.
Deprecation
When a major API version is deprecated, it will continue to be available
for a period of time to allow partners to migrate.
Deprecation timelines and migration guidance will be communicated in advance.