The following information is true for every type of request
You will receive a private key from us that will be used for authentication. To make the key stronger we will use a salt that will be total minutes elapsed since 1 Jan 1970 00:00, also known as Unix time (note that use minutes and not seconds).
We are concatenating our secret key, for example "DarthVader", with total minutes elapsed from 1970 until now, 24272143 as I'm writing this and we get "DarthVader24272143".
Now that we have our salted key we will encript it using SHA-1 algorithm, and this will render a hexadecimal number, 40 digits long. For our little example the result will be "f595d10fa50123c3a82c85f538d7d72092907bfa". This will be your acces token to be placed in every request's header along with your username.
For this to work your machine must have the correct date and time set, otherwise you'll get another salt for your secret key, resulting in a different access token. We know that time synchronization on servers can be harsh so we will tolerate a +/-5 minutes difference, but not more. Pretty simple, huh?
Hotel details like description, pictures, address etc rarely change, that's why it is ok to download static data once, update it from time to time and use those hotel details in your website. This way we will not send these on our Booking Flow API, allowing us to have a light and fast Booking Flow API.
Please take a look at our sandbox for static data following the link below. From there you can make requests to our demo api and you'll also find the documentation about the request and response parameters.
The flow for downloading static data is simple and intuitive.
Our REST API provides you the ability to choose between xml and json request/response. We have full integration support for multiple programming languages providing you with already created API clients in order to have a smooth integration process. In order to minimise the scenarios where the price and availability change during the booking flow all the requests are made directly at the suppliers therefore our booking flow is live one.
Please take a look at our booking flow sandbox following the link below. From there you can make requests to our demo api and you'll also find the documentation describing all the parameters. Note that some parameters from our request example must be modified with real values obtained from previous request. For example on a CheckRates request you should replace the RoomGroup elements with real values obtained from HotelAvailability request.
Here is how a 3 steps booking should be created:
After a booking is confirmed you have the posibillity to cancel it or to retrieve its details