Skip to main content

Enhanced Air Ticket

Air
Ticketing
REST API
Travel Agency
Try Now
release_note
  • 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.

API Information

Response Format
JSON
Method/Endpoint
/v1.2.1​/air​/ticket
Current Version
1.2.1
Target Audience
TN
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.

Relase note ID: 16015


API Information

Response Format
JSON
Method/Endpoint
​/v1.2.1​/air​/ticket
Current Version
1.2.1
Target Audience
TN
Environment
Production

What's New


Resolved Issues

In the Request

N/A

With this change the API will properly query ticketing database for customers working on AA partition and AA current cities

Relase note ID: 14848


API Information

Response Format
JSON
Method/Endpoint
/v1.2.1/air/ticket
Current Version
1.2.1
Target Audience
TN
Environment
Production

What's New


Resolved Issues

In the Request/Response

N/A

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.

Relase note ID: 14772


  • Added ability to validate whether the newly issued tickets have been commited to the face of the PNR.

API Information

Response Format
XML
Service Action Code
AirTicketRQ
Current Version
1.2.1
Target Audience
Both TN and AS
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>
Note:

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:

 
Note:

Relase note ID: 13352


  • 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.

API Information

Response Format
JSON
Method/Endpoint
POST/v1.2.0/air/ticket
Current Version
1.2.0
Target Audience
TN
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.

Relase note ID: 12998