Booking Search Multi-City Flight Offers API

Search documented multi-city itineraries using comma-separated leavingFrom, goingTo, and multiStopDates lists. Align each origin, destination, and date by leg; use explicit dates rather than the old documentation examples. Optional passengers, cabin, airline, time bands, directFlightsOnly, stops, sort, and page retain itinerary constraints. Live multi-city responses and offer availability were not validated; inspect actual flightOffers and any detail token before use.

API Features

Parallel route lists by leg Align each leavingFrom value with its goingTo destination.

One explicit date per leg Supply matching multiStopDates entries for the intended itinerary.

Shared multi-city traveler context Keep passengers and cabin settings consistent across the documented request.

Multi-leg offer inspection Validate actual leg structure before passing a selected offer to detail lookup.

Live API Demo

GET /api/project/booking/flights-search-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-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-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

Evaluate a two-city business itinerary with one date per flight leg.
Check airport-list alignment before submitting a multi-city search.
Compare documented cabin constraints for an otherwise fixed multi-leg trip.
Inspect selected multi-city offer details after validating the search response.

Frequently asked questions

How should the three comma-separated lists line up?

Use one origin, one destination, and one date for each leg, in matching order. Do not concatenate unrelated airport lists.

Can I use old example multiStopDates?

Choose dates for the actual trip. Fixed historical examples are not reusable availability controls, and this search route was not live-validated.

Related operations

Guides

View Subscription Plans →