Search to SOAP/XML AirPricing

After running a JSON Search request, you can choose to switch to the Travelport SOAP/XML APIs to continue the workflow, continuing with an Air Pricing request to confirm pricing and availability on an itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey. returned in JSON Search.

This topic discusses how to move from Search to SOAP/XML Air Pricing, including required and optional data and examples of the requests and responses in the flow.

In this topic:

Required and Optional Data

Per the following sections, in your SOAP/XML Air Price request you must include specific objects from the Search response, plus additional data. Other Search response data is optional.

Required JSON Search Response Objects in AirPrice Request

All of the following data from the Search response is required in the Air Pricing request:

Optional JSON Search Response Objects in AirPrice Request

The following data from the Search response is optional in the Air Pricing request:

When ReferenceListProduct/Product(@type ProductAir) returns multiple instances of FlightSegment, the sequence defines the flights as connecting.

Other Required Information in AirPrice Request

In addition to the information from the Search response, all of the following is required in the SOAP/XML Air Pricing request (AirPriceReq):

  • The Billing Point of Sale Info Origin Application you use for Travelport SOAP/XML APIs.

  • All of the following for each segment:

    • A unique Key value.

    • A group number. Note the following:

      • When the flight is not connecting to another flight, the Group number of the air segment is unique.

      • When the flight is connecting to another flight., the Group number of the air segments is the same (Search sequence "1" "2" "3" = uAPI Group "1" "1" "1").

    • A connectionClosed A change to a different airplane on the way to the destination. indicator. Note the following:

      • When the flight is connecting to another flight and the JSON API Search response returns the boundFlightsInd, AirSegment/Connection must be sent in the SOAP/XML AirPrice Request for the air segment.

    • The provider code you use for SOAP/XML APIs.

  • A unique Key value for each passenger.

  • The Air pricing command.

Search to AirPricing Object Mapping

The table below maps the individual objects from the Search response to their corresponding location in the SOAP/XML Air Pricing request.

JSON Search Response Object...

... maps to SOAP/XML Air Pricing Request Element

ReferenceListFlight

AirItinerary

Flight/carrier

AirSegment @Carrier

Flight/number

AirSegment @FlightNumber

Flight/equipment AirSegment @Equipment

Departure/location

AirSegment @Origin

Arrival/location

AirSegment @Destination

Departure/date + /time

AirSegment @DepartureTime

Arrival/date + /time

AirSegment @ArrivalTime

ReferenceListProduct/Product (@type ProductAir)/FlightSegment/sequence

AirSegment @Group (see notes above on Group number)

ReferenceListProduct/Product (@type ProductAir)/FlightSegment/boundFlightsInd

AirSegment/Connection (see notes above on Connection indicator)

ReferenceListProduct/Product (@type ProductAir)/PassengerFlight/passengerTypeCode

SearchPassenger @Code

SearchPassenger @BookingTravelerRef

ReferenceListBrand/Brand/tier

AirPricingCommand/AirSegmentPricingModifiers @BrandTier

ReferenceListProduct/Product (@type ProductAir)/PassengerFlight/FlightProduct/classOfService

AirPricingCommand/AirSegmentPricingModifiers/PermittedBookingCodes/BookingCode @Code

AirPricingCommand/AirSegmentPricingModifiers @AirSegmentRef

Examples

The following example Search request is for a one-wayClosed An itinerary with a single destination; e.g., LHR > CDG. itinerary from SFO to DSM with one passenger.

For brevity, the following examples omits object instances not relevant to this flow. Data from segments 37 and 38 (37s and 38s) and product 0 (p0) from the following example are sent in the AirPricing example that follows.

The following example AirPricing request sends the required details from the Search response above.

The following example AirPricing response returns pricing for the flights sent in the AirPricing request above.