Optional parameters
This method Is intended for booking of tickets and seats on the flight.
On the stages of booking, the flight segments should be distributed is as follows:
OreginDestination=slice, Flight=segment
Use cases
The following list of cases supported by the Shopping API and provides their required inputs as well as a list of common inputs used with that case:
- Book - Returns PNR locator, one for all passengers and Ticket Time Limits.
- Standard booking flow - reservation of chosen solution from search results. Include passengers and itinerary information.
- 3D agreement boooking flow - reservation of chosen solution from search results (сonsidering corporate discount). Include Agent/Corporate client and itinerary information.
Table of contents
Book
Standard booking flow
Required inputs
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 1 | Block of access parameters | /Envelope/Body/OrderCreateRQ/Party/Sender/AgentUserSender | |
| 2 | Passenger information | /Envelope/Body/OrderCreateRQ/Query/Passengers/Passenger | |
| 3 | Passengers and flight segments references | /Envelope/Body/OrderCreateRQ/Query/OrderItems/ShoppingResponse | |
| 4 | Itinerary infirmation | solution from Search method RS | /Envelope/Body/OrderCreateRQ/Query/OrderItems/OfferItem/DetailedFlightItem |
Optional parameters
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 1 | Additional Information | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists | |
Seats information | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/SeatList/Seats | ||
TTL | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/ServiceList/Service[ServiceID][Name]TimeLimits/TicketingTimeLimits |
The flight contains 2 slice OVB->KUF and KUF->OVB (in the request there will be 2 block OreginDestination) where:
slice OVB->KUF consists of 2 segments of the OVB->DME; DME ->KUF, then the first block OreginDestination describing slice OVB->KUF, will consist of 2 blocks of the Flight, one will describe the segment, OVB->DME, and the second DME->KUF.
For slice KUF->OVB is the same.
Each of the slices may consist of any number of segments (depending on the number of transfers in).
The logic is always the same, the slice to be written as OreginDestination, inside it writable segments through Flight.