Skip Navigation

Exchange Booking

Air
Pricing
REST API
Travel Agency
Try Now
  • The API will now use and orchestrated EnhancedEndTransactionRQ instead of low-level EndTransactionLLSRQ. The internal orchestrated API introduces capability of recovering from known end transaction errors, which will simplify the exchange booking process.
  • The API will now validate internal agency setting to check whether the Automatic Segment Arrange setting is enabled (TJR AZA). If not, the API will return the following warning : "Automatic Segment Arrange TJR flag is not enabled. The flight segments may be out of order."
  • Added a reservation redisplay right after flight segment cancellation step. In some cases, lack of such action could prevent automated segment rearrangement.
  • Added support for multiple passenger/ticket exchanges - see 'Help' section for more details.
  • Up until recently the API always assumed that the DisplayPriceQuoteLLSRQ API will never return an error, from now on the users will see the downline service error message as well as a well defined warning: 'Unable to retrieve PQR information - see below messages for details'.
  • (08/01/2022) Modified warning message for Price Comparison when 'haltOnNonAcceptablePrice' equals 'false' - Starting from this release the warning message will be changed to correctly state that ..."Price Comparison failed" instead of stating that the "Exchange Booking transaction" has failed.
  • (08/01/2022) Modified failed reservation redisplay error messages in multiple ticket exchanges scenario. - With this small adjustment the users will now see specific ticket numbers, for which the API failed to retrieve details. The example message: "Unable to retrieve reservation details for ticket number(s) 0012345678901 - see below messages for details."
  • (08/30/2022) Starting from this release the user will receive a well defined error message upon sending an empty 'PriceComparison' node: 'When using PriceComparison either AcceptablePriceIncrease or AcceptablePriceDecrease is required.'
  • (08/30/2022) The API was enhanced to inform the user when segments to be priced or cancelled are not found in the reservation, example: '/ExchangeBookingRQ/Itinerary/SegmentPricing/SegmentSelect/@number=150 does not exist within the reservation'
  • (08/30/2022) The API was enhanced to support adding Special Service Requests (SSRs) right after booking new air segments
  • (10/04/2022) When customers attempt to cancel and book identical flight segments they may run into waitlist and other air booking issues, so a warning message will be returned from now on: "Cancelling segments and rebooking identical ones may cause issues with Air Booking."
  • (10/04/2022) Multiple ticket exchanges - corrected error handling when the first ticket exchange fails (reported under [ASTSP-439]). If the API encounters an error during the first ticket exchange, the API will stop processing, because otherwise entering another loop might cause issues with the state of the PNR. The API will now stop processing upon encountering errors during Automated Exchanges Comparison, Price Comparison, Automated Exchanges Confirmation, and End Transaction steps.
  • (04/04/2023) - From now on, in the case of multiple ticket exchanges, if a process for one of the tickets fails, the API will attempt to re-try generation of Price Quote Reissue Record up to 3 times (initial failure + 3 retries). This change is meant to help you work around any synchronization issues between downstream service providers.
  • (04/04/2023) - Removed obsolete .PostProcessing.acceptIncompleteTransactions - The attribute was never supported and its removal is meant to polish the request schema document
  • (05/30/2023) Added capability to pass PQR associated information on refundable amount to be collected on EMD at ExchangeConfirmation.RefundableAmountOnEMD.

API Information

Format
JSON
Endpoint
/v1.0.1/exchange/booking
Current Version
1.0.1
Environment
Production

What's New

  • The API will now use and orchestrated EnhancedEndTransactionRQ instead of low-level EndTransactionLLSRQ. The internal orchestrated API introduces capability of recovering from known end transaction errors, which will simplify the exchange booking process.
  • The API will now validate internal agency setting to check whether the Automatic Segment Arrange setting is enabled (TJR AZA). If not, the API will return the following warning : "Automatic Segment Arrange TJR flag is not enabled. The flight segments may be out of order."
  • Added a reservation redisplay right after flight segment cancellation step. In some cases, lack of such action could prevent automated segment rearrangement.
  • Added support for multiple passenger/ticket exchanges - see 'Help' section for more details.
  • Up until recently the API always assumed that the DisplayPriceQuoteLLSRQ API will never return an error, from now on the users will see the downline service error message as well as a well defined warning: 'Unable to retrieve PQR information - see below messages for details'.
  • (08/01/2022) Modified warning message for Price Comparison when 'haltOnNonAcceptablePrice' equals 'false' - Starting from this release the warning message will be changed to correctly state that ..."Price Comparison failed" instead of stating that the "Exchange Booking transaction" has failed.
  • (08/01/2022) Modified failed reservation redisplay error messages in multiple ticket exchanges scenario. - With this small adjustment the users will now see specific ticket numbers, for which the API failed to retrieve details. The example message: "Unable to retrieve reservation details for ticket number(s) 0012345678901 - see below messages for details."
  • (08/30/2022) Starting from this release the user will receive a well defined error message upon sending an empty 'PriceComparison' node: 'When using PriceComparison either AcceptablePriceIncrease or AcceptablePriceDecrease is required.'
  • (08/30/2022) The API was enhanced to inform the user when segments to be priced or cancelled are not found in the reservation, example: '/ExchangeBookingRQ/Itinerary/SegmentPricing/SegmentSelect/@number=150 does not exist within the reservation'
  • (08/30/2022) The API was enhanced to support adding Special Service Requests (SSRs) right after booking new air segments
  • (10/04/2022) When customers attempt to cancel and book identical flight segments they may run into waitlist and other air booking issues, so a warning message will be returned from now on: "Cancelling segments and rebooking identical ones may cause issues with Air Booking."
  • (10/04/2022) Multiple ticket exchanges - corrected error handling when the first ticket exchange fails (reported under [ASTSP-439]). If the API encounters an error during the first ticket exchange, the API will stop processing, because otherwise entering another loop might cause issues with the state of the PNR. The API will now stop processing upon encountering errors during Automated Exchanges Comparison, Price Comparison, Automated Exchanges Confirmation, and End Transaction steps.
  • (04/04/2023) - From now on, in the case of multiple ticket exchanges, if a process for one of the tickets fails, the API will attempt to re-try generation of Price Quote Reissue Record up to 3 times (initial failure + 3 retries). This change is meant to help you work around any synchronization issues between downstream service providers.
  • (04/04/2023) - Removed obsolete .PostProcessing.acceptIncompleteTransactions - The attribute was never supported and its removal is meant to polish the request schema document
  • (05/30/2023) Added capability to pass PQR associated information on refundable amount to be collected on EMD at ExchangeConfirmation.RefundableAmountOnEMD.


  • The API will now use and orchestrated EnhancedEndTransactionRQ instead of low-level EndTransactionLLSRQ. The internal orchestrated API introduces capability of recovering from known end transaction errors, which will simplify the exchange booking process.
  • Corrected business logic related to .ExchangeComparison.ExchangeSegment. As of the release date the API will properly pass the exchange segment information to downline services.
  • (03/08/2022) Added support for ExchangeBookingRQ.targetCity - From now on the customers will be able to specify the pseudo city code where they wish to create the price quote reissue record.
  • (03/08/2022) The API will now validate internal agency setting to check whether the Automatic Segment Arrange setting is enabled (TJR AZA). If not, the API will return the following warning : "Automatic Segment Arrange TJR flag is not enabled. The flight segments may be out of order."
  • (03/08/2022) Added a reservation redisplay right after flight segment cancellation step. In some cases, lack of such action could prevent automated segment rearrangement.

API Information

Format
JSON
Endpoint
/v1.0.1/exchange/booking
Current Version
1.0.1
Environment
Production

What's New

  • The API will now use and orchestrated EnhancedEndTransactionRQ instead of low-level EndTransactionLLSRQ. The internal orchestrated API introduces capability of recovering from known end transaction errors, which will simplify the exchange booking process.
  • Corrected business logic related to .ExchangeComparison.ExchangeSegment. As of the release date the API will properly pass the exchange segment information to downline services.
  • (03/08/2022) Added support for ExchangeBookingRQ.targetCity - From now on the customers will be able to specify the pseudo city code where they wish to create the price quote reissue record.
  • (03/08/2022) The API will now validate internal agency setting to check whether the Automatic Segment Arrange setting is enabled (TJR AZA). If not, the API will return the following warning : "Automatic Segment Arrange TJR flag is not enabled. The flight segments may be out of order."
  • (03/08/2022) Added a reservation redisplay right after flight segment cancellation step. In some cases, lack of such action could prevent automated segment rearrangement.


  • Initial version. Provides the capability to update the itinerary and create a Price Quote Reissue Record for a ticket exchange in a single API call.
  • Provides the capability to specify a price tolerance threashold for the Automated Exchanges Comparison response
  • Returns details of the generated Price Quote Reissue record
  • Manages sessions on behalf of the client application
  • Introduces error handling to ensure the successful issuance of a PQR
  • Handles Context change/AAA

API Information

Format
JSON
Endpoint
/POST /v1.0.0/exchange/booking
Current Version
1.0.0
Environment
Production

What's New

  • Initial version. Provides the capability to update the itinerary and create a Price Quote Reissue Record for a ticket exchange in a single API call.
  • Provides the capability to specify a price tolerance threashold for the Automated Exchanges Comparison response
  • Returns details of the generated Price Quote Reissue record
  • Manages sessions on behalf of the client application
  • Introduces error handling to ensure the successful issuance of a PQR
  • Handles Context change/AAA