Search Round-Trip Flight Offers
View all Booking.com Hotel & Travel Data endpoints →Search documented return itineraries using leavingFrom, goingTo, departureDate, and returnDate with a consistent cabin and passenger configuration. Optional outbound/return time bands, airline, stops, duration, sorting, and paging constrain the request. Documented defaults are departure tomorrow and return five days after departure; use explicit dates instead. Documentation references flight-offer tokens for detail lookup, but live return-flight fields and pricing were not validated.
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-roundtrip API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/flights-search-roundtrip?key=<API_KEY>&directFlightsOnly=false&goingTo=LOS&leavingFrom=JFK'
Query Result
Use Cases
- Evaluate weekend return-trip candidates for fixed travel dates.
- Compare cheapest and fastest ordering for a single round-trip passenger configuration.
- Inspect return-time constraints for a traveler who must be home before work.
- Review selected return-itinerary details without requesting every offer individually.
Frequently asked questions
What defaults apply to omitted return-trip dates?
Documentation describes departure as the current date plus one day and return as departureDate plus five days. Set both dates for an intentional trip.
Can I constrain outbound and return times separately?
Separate documented time-band fields exist for each direction. Their actual effect and live response fields were not validated.