Versioning

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 ContentAPI v2.0 next year.

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

Changelog

This is the list of changes ContentAPI had so far:

2018-09-07

  • hotel operations: added lastUpdate field in response.

2018-07-30

  • hotel operations: added ranking field in response.

2018-06-29

  • hotelDetails: multiple hotel codes per request.

2018-06-15

  • hotelDetails: state field in ContentAPI

2016-07-13

  • rateCommentDetail: Changed operation name to rateCommentDetails.

2016-04-29

  • hotel operations: Added the following filters: allIncluded, categoryCodes, categoryGroupCodes, photoNumber, imageTypes, languageDescriptions, accommodationTypes, boardCodes, segmentCodes, rooms, roomCapacity, chainCodes, newFrom, S2C, TripAdvisorRanking, merchant/liberate.

Docs Navigation