Get Property Facilities by Detail ID

View all Booking.com Hotel & Travel Data endpoints →

Inspect documented property facilities using detail_id with optional language_code. This route has no numeric hotel_id, stay-date, or currency inputs. Retain the properties-workflow identifier provenance and do not substitute an unrelated hotel or city ID. Its live response was not validated; inspect actual facility fields and omissions before attaching amenities to a property record.

API Features

Facilities keyed by detail_id Request amenities with the dedicated properties-workflow identifier.
Property facility language input Select a supported language_code while retaining the same detail_id.
No date or currency aliasing Keep this narrower request separate from numeric-hotel facility lookups.
Property amenity coverage inspection Check actual reported facilities and missing fields before rendering badges.

Live API Demo

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

Use Cases

Frequently asked questions

Can I send hotel_id or checkin_date here?

No. This operation exposes detail_id and optional language_code only. Numeric hotel facility lookup is a different endpoint.

Does a missing amenity prove it is unavailable?

No. Inspect the response and preserve missing data separately from a confirmed negative. This detail_id facilities route was not live-validated.

Related operations

Guides

View Subscription Plans →