To enable Skyscanner to ingest your daily booking data for package products, please adhere to the following data specification and transfer methods. This will help us ensure smooth data processing and accurate performance tracking.
Required parameters:
| Field | Required? | Example Value | Note |
| Booking Id | Required | 10625596 | The PNR code or booking IDthat uniquely identifies each booking. |
| Redirect Id | Required | 2KrtIocTStOxePSv5spTne | The raw redirect_id value provided by Skyscanner at the time of redirection. |
| Booking Status | Required |
One of the following: 2. Cancelled |
The status of the booking |
| Total Price Local | Required | 647.90 | The monetary value associated with the booking. |
| Total Price Currency Code | Required | GBP | The ISO currency code in which the ‘Total Price Local’ is denominated. |
| Check In Date | Required | 2025-05-01 | Specifies the check-in date in YYYY-MM-DD format. |
| Check Out Date | Required | 2025-05-03 | Specifies the check-out date in YYYY-MM-DD format. |
| Partner Hotel Id | Required | 115414599 | A unique identifier for the hotel within your system or platform. |
| Market | Required | GB | The country where the order being sold on your end. Must follow ISO 3166-2 (2 digits country code) |
| Device | Required | One the following: 1. Web 2. Mobile |
The device of this order being placed or lands on your side. The “Mobile” include mobile web and the App platform. |
| Board Basis | Optional | One of the following: 1.Bed and Breakfast 2.Room Only 3.Half Board 4.Full Board 5.All Inclusive 6.Other |
meals and drinks included in the price of your hotel |
| Dep Country Code | Optional | GB | The country from which the flight firstly departs (if a flight is included). Must follow ISO 3166-2 (2 digits country code) |
| Arr Country Code | Optional | IT | The country where the flight firstly arrives (if a flight is included). Must follow ISO 3166-2 (2 digits country code) |
| Adults | Optional | 2 | The number of adult travelers associated with the booking. |
| Non Adults | Optional | 0 | The number of non-adult travelers associated with the booking. |
| Flight Carrier Outbound | Optional | FR | The outbound flight carrier, if a flight is included. |
| Flight Carrier Inbound | Optional | BA | The inbound flight carrier, if a flight is included. |
| Hotel Name | Optional | Hotel Villa Edera | The name of the hotel associated with the booking |
| Hotel Star Rating | Optional | 3 | The rating of the hotel |
Delivery Methods:
To ensure robust and automated ingestion of package booking data, Skyscanner supports 4 delivery mechanisms. Below is a breakdown of each method, including responsibilities, access expectations, and operational flow.
sFTP (Hosted by partner)
Overview:
If you can host the booking files on your own sFTP server, Skyscanner will proactively connect and retrieve the files daily. This method is preferred for its reliability and centralized control on your side.
Partner Requirements
Overview:
If you can host the booking files on your own sFTP server, Skyscanner will proactively connect and retrieve the files daily. This method is preferred for its reliability and centralized control on your side.
Partner Requirements
Host an sFTP server.
Ensure files include all mandatory schema fields.
-
Provide Skyscanner with:
Host address and port
Authentication details (password or SSH key)
Delivery directory path
File naming convention including booking date (e.g.
booking_YYYYMMDD.csv)
Make files available daily by the agreed cut-off time (e.g. 00:00 UTC).
Retain files for 7–14 days for reprocessing.
API Endpoint (Hosted by partner)
Overview:
If you have an existing API to expose package booking data, Skyscanner can proactively
fetch the data based on either:
A fixed daily window (e.g., fetch “bookings created on YYYYMMDD”); or
A custom time range, passed via parameters (e.g., from_date / to_date).
Partner Requirements
-
Provide:
API base URL
Authentication method
Supported query parameters
API rate limits (if applicable)
Response format (JSON or CSV)
Example request and response payloads
-
Ensure:
All mandatory schema fields are included.
Daily data is complete and available by the agreed time.
Automated Email Delivery
Overview:
You may choose to email your daily booking file as an attachment (CSV or JSON) to our
dedicated inbox:
Partner Requirements
Partner Requirements
Automate daily email delivery with the booking file attached.
Use subject format:
[PartnerName] Daily Package Booking File – YYYY-MM-DDEnsure attachments are UTF-8 encoded, schema-compliant, and delivered by the agreed cut-off time.
Third-party File Hosting
Overview:
If you store booking files in a cloud-based object storage system (e.g., Amazon S3, Google
Cloud Storage, or Azure Blob Storage), Skyscanner can access the data through a secure, read-
access endpoint.
Partner Requirements
Provide a public or secure access method (pre-signed URL or bucket credentials).
Ensure files follow naming conventions and are available by the daily cut-off.
Optionally use expiring signed URLs for added security.
Supported services: Amazon S3, Google Cloud Storage, Azure Blob Storage.
Security Requirement – IP Allow List
For all delivery methods where Skyscanner initiates access (e.g., sFTP pull, API pull, or access to third-party file hosting), Skyscanner’s outbound IP address(es) must be added to the partner’s allow list to ensure secure and successful connectivity. Skyscanner will provide the fixed public IP address range upon request.
Partners are responsible for updating firewall or access rules to permit inbound traffic from these IPs.
This applies to:
sFTP servers hosted by the partner
APIs requiring IP-based access control
Object storage platforms (e.g., Amazon S3, Google Cloud Storage, Azure Blob) when bucket-level access policies are enforced
This requirement does not apply to delivery via automated email.