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
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/flights-search-minprice-roundtrip 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'
Query Result
Use Cases
- Evaluate explicit weekend date pairs using the return minimum-price variant.
- Compare cabin constraints within a single fixed return itinerary.
- Inspect the effect of documented outbound and return time windows on candidate data.
- Validate minimum-price response structure before selecting fields for a return-fare experiment.
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.