To ensure a smooth and reliable integration, please review the technical checklist below. This checklist outlines the key data points and configuration requirements that must be provided for successful API connectivity.
For more in-depth explanations, examples, and troubleshooting guidance, refer to the detailed documentation available in this helpdesk. The information below serves as a high-level overview of the essential prerequisites and best practices to help you self-validate your integration setup effectively.
Availability API
Full Requirements can be found in this link
- Production environment API (testing environment is not supported)
- API Format: One of the following formats is supported-JSON, XML, or SOAP
- API request must include hotel ID (preferred) or city code (catalogue must include this information)
- Other required parameters for API request. Check this link for more details.
- Other required parameters for API response. Check this link for more details.
- Skyscanner IPs allowed access (if required). These will be provided during the integration.
- Booking page depth (the page before the payment page. This is optional but preferred for a better user experience)
- Do not include credentials or any "skyscanner" references in the deeplinks
- Ensure the price in the API response matches the landing page
Hotel Inventory/Catalogue
Full Requirements can be found in this link
- Hotel Inventory is a separate environment from the Availability API (We aren't able to support if we have to consume inventory content in the same Availability API).
- Supported Methods: One of the following formats is supported-SFTP, API, or Static Downloadable Link
- File Format (csv, xml, json, zip/gz)
- List minimum requirements: Hotel Name, Hotel Street Address, Hotel City, Hotel Country, Hotel Postcode, Unique Hotel Identifier (hotel ID), Latitude, and Longitude. Refer to this page for details on requirements and additional preferences.
- Use English for column headers.