Get Stay Facilities by Query

View all Booking.com Hotel & Travel Data endpoints →

Inspect facilities using query as a known hotel ID, property URL, or supported hotel-name value, with optional check-in/check-out dates, currency, and language. The documented date defaults are the current date through four days later; use explicit dates for a selected stay. This flexible facilities route was not live-validated, so verify the resolved property and actual amenity fields before display.

API Features

Facilities from a property query Accept a documented hotel ID, URL, or name for the facilities lookup.
Query-facilities date alignment Send explicit dates to keep facility information attached to the chosen stay.
Name-based amenity identity check Confirm the hotel before applying returned amenities to a catalog record.
Flexible versus numeric facilities audit Evaluate schema and identity parity separately from numeric hotel facilities.

Live API Demo

GET /api/project/booking/stays-details-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/stays-details-facilities?key=<API_KEY>&query=180769'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Do omitted dates remain fixed for facilities lookup?

No. Documentation describes the current date and four days later. Send both dates when matching a selected stay; the response was not live-validated.

Can a name query be treated as an exact property ID match?

No. Confirm the returned hotel identity and geography before displaying amenities, especially when names are ambiguous.

Related operations

Guides

View Subscription Plans →