Overview
An example of end-to-end scenario based on on operation flow and user story searchFlightsJourney → book (Flight) → reprice without PNR → reprice with PNR → servicePrice → seatMap → demandTickets (ETK) S7 agent wants to buy one way flight from Moscow (DME) to Samara (KUF) for one adult traveler. He also wants to buy extra space seat and two extra bags. He chooses direct S7 flight.Operation flow
User story
Scenario
The general process for buying a trip such as this is:
- Initial search for flight solutions: S7 Agent executes a searchFlightsJourney operation with itinerary criteria and passenger types count;
- Book a reservation: S7 Agent executes a book operation with passenger details and itinerary info of chosen solution from search results;
- Request for informative reservation pricing: S7 Agent executes a reprice operation with itinerary info of chosen solution;
- Request for reservation pricing: S7 Agent executes a reprice operation with itinerary info of chosen solution;
- Request for ancillaries pricing for baggage: S7 Agent executes a servicePrice operation with the whole journey details and passenger type list;
- Request for ancillaries pricing for seats: S7 Agent executes a setaMap operation with the whole journey details and cabin type;
- Issue tickets with EMD for each passenger: S7 Agent executes a demandTickets operation with reservation reference, baggage codes, seats codes and pricing details for air, seats and baggage.
Table of contents:
Before you can send a request to S7 Agent API, you must get an SSL certificate and configure your software.
EMDs are available for cross sell only.
Extra seat is available for each segment.
Extra baggage is available for each slice.
Step 1: Initial search for flight solutions
S7 Agent executes a searchFlightsJourney operation with itinerary criteria and passenger types count
Received solutions divided by fare family and mostly includes 4 sub solutions (Basic Economy, Flex Economy, Basic Business, Flex Business) for each itinerary solution.
Step 2: Book a reservation
S7 Agent executes a book operation with passenger details and itinerary info of chosen solution from search results.
<DetailedFlightItem> block consists of journey information, where each slice is described by the <OriginDestination> element.
<OriginDestination> block takes from appropriate AirShoppingRS
and <ClassOfService> (RBD) from
Step 3: Request for informative reservation pricing
S7 Agent executes a reprice operation with itinerary info of chosen solution
All information must be taken from AirShoppingRS:
itinerary details (airport codes and dates for origin and departure, airline code and flight number);
<FlightItem> block must fill in like in OrderCreateRQ. Each slice is described by the <OriginDestination> element.
- passenger types (PTC);
- fare details (RBD and fare code).
Step 4: Request for reservation pricing
S7 Agent executes a reprice operation with itinerary info of chosen solution
All information must be taken from AirShoppingRS:
itinerary details (airport codes and dates for origin and departure, airline code and flight number);
<FlightItem> block must fill in like in OrderCreateRQ. Each slice is described by the <OriginDestination> element.
- passenger types (PTC);
- fare details (RBD and fare code).
Step 5: Request for ancillaries pricing for baggage
S7 Agent executes a servicePrice operation with the whole journey details and passenger type list
Step 6: Request for ancillaries pricing for seats
S7 Agent executes a seatMap operation operation with the whole journey details and cabin type
Step 6: Issue tickets with EMD for each passenger
S7 Agent executes a demandTickets operation with reservation reference, baggage codes, seats codes and pricing details for air, seats and baggage.
It is necessary correctly indicate passenger reference (RPH) for whom a ticket is issued. Used passenger SH number from the book operation
- Add information about PNR from OrderViewRS
- Specify payment object key like "ETK" for ticket and "EMD" for EMDs.
- Fill in the form of payment as in example <*A*TEXT>
FOP for ETK and EMDs must be the same.
- FareList for baggage and CheckedBagAllowanceList data takes from ServicePriceRS
- FareList for seats and SeatList data takes from SeatAvailabilityRS
- FlightSegmentList and OriginDestinationList data takes from OrderViewRS