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
| # | 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 andReferences for more details | /Envelope/Body/AirDocIssueRQ/Party/Sender/AgentUserSender |
| 2 | Information on the issued ticket | Contains information about passengers, payment system, PNR and RPH | /Envelope/Body/AirDocIssueRQ/Query/TicketDocInfo |
| 3 | Payments | Contains information on the payment system | /Envelope/Body/AirDocIssueRQ/Query/TicketDocInfo/Payments |
| 4 | List of allowed Luggage | Contains information on the baggage with reference to a flight segmen | /Envelope/Body/AirDocIssueRQ/Query/DataLists/CheckedBagAllowanceList |
| 5 | Data on tariff plans | Сontains information about Taxes, Endorsements, Fare Basis Code and Base Amount | /Envelope/Body/AirDocIssueRQ/Query/DataLists/FareList |
| 6 | Flight Segment List | Contains information on flight segments | /Envelope/Body/AirDocIssueRQ/Query/DataLists/FlightSegmentList |
| 7 | Terms List | Contains information on the timing of departure with reference to a flight segment | /Envelope/Body/AirDocIssueRQ/Query/DataLists/TermsList |
Optional parameters
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |
3D agreement demandTicket
Required inputs
| # | Name | Format/Reference | xPath |
|---|---|---|---|
| 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 |
3D demand operation available only for ADT type passengers
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.