Page History

Overview

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

Excerpt

Operation flow

searchFlightsJourney → book (Flight) → reprice without PNR → reprice with PNR → servicePrice → 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 and two extra bags. 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 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:

Table of Contents

Note

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

Excerpt Include

	OW + 1xADT + Direct + S7 flight\| v0.52 \| searchFlightsJourney operation
	OW + 1xADT + Direct + S7 flight\| v0.52 \| searchFlightsJourney operation
nopanel	true

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

Code Block

language	xml
theme	Confluence
title	OriginDestination information in AirShoppingRS
collapse	true

Envelope/Body/AirShoppingRS/DataLists/FlightSegmentList

and <ClassOfService> (RBD) from

Code Block

language	xml
theme	Confluence
title	RBD information in AirShoppingRS
collapse	true

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

Excerpt Include

	OW + 1xADT + Direct + S7 flight \| v0.52 \| book operation
	OW + 1xADT + Direct + S7 flight \| v0.52 \| book operation
nopanel	true

Step 3: Request for

informative reservation pricing

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);

Note
<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).

Excerpt Include

	1А \| OW + 1xADT + Direct + S7 flight \| v0.52 \| reprice without PNR operation
	1А \| OW + 1xADT + Direct + S7 flight \| v0.52 \| reprice without PNR operation
nopanel	true

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);

Note
<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).

Excerpt Include

	1А \| OW + 1xADT + Direct + S7 flight \| v0.52 \| reprice with PNR operation
	1А \| OW + 1xADT + Direct + S7 flight \| v0.52 \| reprice with PNR operation
nopanel	true

Step 5: Request for ancillaries pricing for baggage

S7 Agent executes a servicePrice operation with the whole journey details and passenger type list

Excerpt Include

	Baggage \| OW + 1xADT + Direct + S7 flight\| v0.52 \| servicePrice operation
	Baggage \| OW + 1xADT + Direct + S7 flight\| v0.52 \| servicePrice operation
nopanel	true

Step 6: Request for ancillaries pricing for seats

S7 Agent executes a seatMap operation operation with the whole journey details and cabin type

Excerpt Include

	OW + 1xADT + Direct + S7 flight \| v0.52 \| seatMap
	OW + 1xADT + Direct + S7 flight \| v0.52 \| seatMap
nopanel	true

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

Code Block

language	xml
title	Passenger ref in OrderViewRS
collapse	true

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

Add information about PNR from OrderViewRS

Code Block

language	xml
theme	Confluence
title	PNR information in OrderViewRS
collapse	true

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

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

Note
FOP for ETK and EMDs must be the same.

Code Block

language	xml
theme	Confluence
title	FOP
collapse	true

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

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

Excerpt Include

	OW + 1xADT + Direct + S7 flight \| TKT + EMD baggage&seat \| v0.52 \| demandTickets operation
	OW + 1xADT + Direct + S7 flight \| TKT + EMD baggage&seat \| v0.52 \| demandTickets operation
nopanel	true

Page tree

Versions Compared

Old Version 2

New Version 3

Key

Overview

Operation flow

User story

Scenario

Step 1: Initial search for flight solutions

Step 2: Book a reservation

Step 3: Request for

informative pricing

Step 4: Request for reservation pricing

Step 5: Request for ancillaries pricing for baggage

Step 6: Request for ancillaries pricing for seats

Step 6: Issue tickets with EMD for each passenger