Discover Property List Filters
View all Booking.com Hotel & Travel Data endpoints →Retrieve documented property-list filter metadata using a known dest_id/dest_type and required stay dates. Keep adults, child count/ages, rooms, currency, language, and any existing categories-filter aligned with the intended property search. Documentation references data.filters.options.genericId for filter values. The live metadata response and available facet coverage were not validated; inspect actual choices before assembling a property-list filter request.
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-list-filters API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-filters?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&dest_id=20088325&dest_type=city'
Query Result
Use Cases
- Initialize vacation-rental search controls for a confirmed destination and stay.
- Discover supported property-type tokens before an apartment research query.
- Refresh property facets after the family guest configuration changes.
- Audit stale genericId values in saved property-list requests.
Frequently asked questions
Where should categories-filter values come from?
Documentation points to data.filters.options.genericId in this property-filter workflow. Check the actual returned choices; this route was not live-validated.
Can I request filters without stay dates?
No. Both checkin_date and checkout_date are required here, as are dest_id and dest_type. Keep the context aligned with the property list you intend to query.