We will up-version our APIs when: 

  • we change the format of the response data for one or more calls
  • we change the response type (i.e. changing an integer to a float)
  • we remove any part of the API.

We will NOT up-version for non-breaking changes such as:

  • adding new response fields 
  • adding new endpoints/operations
  • adding new optional paramethers in the requests
  • changing the order of properties in existing API responses.
  • changing the length or format of strings. 

Upcoming changes

We will be releasing BookingAPI v2.0 next year.

Stay tunned to know the incoming changes in advance and be prepared! 


This is the list of changes BookingAPI had so far:


  • New allotment control: error returned when clients request more allotment than the available one.


  • BookingChange operation now available.
  • New parameters to filter in BookingList operation: filter by clientReference, by Hotels, by zones and by destinations. 


  • Confirmation v1.2 released: response is compressed when the request have the Accept-Encoding header 


  • Availability number of rooms that can be requested increased from 5 to 10


  • Booking List  "from" and "to" limit increased from 25 to 100 bookings. 
  • Changed several INVALID errors that were incorrectly being returned with the 500 error code to 400.
  • Changed PRODUCT_EXCEPTION errors from 500 to 503 error code. 

Docs Navigation