v1.2.1 | September 23, 2021
- Extended sleep/delay logic for future ticketing lines. When API receives the "F LINE PROCESSING STARTED" warning message from AirTicketLLSRS, it will will wait 2000 ms for each future ticketing line that is sent in the AirTicketRQ in order to successfully complete the ticketing transaction.
- Added a delay before 2nd call to TKT_DocumentServicesRQ - This is done to mitigate cases where multiple tickets were issued but only some of them are visible in the ticketing database, the extra delay of 500 ms aims to mitigate the problem.
- Added AirTicketRQ.PostProcessing.actionOnBackDatePrice - The API was enhanced to handle `UNABLE TO TICKET STORED FARE - PQ CONTAINS BACK DATE PRICE` ticketing mask. By default, the API will attempt to "R" - Reprice the stored fare, however the user can specify to "O" - Override or "Q" - Quit as well.
- Extend future line logic with Ticketing Mask detection. - As of now, when future ticketing line processing starts, the API will also react to known ticketing mask messages via SabreCommandLLSRQ.
- (03/08/2022) Enabled user controlled delays between multiple ticketing transactions as a way to limit 'SIMULTANEOUS CHANGES' error occurrences. Added AirTicketRQ.PostProcessing.TicketingInterval.waitInterval to allow the user to tell the API to wait between subsequent .Ticketing transactions.
- (03/08/2022) The API will now handle a very specific corner case related to multiple Future Line issuance. If you decide to quit upon encountering so-called 'ticketing masks' (acceptNegotiatedFare, acceptPriceChanges, actionOnBackDatePrice and actionOnPQExpired), system will now take into account already issued Future Ticketing lines commit them to the reservation.
- (06/28/2022) The API will now re-try the Ticketing command upon encountering the banner message 'VALIDATING CARRIER NOT PRESENT IN ITINERARY' , this applies to Abacus customers.
API Information
Format
JSON
Endpoint
/v1.2.1/air/ticket
Current Version
1.2.1
Environment
Production
What's New
- Extended sleep/delay logic for future ticketing lines. When API receives the "F LINE PROCESSING STARTED" warning message from AirTicketLLSRS, it will will wait 2000 ms for each future ticketing line that is sent in the AirTicketRQ in order to successfully complete the ticketing transaction.
- Added a delay before 2nd call to TKT_DocumentServicesRQ - This is done to mitigate cases where multiple tickets were issued but only some of them are visible in the ticketing database, the extra delay of 500 ms aims to mitigate the problem.
- Added AirTicketRQ.PostProcessing.actionOnBackDatePrice - The API was enhanced to handle `UNABLE TO TICKET STORED FARE - PQ CONTAINS BACK DATE PRICE` ticketing mask. By default, the API will attempt to "R" - Reprice the stored fare, however the user can specify to "O" - Override or "Q" - Quit as well.
- Extend future line logic with Ticketing Mask detection. - As of now, when future ticketing line processing starts, the API will also react to known ticketing mask messages via SabreCommandLLSRQ.
- (03/08/2022) Enabled user controlled delays between multiple ticketing transactions as a way to limit 'SIMULTANEOUS CHANGES' error occurrences. Added AirTicketRQ.PostProcessing.TicketingInterval.waitInterval to allow the user to tell the API to wait between subsequent .Ticketing transactions.
- (03/08/2022) The API will now handle a very specific corner case related to multiple Future Line issuance. If you decide to quit upon encountering so-called 'ticketing masks' (acceptNegotiatedFare, acceptPriceChanges, actionOnBackDatePrice and actionOnPQExpired), system will now take into account already issued Future Ticketing lines commit them to the reservation.
- (06/28/2022) The API will now re-try the Ticketing command upon encountering the banner message 'VALIDATING CARRIER NOT PRESENT IN ITINERARY' , this applies to Abacus customers.
Resolved Issues
In the Response
Optional
Description: (03/08/2022) The API will now handle a very specific corner case related to multiple Future Line issuance. If you decide to quit upon encountering so-called 'ticketing masks' (acceptNegotiatedFare, acceptPriceChanges, actionOnBackDatePrice and actionOnPQExpired), system will now take into account already issued Future Ticketing lines commit them to the reservation.
v1.2.1 | October 13, 2020
- In this version defect fixes were introduced.
API Information
Format
JSON
Endpoint
/v1.2.1/air/ticket
Current Version
1.2.1
Environment
Production
What's New
- In this version defect fixes were introduced.
Resolved Issues
In the Request
N/A
Description: With this change the API will properly query ticketing database for customers working on AA partition and AA current cities
v1.2.1 | August 20, 2020
- In this version defect fixes were introduced.
API Information
Format
JSON
Endpoint
/v1.2.1/air/ticket
Current Version
1.2.1
Environment
Production
What's New
- In this version defect fixes were introduced.
Resolved Issues
In the Request/Response
N/A
Description: The API will now automatically handle an intermittent scenario where, upon clearing the session post-ticketing, the system may respond with an "ET REQUIRED" error.
v1.2.1 | November 12, 2019
- Added ability to validate whether the newly issued tickets have been commited to the face of the PNR.
API Information
Format
XML
Current Version
1.2.1
Environment
Production
What's New
- Added ability to validate whether the newly issued tickets have been commited to the face of the PNR.
Functional Updates And Enhancements
In the Request
Optional
- Parameter: GhostTicketCheck
-
Type: N/A
Description: Used to specify wait interval to wait before the final reservation retrieval post ticketing. It is mandatory if you wish to validate whether the newly issued tickets were commited to the face of the PNR
Sample Value:
|-|PostProcessing acceptNegotiatedFare="true" acceptPriceChanges="true" actionOnPQExpired="O"|--|
|-|EndTransaction|--|
|-|Source ReceivedFrom="SWS TESTING"/|--|
|-|/EndTransaction|--|
|-|GhostTicketCheck waitInterval="1000" numAttempts="2"/|--|
|-|/PostProcessing|--|
In the Response
Optional
- Parameter: committed
-
Type: boolean
Description: Indicates that the ticket number has been commited to the face of the PNR. This validation will only be initiated if you specify GhostTicketCheck within request payload
Sample Value:
|-|Summary committed="true"|--|
|-|DocumentNumber|--|8298200110468|-|/DocumentNumber|--|
|-|LocalIssueDateTime|--|2011-09-08T16:11:32.000Z|-|/LocalIssueDateTime|--|
v1.2.0 | December 14, 2017
- Initial release. Features of this new orchestrated API:
- issue multiple Air Tickets and EMDs within a single call,
- issue multiple PQRs in one call,
- issue more than one PTC in the same transaction with installments,
- integrate printer address designation/un-designation,
- manage sessions on behalf of the client application,
- introduces 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.
- (12/07/2022) Resolved an intermittent issue where the API could not undesignate printers due to a gateway error "SC SERVICE UNAVAILABLE". This change introduces additional retry attempts to remedy the situation.
- (12/07/2022) Resolved an issue where the API stopped processing upon encountering "UNABLE - PRINTER PROFILE RECORD 01 IS ACTIVE". This happens when customers attempts to designate a printer which is already active in their session. After the change, the API will ignore this downline system message and proceed to issue tickets.
API Information
Format
JSON
Endpoint
/v1.2.0/air/ticket
Current Version
1.2.0
Environment
Production
What's New
- Initial release. Features of this new orchestrated API:
- issue multiple Air Tickets and EMDs within a single call,
- issue multiple PQRs in one call,
- issue more than one PTC in the same transaction with installments,
- integrate printer address designation/un-designation,
- manage sessions on behalf of the client application,
- introduces 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.
- (12/07/2022) Resolved an intermittent issue where the API could not undesignate printers due to a gateway error "SC SERVICE UNAVAILABLE". This change introduces additional retry attempts to remedy the situation.
- (12/07/2022) Resolved an issue where the API stopped processing upon encountering "UNABLE - PRINTER PROFILE RECORD 01 IS ACTIVE". This happens when customers attempts to designate a printer which is already active in their session. After the change, the API will ignore this downline system message and proceed to issue tickets.