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

Property-family facet initialization Inspect filters specifically for the destination-based property-list workflow.
Required stay context for facets Supply both dates alongside the destination identity.
Documented property genericId source Validate returned filter values before composing categories-filter.
Occupancy-sensitive facet refresh Reassess property choices when guests, rooms, or dates change.

Live API Demo

GET /api/project/booking/properties-list-filters

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-list-filters?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&dest_id=20088325&dest_type=city'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →