Flights Technical Readiness Checklist

Purpose

Use this checklist to quickly assess whether you’re ready to start a Flights integration with Skyscanner.

For in-depth explanations, examples and troubleshooting, refer to the linked helpdesk articles.

 

Readiness Checklist

Area	You are ready if...
Production environment	You have a live production environment that is available and not subject to change. (We do not work with test/staging environments)
Quote API	API meets technical requirements (e.g. response time). API meets content requirements API meets pricing/policy requirements (final price, currency, error mapping).
Deeplinks	Deeplink meets depth requirements (booking page preferred; day view fallback). Deeplink meets landing behaviour (lands on exact flight or matching results) Deeplink meets tracking/security requirements (HTTPS, tracking params, no plain-text credentials).
Pricing & policies	Pricing meets parity requirements (Total price can be calculated from the API response) Pricing meets tax/fee requirements Pricing follows Skyscanner’s payment policy.
Route Configuration	Routes meet content requirements Routes can be retrieved using one of the supported methods (eg. OAG/automated/manual)
Cabin Classes	You can minimally provide mappings from your cabin classes to general cabin classes (e.g. Economy: 'Y' or '1' or 'Economy'), and you may optionally also provide mappings for fare basis codes. This is strongly recommended, but not strictly required if you only ever return a single cabin class (e.g. Economy).
API Schema	Schema provided (JSON or XSD) Documentation includes a working request & response example (or provided separately) List of error codes provided (codes and short descriptions)
Downstream Visibility	DV opt-in (if applicable) and method chosen (Tag / Pixel / S2S) DV meets data requirements
Skyscanner Keyword Tracking	Keyword tracking method chosen (API preferred / SFTP / Email / Portal) Keyword revenue report meets content requirements