You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 34 Next »


Book operation makes a reservation of chosen solution for one or more passengers and returns PNR locator with passengers, itinerary information and Ticket Time Limits 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:

  1. Standard booking flow — reservation of chosen solution from search results. Includes passengers and itinerary information.
  2. 3D agreement boooking flow — reservation of chosen solution from search results (сonsidering corporate discount). Includes Agent/Corporate client and itinerary information. 3D agreement booking flow is available only for S7 Corporate program. Applying 3D agreement booking flow for S7 Profi program is not allowed.
  3. S7 Profi boooking flow - reservation of chosen solution from search results. Includes S7 Profi client code and itinerary information.

Table of contents

Request (OrderCreateRQ)

Required inputs

#NameFormat/ReferencexPath
1

Block of access parameters

Use credentials that you received from our technical support. Check out Quick Start | S7 Agent API for how to get it and References for more details/Envelope/Body/OrderCreateRQ/Party/Sender/AgentUserSender
2Passenger information

This element contains information about passengers: name, surname, date of birth, contacts, passport data, etc.

(warning) Max 4 passengers for economy cabin, 2 - business in case of CodeShare or SPA flights (check glossary for flights types) 

/Envelope/Body/OrderCreateRQ/Query/Passengers/Passenger

3Passengers and flight segments references

Includes reference elements connecting passengers with the appropriate flights

/Envelope/Body/OrderCreateRQ/Query/OrderItems/ShoppingResponse

4Itinerary informationSolution from Search method RS
Segments must be devided into slices:
  • one slice (OriginDestination block) 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 block;
  • in Transfer Trip segments with stopover between are divided into two OriginDestination,Check glossary for more info.

/Envelope/Body/OrderCreateRQ/Query/OrderItems/OfferItem/DetailedFlightItem

Optional parameters

#NameFormat/ReferencexPath
1

Seats information

Contains the list of seats with a price/Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/SeatList/Seats
2

Ticketing Time Limit

Booking cancelation datetime in case of tickets are not issued.

By default calculated by S7 rules.

/Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/ServiceList/Service[ServiceID][Name]TimeLimits/TicketingTimeLimits
33D agreement credentialsAvailable only for scenario with 3D AgreementUse credentials that you received from our technical support. Check out Quick Start for how to get those IDs/Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction
4S7 Profi credentialsAvailable only for S7 Profi program scenario. Use credentials that you received from our technical support. Check out Quick Start for how to get those IDs/Envelope/Body/OrderCreateRQ/Query/OrderItems/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction

Response (OrderViewRS)


NameFormat/ReferencexPath
1Passengers information

This element contains information about passengers: name, surname, date of birth, contacts, passport data, etc.

/Envelope/Body/OrderViewRS/Response/Passengers/Passenger

2Booking reservation numberPNR/Envelope/Body/OrderViewRS/Response/Order/BookingReferences
3Ticketing Time LimitTTL/Envelope/Body/OrderViewRS/Response/Order/TimeLimits/PaymentTimeLimit
4Itinerary informationItinerary information/Envelope/Body/OrderViewRS/Response/Order/OrderItems

Samples

  • No labels