List Hotel Rooms for a Stay

View all Booking.com Hotel & Travel Data endpoints →

Request room options for a known hotel_id and carry checkin_date, checkout_date, adults, children_age, rooms, and currency_code from the selected stay. Optional units and temperature_unit control documented display preferences. This dedicated room-list route was not live-validated; do not assume it has the same schema as the tested hotel-details response. Inspect returned room identities, amounts, occupancy, and conditions before building a room selector. Retrieval does not hold or purchase a room.

API Features

Dedicated room-option request Inspect rooms independently after a traveler has chosen a property.
Guest configuration carried into rooms Keep adults and child ages aligned with the originating accommodation search.
Room-list display preferences Select metric or imperial units and a documented temperature scale when needed.
Offer-condition review boundary Validate the actual room response before interpreting price units or reservation conditions.

Live API Demo

GET /api/project/booking/get-room-list

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/get-room-list?key=<API_KEY>&hotel_id=180769'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Should I reuse the search occupancy for room retrieval?

Yes. Carry the same adults, child ages, rooms, dates, and currency so you do not compare offers for different stays.

Can I assume this route returns the tested hotel-details schema?

No. The dedicated room-list response was not live-validated. Check its returned fields and room conditions before integrating it into a booking-oriented interface.

Related operations

Guides

View Subscription Plans →