Evaluate Return Minimum-Price Search

View all Booking.com Hotel & Travel Data endpoints →

Evaluate the documented minimum-price return-trip variant using leavingFrom, goingTo, explicit departureDate/returnDate, and consistent passengers and cabin. Optional outbound and return time bands, airline, stop, duration, page, and sort inputs constrain the request. This variant was not live-validated; do not promise a single lowest-fare field, guaranteed savings, or booking availability. Compare only matching route/date/passenger contexts.

API Features

Return-trip minimum-price variant Inspect this documented route independently from ordinary round-trip search.
Two-date fare comparison frame Freeze both departure and return dates when comparing candidate prices.
Directional time limits for low fares Retain separate outbound and return time bands in the research context.
No guaranteed savings claim Validate returned amounts and conditions before describing any offer as cheapest.

Live API Demo

GET /api/project/booking/flights-search-minprice-roundtrip

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-roundtrip?key=<API_KEY>&directFlightsOnly=false&goingTo=LOS&leavingFrom=JFK'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Must I use explicit dates for a return-price comparison?

Use both dates to freeze the trip. Documentation otherwise describes departure tomorrow and return five days later, which changes over time.

Can the result be presented as guaranteed cheapest or bookable?

No. This response was not live-validated and no exhaustive comparison or reservation guarantee was established.

Related operations

Guides

View Subscription Plans →