Next Leg Search API Reference

POST

catalog/search/catalogproductofferings/buildnext

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 Next Leg Search API to return offers for the next legClosed The flight or connecting flights between one origin and destination pair. For example, on a round-trip flight, LAX > MSP could be the first leg (aka outbound leg) and MSP > DEN > LAX could be the second leg (aka inbound leg). The JSON APIs use the term product (see below) to represent one leg of the itinerary. of an itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey. after a leg-based round-trip Search. A leg-basedClosed A Search that returns offers for only the first leg of the itinerary. Must be followed by a Next Leg Search request that selects an offer for the first leg and returns offers to combine with that leg. A multi-city itinerary requires another Next Leg Search for the third leg. See the Air Shopping Guide for details. See journey-based above. Search response returns offers for only the outbound leg of the itinerary, and Next Leg Search is then required to return offers for the next leg of the trip.

For a multi-cityClosed An itinerary that includes multiple destinations; e.g., LHR > CDG > AMS > BCN. itinerary, send an additional Next Leg Search request for each remaining leg. GDSClosed Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the JSON APIs, GDS content is distributed from Travelport. supports searching for up to six O&DClosed Origin and destination (O&D) pair, or one leg of an itinerary. In the JSON APIs, product is the term for the flight/s on one leg. pairs (legs of the itinerary) while three are supported for NDCClosed New Distribution Capability, an XML standard for exchanging data that supports airlines in distributing their content directly to online travel agencies. See the NDC Guide..

Any modifiers or indicators sent in the Search request carry over to the Next Leg Search request and are not re-sent.

Request

Query Parameters

None.

Request Body

The Next Leg Search request payload sends identifiers for the preceding search 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 to select for the first leg.

Response

The Next Leg Search response uses the same structure and returns the same objects as the Search response. The only differences are:

  • The first instance of CatalogProductOffering (id o1) is the offer and product sent in the Next Leg Search request. This is the selected offer and product for the first leg.
  • Subsequent instances of CatalogProductOffering are offers for the second leg.

Example Request

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

The Next Leg Search example request below is a follow-on request to a preceding round-tripClosed An itinerary in which travel goes to a single destination and returns to the origin. E.g., LHR > CDG and CDG > LHR. leg-based Search request; see the Search API Reference for the example request that would be sent before this request. This request sends the transaction identifier from the response to that request (CatalogProductOfferingsIdentifier/Identifier) and sends identifiers for the offer and product from that response to select for the first leg of the itinerary (CatalogProductOfferingIdentifier for the offer and ProductIdentifier for the product).

Example Response

The Next Leg Search example request below is an excerpt from the response to the above request. It is an excerpt through the end of the offers in CatalogProductOfferings and does not include ReferenceList data for brevity.

This example returns two instances of CatalogProductOffering:

For brevity, , and the ReferenceList object and all but two instances of ProductBrandOptions for the second CatalogProductOffering have been edited out of the excerpt.