Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


DemandTicket operation is for ticketing passengers from existing booking. Returns ticket number for a passenger specified in the request.

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 demandTicket flow — allows to issue ticket for a specified passenger. Includes passenger, booking and itinerary information.
  2. 3D agreement demandTicket flow — allows to issue ticket for a specified passenger (сonsidering corporate discount). Includes Agent/Corporate client, booking and itinerary information.


Table of contents

Table of Contents

Request (AirDocIssueRQ)

Required inputs

#NameFormat/ReferencexPath
1Block of access parametersUse credentials that you received from our technical support. Check out Quick Start for how to get it andReferences for more details/Envelope /Body /AirDocIssueRQ /Party /Sender /AgentUserSender
2Passenger information

Passenger name, surname and type

/Envelope/Body /AirDocIssueRQ /Query /TicketDocInfo /TravelerInfo

3Booking informationPNR and passenger object key/Envelope/Body /AirDocIssueRQ /Query /TicketDocInfo /BookingReference
4Payment information

Payment details

/Envelope /Body /AirDocIssueRQ /Query /TicketDocInfo /Payments

5Checked Bagage Allowance ListList of Checked Baggage Allowance for each segment

/Envelope /Body /AirDocIssueRQ /Query /DataLists /CheckedBagAllowanceList 

6Pricing informationInformation about fares, taxes and endorsements/Envelope /Body /AirDocIssueRQ /Query /DataLists /FareList
7Flight Segment ListFlight segments information /Envelope /Body /AirDocIssueRQ /Query /DataLists /FlightSegmentList 
8Valid before dateSegments not valid after date/Envelope/Body /AirDocIssueRQ /Query /DataLists /TermsList

Optional parameters

#NameFormat/ReferencexPath
1

3D agreement credentials

Available 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 /AirDocIssueRQ /Query /DataLists /InstructionsList /Instruction[@ListKey="CC"] /SpecialBookingInstruction

Response ( AirDocDisplayRS)

#NameFormat/ReferencexPath
1Passenger information

Passenger name, surname and type

/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /TravelerInfo

2Booking informationPNR and passenger object key/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /BookingReference
3Total priceTotal price

/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /Payments

4Journey informationOrigin and destination airports/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /OriginDestination
5Pricing informationInformation about fares, taxes and endorsements/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /FareInfo
6Issued document informationDocument number, type, date of issue and status/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /TicketDocument
7

Coupons information

Coupons information by segment/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /TicketDocument /CouponInfo /SoldAirlineInfo
8Transfer inscriptions and restrictionsTransfer inscriptions and restrictions/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /Commission
9Passenger document numberPassenger document number/Envelope/Body /AirDocDisplayRS /Response /TicketDocInfos /TicketDocInfo /PassengerSpecificData

Samples

Children Display
styleh3
pagedemandTicket demandTickets operation | Samples
excerptTyperich content