Evaluate One-Way Minimum-Price Search
View all Booking.com Hotel & Travel Data endpoints →Evaluate the documented minimum-price variant for a one-way airport pair with departureDate, passengers, cabin, airline, stop, duration, time-band, page, and sort preferences. A missing departure date is documented as tomorrow. This variant was not live-validated: no single-minimum output field, comparison coverage, or returned-offer schema is promised. Treat it as current date-specific search research, not an all-time or historical lowest-fare service.
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-oneway API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/flights-search-minprice-oneway?key=<API_KEY>&directFlightsOnly=false&goingTo=LOS&leavingFrom=JFK'
Query Result
Use Cases
- Evaluate the minimum-price variant across a small set of departure dates.
- Compare documented stop constraints for one fixed one-way fare-research case.
- Inspect which price fields this variant returns before designing a low-fare panel.
- Test cabin changes without describing the resulting snapshots as historical fare lows.
Frequently asked questions
Does this promise one numeric lowest-fare value?
No actual response was validated. Inspect the returned fields before interpreting the operation as a scalar minimum-price service.
Does minimum price mean the cheapest fare ever observed?
No historical-minimum feed was established. This is a documented date-specific search variant, with fares and availability unverified live.