Technical requirements for Yandex and Customer web systems interaction for the provision of Materials by the Customer
1. Interaction scheme in receipt of Materials
General interaction scheme:
1. The User requests Yandex.Flights to provide flights options between two points on the selected date.
2. Yandex.Flights sends a request (GET or POST) to the Customer website, by transferring the following parameters:
2.1. departure – IATA or Sirena - code of departure point;
2.2. arrival – IATA or Sirena- code of arrival point;
2.3. date_forward – direct departure date in the format YYYY-MM-DD;
2.4. date_backward – return flight date in the format YYYY-MM-DD, optional;
2.5. class – class of service, e.g. E for Economy or B for Business;
2.6. adult – number of adult passengers;
2.7. child – number of children, optional;
2.8. infant – number of infants without a seat, optional.
3. The Customer website shall return XML specifying the information about seats and prices in the following format.
For example:
<variant
url = "[address]" // url to redirect the user to the Customer’s website
/>
<route_forward
route_code = "0123АБ" // flight number
company_code = "BL" // airline code
company_name = "Blah-air" // airline name
departure_airport_code = "DME" // departure airport code
arrival_airport_code = "SVO" // arrival airport code
departure_datetime = "2011-04-01 18:12" // departure date-time (local time)
arrival_datetime = "2011-04-01 21:20" // arrival date-time (local time)
route_time = "123" // travel time in minutes
farecode="WFLOWCS" // fare code
tariff_adult = “80.00” // adult tariff, if requested
tariff_child = “60.00” // child tariff, if requested
tariff_infant = “3.45” // infant tariff without a seat, if requested
/>
...
<route_backward
route_code = "0123АБ" // flight number
company_code = "BL" // airline code
company_name = "Blah-air" // airline name
departure_airport_code = "DME" // departure airport code
arrival_airport_code = "SVO" // arrival airport code
departure_datetime = "2011-04-01 18:12" // departure date-time (local time)
arrival_datetime = "2011-04-01 21:20" // arrival date-time (local time)
route_time = "123" // travel time in minutes
farecode="WFLOWCS" // fare code
tariff_adult = “80.00” // adult tariff, if requested
tariff_child = “60.00” // child tariff, if requested
tariff_infant = “3.45” // infant tariff without a seat, if requested
/>
...
<fare
value = "123.45" // fare (minimum fare) for a given class of serviceclass = "E" // service class code
charter = “true|false” //charter fare attribute
block = “true|false” //block fare attribute
/>
</variant>
All the flight information used in the example above is required to be included into a response according to the requested types of passengers.
The cost of individual flight segments need to be provided in all cases where the fare allows it.
4. The variant unit shall be repeated for each booking offer in a given class of service. Each variant unit has one or more route_forward and route_backward sub-units containing the information about segments of flight forward and backward respectively.
5. If the return date is not specified, then only one-way offers shall return, provided that variant units contain only route_forward sub-units.
6. Materials of the Customer received after 20 seconds of waiting or after termination of the waiting time by a user will not be placed. Such materials received after 20 seconds and before termination of a 2-minute period will be stored and displayed without a repeated request sent to the Customer until expiry of the cache lifetime.
7. Customers using Sirena-Travel GDS shall respond to requests with internal codes used in such GDS.
8. The Customer shall use a secure data transfer protocol (https) on its website to transfer from the Yandex.Avia service.
9. The Customer shall inform Yandex on the transition to a new protocol of Information provision no less than thirty (30) calendar days prior to implementation of such transition.
10. A report on the number and total cost of the air tickets purchased by Users through transfer from web-pages of the Yandex.Flights service to be submitted by the Customer according to paragraph 3.3.9 of the Agreement shall be in the xsl/xslx or csv format.
11. To limit the directions requests, you can connect regionalization send the link to the csv-file with the following format pairs of IATA and/or Siren area/airport codes, one in each line separated by “;”.
Each pair specifies permission to survey the direction both ways.
For example:
ATH;CMB
ATH;DXB
GBB;GOI
GPA;HAV
HER;KLX
KVD;LCA
LIS;LLK
LWN;MAD
MLE;NAP
СХТ;RHO
СХТ;СПТ
Data is collected once per day.
2. Interaction scheme in transfer to sales
The transfer from Yandex.Flights to the Customer website shall be conducted as follows:
1. The user selects an offer and clicks on the link (the cost of the air ticket provided by the Customer) at Yandex.Flights service.
2. The User is redirected to the Customer website at the address received in response in the url field of the variant unit for this offer.
3. The user starts booking on the Customer’s website:
3.1. the offers selected by the user at Yandex.Flights shall be automatically checked for availability on the Customer website (such check shall be performed before the User starts booking on the Customer’s website);
3.2. if the option selected by the User is not available, then the relevant information message shall be displayed to the User, and the User shall be offered other options corresponding to the parameters of the his/her search;
3.3. if the option selected by the User is available, then a page shall be displayed containing detailed information about the selected option and a field to enter passengers information for booking purposes. The following requirements shall also be met for the page:
If payment is made online by a bank card, the price of an air ticket displayed on the page shall fully correspond to the price specified by the Customer in the Materials, it must be displayed prominently and visually separated from other possible options offered by the Customer;
- The description of the option selected shall contain comprehensive information on check-in and carry-on baggage allowances applicable to this air ticket. These data shall be available on the same page and cannot be placed in blocks hidden by default.
3.4. In case the Customer, along with air tickets, offers any additional services to the User on the Customer website, the Customer undertakes to enable the User to select such additional services on its website independently. All additional services shall be offered before the details of the User’s bank card are entered. No additional services shall be added to the air ticket cost until consent of the User is received.
4. In case the User starts booking process on the Customer’s website, and the selected option requires the Customer’s confirmation, the following requirements shall be met:
- For air tickets requiring to be confirmed manually, an automatic response shall be given specifying the terms of the final confirmation.
- The term of the final response on the availability of the selected offer and its cost shall not exceed 1 business day.
- The User shall be informed, if the offer is not confirmed.
5. The Customer undertakes not to transfer the Materials in response to the request from Yandex.Avia in the following cases:
5.1. if the parameters described herein are not fully displayed on the Customer’s website in obtaining the Materials;
5.2. if the Customer’s website is not launched as specified in the response according to clause 2 of the Interaction Scheme in the transfer to sales, and an error message is displayed;
5.3. in case of any technical or other issues preventing the User from visiting the page with the selected option details (in accordance with clause 3.3 hereof) and complete the purchase process on the Customer website.
6. In that case, the purchase process shall continue, in accordance with the technology used on the Customer website.
_____________________________
Date of publication: 06.10.2016
Effective Date: 06.10.2016
Previous version of the document: https://yandex.com/legal/airplane_timetable_requirements_ch/25072016
Previous version of the document: https://yandex.com/legal/airplane_timetable_requirements_ch/15032016