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
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/properties-detail-facilities API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-detail-facilities?key=<API_KEY>&detail_id=<detail_id>'
Query Result
Use Cases
- Evaluate amenity enrichment for a catalog that already stores detail_id values.
- Audit facility-field coverage during a property identifier migration.
- Compare localized facility metadata for a single known property detail ID.
- Check whether property-level amenities can support an internal catalog quality review.
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.