We request that you provide us with complete working example calls to your API to access rates, and the final price payable on your website (inclusive of provisions, fees, taxes, etc.). You should also include the breakdown of the final rate into different items (base rate, taxes, fees, etc.) For multiple-day stays, you shall provide the total price for all nights.
You will provide appropriate endpoints, IP addresses, passwords and user names in order to allow Skyscanner access to the API as well as sufficient documentation for Skyscanner to access and integrate with the real-time API. You will also provide the required parameters and information from your inventory which will be used in the availability API.
In addition:
- You agree to allow API requests from Skyscanner IP ranges. These will be provided in a separate document and Skyscanner may add ranges from time to time, if this happens you will be notified
- You agree that you will respond to as many API requests as possible in under 10 seconds.
- Skyscanner may ignore any API responses which take longer and this may impact visibility, traffic and revenue for you.
- You will provide a real-time availability and pricing API which supports the requirements described below:
The searching availability and pricing request must support a way of identifying the collection of relevant hotels either as a list of hotel identifiers or a unique location identifier (i.e. city identifier), provided that all the hotels in the catalogue provided by you have a location identifier provided in the catalogue.
You should also support the following inputs for the search availability and pricing request:
- Check-in date
- Check-out date or number of nights
- Number of guests (unless maximum occupancy output is provided in the response)
- Desired language
- Desired currency
- Number of rooms
- Number of adults and children specifying where possible the ages of the children
- An explicit distribution of guests in the different rooms
The search and availability pricing response must fulfill all criteria included above as follows:
- Hotel identifier (as included in the catalogue)
- Minimum price for the specified inputs
- Currency used for pricing
- Maximum occupancy for each room type. If maximum occupancy is not provided, the response should only contain groups of rooms that are guaranteed to match the input criteria
- Room name for each available room type
- Optionally, room description for enhanced user understanding
- If possible, provide a rule or guideline for mapping the room to Skyscanner supported room types. This would help streamline the booking process
- Skyscanner supported room types include: SINGLE, DOUBLE, TWIN, TRIPLE, SHARED, FAMILY, SUITE, JAPANESE_STYLE_ROOM, and ROOM_TYPE_JAPANESE_BED_ROOM
Where possible, the response should also support the following output fields:
- Cancellation policy, including details on whether free cancellation is included in the price and any associated deadlines
- Penalties and other conditions related to cancellations or modifications
- Inclusion of amenities such as breakfast, half board, full board, or all-inclusive packages in the price
- Availability of a deeplink for direct access to the booking page. In cases where direct deeplinking is not feasible using solely the hotel ID and/or location ID, alternative methods or additional information required for deeplinking should be provided
- Payment type accepted by the partner
- Price before any discounts or promotions are applied
- Daily price breakdown, if feasible for the partner to provide
Please Note: The minimum price we receive in the response must match the price available to the user after redirect. If we detect pricing issues in our testing phase we will be unable to release the integration to our live environment. Please ensure your API offers accurate pricing. We also have a specific price policy that is dependent on the point-of-sale market. Please review this policy and ensure you are compliant with this prior to the integration