Skip Navigation

Exchange Booking

Air
Pricing
REST API
Travel Agency
Try Now

What is it?

The Exchange Booking API is used to update the itinerary and create a Price Quote Reissue Record for a ticket exchange in a single API call.

Why use it?

You can use this API to:

  • Updates the itinerary and creates a Price Quote Reissue Record for a ticket exchange in a single API call
  • Specifies a price tolerance threshold for the Automated Exchanges Comparison response
  • Returns details of the generated Price Quote Reissue record
  • Manages sessions on behalf of the client application
  • Successfully issues a PQR via error handling

How it works

The Exchange Booking API performs several steps to issue a PQR:

  • Performs an “ignore transaction” to ensure that the work area is clear
  • Retrieves the existing reservation using a record locator provided within the payload
  • Cancels specified PNR air segments and books new segments
  • Performs automated exchange comparison and confirmation calls
  • Commits the newly generated PQR into the PNR and depending on user input, API can retrieve PQR details and/or retrieve full reservation details

How to use

How to generate a Price Quote Reissue Record using Exchange Booking API

  1. A single PQR is generated by sending a single instance of /ExchangeBookingRQ/AutomatedExchanges.

  2. Depending on the user's choices, the API will:

  • Cancel specific air segments (/ExchangeBookingRQ/Cancel)
  • Add new segments to the reservation (/ExchangeBookingRQ/AirBook)
  • Keep specific segments unchanged (/ExchangeBookingRQ/Itinerary/SegmentPricing)
  1. The API then automatically selects segments to pass onto the Automated Exchanges comparison step. The service response will contain the generated PQR number as a default: (/ExchangeBookingRS/ExchangeConfirmation/@PQR_Number)

  2. Depending on the user choice, the service response may include full PQR details: (/ExchangeBookingRQ/PostProcessing/@returnPQRInfo=”true”) or full reservation details (/ExchangeBookingRQ/PostProcessing/@redisplayReservation=”true”)