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

One-way minimum-price variant Evaluate the dedicated route separately from ordinary one-way offer search.
Fixed-date fare screening context Hold route, departure day, and passenger configuration together.
Stop-limited low-price evaluation Compare documented direct or limited-stop preferences without claiming exhaustive fare coverage.
Minimum output requires validation Inspect actual price fields instead of inferring one scalar minimum from the route name.

Live API Demo

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

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-oneway?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

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.

Related operations

Guides

View Subscription Plans →