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

Outbound and return date pairing Keep both itinerary dates explicit when evaluating a return trip.
Separate return-flight time bands Apply documented return arrival/departure windows independently of outbound bands.
Round-trip passenger consistency Hold cabin and traveler ages fixed when comparing date pairs.
Return-offer detail selection Inspect a selected returned offer before carrying its token to details.

Live API Demo

GET /api/project/booking/flights-search-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-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

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.

Related operations

Guides

View Subscription Plans →