Versioning
The travel API is versioned by URL path. Endpoints are stable, and older paths keep working.
There is no date header and no version parameter. A path either carries a v2/ prefix or it does not. Where both exist, they are backed by the same booking engine, so you can migrate one endpoint at a time.
Authentication
Authentication exists at two paths. They are the same operation against the same session store, so a SessionId from either works everywhere. Pick one.
| v1 | v2 |
|---|---|
/Authenticate/CreateSession | /v2/Authenticate/CreateSession |
/Authenticate/EndSession | /v2/Authenticate/EndSession |
Flights
Flights have one version. Every path is under /Air/ with no version prefix.
Hotels
Hotels have both. The v2 path is the recommended one. It adds public place search and lookup, and richer availability. The booking endpoints are the same engine under both prefixes. New integrations should use v2.
| v1 | v2 | Notes |
|---|---|---|
/Hotel/cities/search | /v2/Hotel/cities/search | Public, no session. |
| - | /v2/Hotel/cities/lookup | v2 only. Public. |
/Hotel/HotelAvailability | /v2/Hotel/HotelAvailability | Same request shape. |
/Hotel/HotelCheckRate | /v2/Hotel/HotelCheckRate | Same. |
/Hotel/HotelBook | /v2/Hotel/HotelBook | Same engine. |
/Hotel/HotelOrder | /v2/Hotel/HotelOrder | Same engine. |
/Hotel/HotelCancelDisplay | /v2/Hotel/HotelCancelDisplay | Same engine. |
/Hotel/HotelCancel | /v2/Hotel/HotelCancel | Same engine. |
/Hotel/HotelBookingData | /v2/Hotel/HotelBookingData | Same engine. |
/Hotel/HotelExtendPaymentDeadline | /v2/Hotel/HotelExtendPaymentDeadline | Same engine. |
Activities
Activities exist only at /Activity/v2/. There is no v1.
Deprecation
Nothing is deprecated today. The v1 hotel paths stay available for existing integrations. When an endpoint is ever retired, it will appear on the changelog with a Breaking label and a migration note before it is removed.