What is it?
The Enhanced Air Ticket API is used to issue one or multiple air tickets and/or EMDs (Electronic Miscellaneous Documents) within a single API call.
Why use it?
You can use this API to:
- Issue multiple Air Tickets and EMDs within a single call
- Issue multiple Price Quote Reissue Records (PQRs) in one call
- Integrate printer address designation/un-designation
- Manage sessions on behalf of the client application (stateless behavior from the user standpoint)
- Manage error handling to ensure the successful issuance of an air ticket
- Return newly issued ticket numbers together with additional details pertaining to specific documents
- Handle context change/AAA (modify target city)
- Delete air accounting lines prior to ticketing
How it works
The API performs following steps to issue a single ticket or multiple tickets:
- Performs an “ignore transaction” to ensure that the work area is clear
- Handles context changes/AAA (modify target city)
- Validates the existence of AUTOEND/AUTOER TJR flag, and designates printers
- Retrieves the existing reservation using a record locator provided within the payload
- Deletes accounting lines prior to ticketing to issue a single ticket (ETR/EMD/PQR), or multiple tickets, and automatically handles Sabre-specific mask scenarios
- Ends transactions and commits the tickets to the face of the PNR (this step is omitted for users who have AUTOEND/AUTOER TJR flag present)
- Retrieves newly generated ticket details, undesignated printers, and performs “ignore transaction” after the transaction to ensure that the work area is clear
How to use
How to invoke a ticketing call via Enhanced Air Ticket API
A single ticketing instruction is generated by sending a single instance of AirTicketRQ.Ticketing. The Enhanced Air Ticket API will then perform a single ticket issuance and attempt to perform the following steps:
-
Ignores the transaction to clear the session data and retrieve the reservation.
-
Performs a single call to the low-level service, AirTicketLLSRQ.
-
If the user has the TJR setting on
AUTOEND/AUTOER, the issued ticket will be automatically committed to the PNR and the EndtransactionLLSRQ call will be omitted.
Notes:
- To issue multiple tickets/ticket types, send
AirTicketRQ.Ticketingwithin the request payload as many times as the number of tickets to be generated. - If there are more tickets to be issued, the above steps will be repeated as many times as
AirTicketRQ.Ticketingis present within the request payload. When the whole process is completed, the API will attempt to retrieve the newly issued ticket details by callingTicketingDocumentServicesRQ.