Flight Specific Search Reference Payload API Reference

POST

catalog/search/catalogproductofferings/buildoptions

Base path:

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

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

Related Content: Air Shopping Guide, Search Workflow Diagrams

Use the Flight Specific Search API reference payloadClosed In the JSON APIs, an API call that sends identifers referring to a previous response for the itinerary to be shopped, priced, added, etc. instead of full itinerary details. request to return additional upsellsClosed A fare presented along with the base fare as a higher level of service, usually a branded fare. Returned if filed by the carrier and requested with maxNumberOfUpsellsToReturn in the Search request. (you can set up to 99) for any product or products returned by a Search or Next Leg Search. The reference payload sends an identifier referencing a previous response and the offerClosed In the JSON Search APIs, an offer is a product available at a specific price under a set of terms and conditions. An offer includes the flight or connecting flights for one leg of the itinerary, plus a service level that includes the cabin class and any fare codes that may apply. At booking, the selected offer from the Search response - including the flight/s, service level, price, terms and conditions, and brand if applicable - is converted into a single Offer object that is subsequently returned for that booking. and product identifiers. The full payload request does not reference a previous Search response.

Request

Query Parameters

None.

Request Body

The Flight Specific Search POST request requires a message payload with identifiers for the transaction, the offer, and the product for which you want to return additional upsells. The following table details the required objects.

Response

The Flight Specific Search response uses the same structure and returns the same objects as the Search response. The differences are:

  • One instance of CatalogProductOffering (id o1) is returned for each offer sent in the request.
  • One instance of ReferenceListProduct/Product is returned for each product sent in the request.

Example Request

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

The following example request sends offer and product identifiers from each leg (CatalogProductOffering) of the preceding Search request to return all filed upsells for those flights on each leg.

Example Response

The following example excerpt returns the base fare and 8 upsells (BrandRef values b0-8) for the outbound leg and the base fare and seven upsells (BrandRef values b0-7) for the inbound leg. The base fare and each upsell are each returned in an instance of ProductBrandOffering. The ReferenceList objects consolidating details were removed for brevity; see the developer toolkits for full examples.