Skip to main content

We are introducing daily content suppression updates and a Partner Portal dashboard for full details across most Flight content.
If any content was suppressed in the last day, you will receive a daily message with a link.
For a limited time, both the new and current channels will be used, duplicate messages can be matched by ticket number.

Redirects Module - Partner Portal
From 17 August 2026, Skyscanner introduced updates to the reporting methodology used to process and report traveller activity across our Travel Insights data.
As a result, you may notice a reduction in the number of Redirects reported in Partner Portal compared with previous periods. This reflects a change in reporting methodology and should not be interpreted as an equivalent reduction in overall traveller activity or demand on Skyscanner.

Integration Process Overview

Updated

This document outlines the end-to-end process required to integrate with Skyscanner. Each phase describes what is expected from your team and what actions will be completed by Skyscanner’s Partner Services and Engineering teams.

1. Pre-Integration

Before development begins, the following steps must be completed:

  • A commercial agreement must be signed.

  • Our Partner Services team will request your technical documentation (API specs, inventory feed details, tracking requirements, etc.).

  • Once all required materials are received, Skyscanner performs pre-integration checks to validate data quality and compatibility.

When the assessment is complete, the integration is scheduled into the engineering queue.

Please Note: We require full access to live environment only. We cannot proceed with an integration with test access. We also require you to install a tracking method either via our HBS solution or Downstream Visibility before any development work can be started. More information can be found on #3 Tracking Method section below.

2. Integration Work

Please Note: For any API connection, we will also supply you with a list of our IPs to ensure that you allow these to prevent us from any issues with accessing the API. Once this information has been collated we will test the API to confirm compatibility. 

Once your integration begins, Skyscanner initiates different workstreams:

Inventory Integration

This workstream focuses on preparing and validating your inventory data:

  • Parsing and validating the inventory feed

  • Preparing data structures for ingestion

  • Performing data release and merging activities

This ensures your property catalogue is mapped correctly to Skyscanner.

In this workstream, our engineering team completes your API and deeplink setup:

  • Connecting your API

  • Configuring deeplinks and tracking parameters

  • Conducting test based on multiple scenerios

Both workstreams are required before your integration can move toward production. This phase ensures that your property information, availability, and pricing are processed correctly.

3. Tracking Method

Tracking integration also begins during engineering work. The approach depends on your chosen method:

Option 1: HBS (Hotel Booking Scraper)

Skyscanner consumes your Booking & Cancellation Reports for revenue tracking. This can be done in several methods but please refer to the documentation here: [Hotel Booking Scraper - HBS ].

  • HBS Reports and booking/cancellation reports fit within the requirements

  • Connectivity tests are done to validate connection

Option 2: Downstream Visibility

For partners implementing Downstream Visibility: This is a method where you’ll have to install a tag on your side, please refer to the documentation there : Downstream Visibility

  • DV integration is configured

  • DV integration is verified triggering valid events

4. Hotels Dynamic CPC Bidding

If you choose to use Hotels Dynamic CPC Bidding, this will begin after the Inventory + API/Deeplink are completed.

Refer to: Hotel Dynamic CPC Bidding – Skyscanner Partner Support

5. Deployment to Production

After successful testing:

  • Your integration is deployed to Skyscanner’s production environment

  • Final confirmation of tracking, availability, and deeplinks is completed

  • You are notified once the integration is fully live

6. Communication, Timeline, Preparation Expectations

While we cannot commit to a fixed integration timeline, due to variations in data readiness, API maturity, and partner systems, we will:

  • Please ensure that your technical specifications fit within our requirements here

  • We will try out best to keep you updated at each stage

  • We will be managing separate communication threads for each integration component

  • To help us keep your integration moving smoothly, we kindly request prompt replies. If we do not receive a response within 2 weeks, the integration may be temporarily placed on hold.


 

Related articles