AirPrice Reference Payload API Reference

POST

price/offers/buildfromcatalogproductofferings

Base path:

Pre-production https://api.pp.travelport.com/11/air/

Production https://api.travelport.com/11/air/

Related Content: Air Pricing Guide, AirPrice Full Payload API Reference

The AirPrice API confirms pricing on air search results. While air pricing is generally an optional but recommended step, it is required for low cost carriers and some NDC carriers.

This API reference documents the reference payload request, which sends identifiers from a response from the Search API. Supported for both NDC and GDS.

To use the AirPrice reference payload request, your initial Search request must send offersPerPage to invoke caching if that Search was journey-based (leg-based search results are always cached).

Request

Query Parameters

None.

Request Body

Basic AirPrice Request - Reference Payload

The reference payload sends identifiers as mapped below from the Search response. Use this same payload to price from a Next Leg Search response.

PricingModifiersAir (optional pricing modifiers)

If any search modifiers were included in the Search request, those modifiers are cached and sent with the AirPrice request. If you send any price modifiers in the AirPrice request, any cached modifiers are discarded and only the modifiers sent in the AirPrice request are used.

Response

The AirPrice response is the same for both reference and full payload requests. The basic response format below is also returned by Standalone Price, except that Standalone Price does not return terms and conditions (TermsAndConditions object).

The tables in this section break down the AirPrice response into several of its objects to list all information in each. See Air Pricing Guide for response layout diagrams and description.

If the AirPrice request set returnBrandedFaresInd to return brand details, the response returns the ReferenceList object to consolidate brand details in ReferenceListBrand. ReferenceListBrand is noted below as conditional.

Top-level Response Objects

OfferID

Result

ReferenceList

AirPrice returns ReferenceList only when brand details were requested with returnBrandedFaresInd.

Example Request

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

The following request includes frequent flyer details in the CustomerLoyalty object.

The following request includes the SellCity pricing modifier, supported only for GDS.

The following request includes PaymentCriteria to request the return of any OB fees charged based on credit card BIN.

The following request includes the includeSplitPaymentInd indicator to request pricing for split ticketing offers from a previous Search response.

 

Example Response

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.

The response is the same for both full payload and reference payload requests. All examples below could be returned for either request.

In the following examples, brand details were not requested.

In the following example response, brand details were requested (returnBrandedFaresInd), so the response includes ReferenceList/ReferenceListBrand listing brand attributes.

In the following pricing example for NDC, the credit card BIN was sent in the response to return OB fees. Supported for both NDC and GDS.

The following response is for a split ticketing offer from a previous Search response. It returns pricing for each of two offers instead of one combined offer. For brevity the TermsAndConditionsFull objects in each instance of Offer were truncated.