Get Hotel Facilities by ID

View all Booking.com Hotel & Travel Data endpoints →

Inspect documented facilities for hotel_id with optional checkin_date, checkout_date, currency_code, and language_code. Omitted dates are documented as the current date through four days later; send explicit dates to align with a selected stay. This dedicated facilities response was not live-validated and should not be assumed to match facilities_block in the tested hotel-details response.

API Features

ID-based amenity inspection Focus the request on facilities for one known numeric hotel ID.
Facilities request aligned to dates Use the same check-in and check-out as the traveler's chosen stay.
Dedicated facilities schema check Validate this endpoint separately from the facilities embedded in hotel details.
Amenity reporting gaps preserved Keep missing or ambiguous facility information distinct from a confirmed absence.

Live API Demo

GET /api/project/booking/get-hotel-facilities

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-hotel-facilities?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

Are these facilities identical to facilities_block in hotel details?

That parity has not been verified. The tested details response contains facilities_block.facilities, but the dedicated facilities route was not live-validated.

Why pass dates for a facility lookup?

The endpoint accepts stay dates and documents a rolling four-day default. Supply the selected dates to keep the facility lookup aligned with the accommodation request.

Related operations

Guides

View Subscription Plans →