Flight Specific Search Full 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's full payloadClosed In the JSON APIs, an API call that sends all details of the flight/s to be shopped, priced, added to the workbench, etc. instead of sending a reference to an offer in a previous API response. 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. for one or more flights. You can request up to 99 upsells.

Request

Query Parameters

None.

Request Body

The Flight Specific Search POST request requires a message payload with itineraryClosed The entire trip on a booking, including all flights on all legs. Also called a journey. details. The following table details the required objects.

If SpecificFlightCriteria/cabin or /classOfService is sent, those are ignored.

Response

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

  • Only one instance of CatalogProductOffering (id o1) is returned, as this includes all upsells for the one product sent in the request.
  • Only one instance of ReferenceListProduct/Product is returned, as one product was sent in the request.

Example Request

The following example request sends full flight details to request all upsells on a one-way GDS itinerary with connecting flights.

Example Response

The following example response excerpt returns the base fare (b0) and 11upsell fares (b1-11), each in an instance of ProductBrandOffering. The Result and ReferenceList objects have been edited out for brevity; see the developer toolkits for full examples.