Search API Reference

POST

catalog/search/catalogproductofferings

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, Next Leg Search API Reference

The Search API is the first step in the JSON API travel booking workflow. Send a Search request to return offers for flights between specific locations.

Request

Headers

Header Field

Description

Required

isJourney

Setting to return either a journey- or leg-based response:

  • true: Journey-based response: Returns offers for all legs of the itinerary. Default behavior.
  • false: Leg-based response: Returns offers for only the first leg of the itinerary. Must be followed with a Next Leg Search to return offers on second leg.
Planned for deprecation. Best practice is not to use IsJourney but instead send the payload object CustomResponseModifiersAir/SearchRepresentation. If both IsJourney and SearchRepresentation are sent and have contradictory values, Search uses the value in SearchRepresentation and disregards IsJourney.

Optional

If not sent default is true.

taxBreakdown

Setting whether to return a tax breakdown for each offer. Send with a value of true to return a tax breakdown or false not to return it.

GDS only; not supported for NDC.

Optional

If not sent default is true.

Query Parameters

None.

Request Body

Basic Search Request

SearchModifiersAir (optional journey modifiers)

PricingModifiersAir (optional pricing modifiers)

SearchControlConsoleChannelID

The Search API supports the Travelport Content Optimizer (formerly known as Search Control Console/SCC) for GDS content only. Travel agency administrators use Content Optimizer to create business rules for filtering certain air shopping results. If your client's application does not use Content Optimizer, do not use these attributes. Contact your Travelport representative if you would like additional information.

Response

CatalogProductOfferingsResponse and CatalogProductOfferings

Result

ReferenceList

 

Example Request

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

The following example requests a GDS round-trip journey-based search, which will return flight options for both legs of the itinerary. No additional search requests are required. It also sends a preference of Preferred for carrier UA, and requests a maximum of one upsell to return. As required for any journey-based round-trip search that will be referenced later in the workflow, this request sends offersPerPage set to any positive number to invoke caching to support subsequent reference-based requests.

The following example sends a request for a one-way NDC search with a carrier preference of Permitted for SQ.

The following example sends PTCs for a one-way GDS search for one adult and one child, plus modifiers requesting a search by departure time range and preferences for business class, refundable, and nonstop fares, No upsells are requested.

The following example requests a GDS round-trip leg-based search, which will return flight options for only the first leg of the itinerary, as requested with SearchRepresentation = Leg. This request must be followed by a Next Leg Search request, see the Next Leg Search API Reference for the follow-on request example. It also sends a preference of Permitted for carrier UA, and requests up to four upsells. Unlike journey-based searches, it does not need to send offersPerPage to invoke caching because leg-based search results are cached by default.

The following example sends the includeSplitPaymentInd indicator to request split ticketing.

Example Response

For additional examples and scenarios, download the developer toolkits and see Using Postman and Developer Toolkits.
If your workflow subsequently references a journey-based search result, the Search request must send offersPerPage set to any positive number. This setting invokes caching so that search results can be referenced later. A journey-based search returns all legs of the itinerary, while a leg-based search returns one leg at a time and is cached by default. If a journey-based Search request does not send offersPerPage, the reference payload requests for Flight Specific Search, AirPrice, and Add Offer will fail.

The following example response excerpt is for the request above for a round-trip journey-based search. For brevity, this excerpt was edited to remove the ReferenceList object, and all but two instances of ProductBrandOffering in each of the two instances of CatalogProductOffering, one for the outbound and another for the inbound flight options. See the developer toolkits for full examples. The base fare and each upsell are each returned in an instance of ProductBrandOffering, usually with BrandRef b0 for the base fare and BrandRef b1+ for upsells.

The following example sends a request for a one-way NDC search with a carrier preference of Permitted for SQ. For brevity, this excerpt was edited to remove the ReferenceList object, and all but two instances of ProductBrandOffering in CatalogProductOffering. See the developer toolkits for full examples.

The following example is the response to the example request above for one adult and one child and preferences for business class, refundable, and nonstop fares, No upsells were returned per the request.

The following example is an excerpt showing the PriceBreakdownAir object for a one-way offer for split ticketing; as indicated with the CombinabilityCode value of j0. This offer can be combined with any offer on the remaining leg of the itinerary that also has a CombinabilityCode value of j0.