Requirements and rules for using the Search API after access is granted.                                                                                                                       

If you already have access to the Search API, please make sure your integration complies with the rules below. These requirements are mandatory and help us ensure fair usage and correct tracking.

User-initiated search only

• Every search request must be initiated by a user action.
• Search results must be displayed to the user in full.

Booking flow

• Each flight option must include a “Book” button.
• A link to the agency’s website must be generated only after the user clicks the “Book” button.
• Automatic generation or preloading of booking links is запрещено.

Data usage restrictions

• It is prohibited to:
  • automatically collect or scrape data from search results via the API;
  • combine the Search API with APIs of other flight metasearch services.

Technical requirements

• API requests must be sent from your server. Client-side (Ajax) requests are not supported.
• Ajax requests to the API don’t work because the access token is passed unencrypted. You must make requests to the API from the server.
• Requests from localhost IP ranges (127.0.0.1–127.255.255.255) are not allowed.

SEO restrictions

• Pages with search results must be hidden from search engine bots using the robots.txt file. or example, if flight tickets are displayed on the page www.sitename.com/search, then robots.txt should contain the following lines:

User-Agent: *
Disallow: /search/

Important

Violation of these rules may result in API access being disabled.