Book operation makes a reservation of chosen solution for one or more passengers and return PNR locator with passengers and itinerary information in XML.
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
| Table of Contents |
|---|
Book
| Anchor | ||||
|---|---|---|---|---|
|
Standard booking
Required inputs
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 1 | Block of access parameters | Use credentials that you received from our technical support. Check out Quick Start for how to get it and References for more details | /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 | |
| 2 | Seats information | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/SeatList/Seats | |
| 3 | TTL | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/ServiceList/Service[ServiceID][Name]TimeLimits/TicketingTimeLimits |
3D agreement boooking
Required inputs
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 1 | Client ID code | QUW1725 | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction/Code |
| 2 | Agent ID code | 918 | /Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction/Definition |
| Note | ||
|---|---|---|
| ||
|
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.