Commons API

STATIC DATA

There are plenty of data that doesn't change that often like a Hotel's name, its address and coordinates, the points of interest of a city and etc. To reduce all the static data we send within our dynamic responses, the Commons API was created. 

The process of migrating this kind of data currently returned on our SOAP API is still an ongoing process and therefore, we strongly suggest that any and all data found both on the Commons API and the SOAP API, should be consumed from the Commons API. As we move on with our process, less and less static data will be available through our SOAP API.

1. Where can you get our Static Data?

The links below hold the files with all the Destinations Ids (part of the SearchAvailability.Criteria and mandatory for building the SearchAvailability Request) and Hotel Data that we have available.

These files are automatically updated every two weeks and will always be available at the addresses above.

2. How should you work with our data?

We have two services available for integrating partners to work with when it comes to accessing our data. Those are:

There are a few possible flows to work with our Commons API, depending on your goal. On the image below we display an example of how you could use our services to choose a destination, make a search on that destination and retrieve the hotel details of the desired hotel.

Further details on how each of the services in our Commons API work can be found in their respective pages: Autocomplete and HotelDetail.

After finishing understading how our Commons API and Static Data work, is time to build your SOAP Request.