Ancillaries shopping scenario | v0.52 | OW + 1xADT + Direct + S7 flight + EMD seat

Overview

An example of end-to-end scenario based on on operation flow and user story

Operation flow

searchFlightsJourney → book (Flight) → reprice without PNR → reprice with PNR → seatMap → demandTickets (ETK)

User story

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. He chooses direct S7 flight.

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: 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, seats codes and pricing details for air and seats.

Table of contents:

Before you can send a request to S7 Agent API, you must get an SSL certificate and configure your software.

EMD seat is available for cross sell only.

Extra seat is available for each segment.

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

Segments (Flight) must be devided into slices (OriginDestination):

one OriginDestination for One Way trip;
two for Round Trip and more for MultiCity;
for Transfer Trip all segments included in one slice have to be pass in one OriginDestination;
for Transfer Trip segments with stopover between have to be divided into two OriginDestination.

OriginDestination information in AirShoppingRS

Envelope/Body/AirShoppingRS/DataLists/FlightSegmentList

and <ClassOfService> (RBD) from

RBD information in AirShoppingRS

Envelope/Body/AirShoppingRS/OffersGroup/AirlineOffers/AirlineOffer/PricedOffer/OfferPrice/RequestedDate/Associations/ApplicableFlight/FlightSegmentReference/ClassOfService/Code

Step 3: Request for informative 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

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 with reservation reference, baggage codes and pricing details for air and baggage.

It is necessary correctly indicate passenger reference (RPH) for whom a ticket is issued. Used passenger SH number from the book operation

Passenger ref in OrderViewRS

Envelope/Body/OrderViewRS/Response/Passengers/Passenger@ObjectKey

Add information about PNR from OrderViewRS

PNR information in OrderViewRS

Envelope/Body/OrderViewRS/Response/Order/BookingReferences/BookingReference/ID

Specify payment object key like "ETK" for ticket and "EMD" for EMD seat.
Fill in the form of payment as in example <*A*TEXT>

FOP for ETK and EMD must be the same.

FOP

<Payments>
    <Payment>
        <Type>
            <Code>MS</Code>
        </Type>
        <Other>
            <Remarks>
                <Remark>*A*TEXT</Remark>
            </Remarks>
        </Other>
    </Payment>
</Payments>

CheckedBagAllowanceList and SeatList data takes from SeatAvailabilityRS

FlightSegmentList and OriginDestinationList data takes from OrderViewRS

Page tree