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

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:

Table of contents

DemandTicket

Standard demandTicket

Required inputs
#NameFormat/ReferencexPath
1Block of access parameters
/Envelope/Body/AirDocIssueRQ/Party/Sender/AgentUserSender
2



3



4


Optional parameters
#NameFormat/ReferencexPath
1




2




3




3D agreement demandTicket

Required inputs
#NameFormat/ReferencexPath
1

Client ID code

QUW1725

/Envelope/Body/AirDocIssueRQ/Query/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction/Code
2

Agent ID code

918/Envelope/Body/AirDocIssueRQ/Query/DataLists/InstructionsList/Instruction[@ListKey="CC"]/SpecialBookingInstruction/Definition


(lightbulb) 3D demand operation available only for ADT type passengers

(lightbulb) Other Required inputs like described in Standard demandTicket





This method using for payment the booked ticket. Payment is made separately for each passenger.

The issuance of tickets to passengers is carried out in two types: 
1) ADT or CHD – adult or child.
2) INF – infant.
In order to write a ticket for an adult passenger, we must watch the sequence of passengers output in booking 
(Order Create RS). In our example, the ADT was first, i.e. Object Key="SH1".
Consequently, for the issue of the ticket, you must specify 
RPH1. 
So for CHD it is necessary to specify RPH2, because he was output second and have Object Key="SH2".
For INF always indicate the RPH1,because this is a different type.
If there were two INF, then for issue the ticket for the second baby, it is necessary to specify RPH2.