Booking Evaluate Multi-City Minimum Prices API

Evaluate the documented minimum-price multi-city variant with aligned comma-separated leavingFrom, goingTo, and multiStopDates lists. Keep traveler ages, adults, cabin, and route constraints consistent across candidate requests. The live response, fare aggregation, leg coverage, and any minimum-price field were not validated. Inspect actual itinerary structure and prices before comparing multi-leg totals; no historical-fare or booking guarantee is implied.

API Features

Multi-city low-price route evaluation Inspect the documented minimum-price variant for a multi-leg itinerary.

Aligned leg-date screening Keep origin, destination, and date entries matched across all legs.

Comparable multi-leg passenger inputs Preserve passenger ages and cabin while evaluating alternate date combinations.

Multi-city total semantics inspection Validate what any returned amount covers before comparing complete itineraries.

Live API Demo

GET /api/project/booking/flights-search-minprice-multi-city

Adults (optional)

Airlines (optional)

Cabin Class (optional)

Children (optional)

Departing Flight Arrival Time (optional)

Departing Flight Departure Time (optional)

Direct Flights Only (optional)

Duration (optional)

Going To *

Language Code (optional)

Leaving From *

Multi Stop Dates *

Page (optional)

Return Flight Arrival Time (optional)

Return Flight Departure Time (optional)

Sort (optional)

Stops (optional)

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/flights-search-minprice-multi-city?key=<API_KEY>&directFlightsOnly=false&goingTo=LOS%2CEWR&leavingFrom=JFK%2CLOS&multiStopDates=<multiStopDates>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/flights-search-minprice-multi-city?key=<API_KEY>&directFlightsOnly=false&goingTo=LOS%2CEWR&leavingFrom=JFK%2CLOS&multiStopDates=<multiStopDates>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Screen a small set of two-leg date combinations for a travel research prototype.
Check that each airport and date list entry maps to the intended leg.
Inspect minimum-price output coverage before comparing multi-city totals.
Evaluate shared cabin constraints across fixed multi-leg candidate requests.

Frequently asked questions

How many dates should multiStopDates contain?

Use one explicit date for each origin/destination leg, preserving list order and matching lengths.

Does this return a guaranteed minimum total for all legs?

That was not validated. Inspect the response, leg coverage, amount semantics, and conditions before drawing a minimum-total conclusion.

Related operations

Guides

View Subscription Plans →