Search Properties by Destination Pair
View all Booking.com Hotel & Travel Data endpoints →Search the property-list workflow with known dest_id, dest_type, checkin_date, and checkout_date. Optional adults, child count/ages, rooms, minimum bedrooms/bathrooms/beds, categories-filter, currency, language, page, and sort refine the documented request. Accommodation autocomplete is unavailable, so start with an independently known destination pair. This property-list response was not live-validated and must not be assumed to match stays-search pagination or identifiers.
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-dest API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-dest?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&dest_id=20088325&dest_type=city'
Query Result
Use Cases
- Reuse a confirmed destination pair for a group-accommodation research run.
- Evaluate multi-bedroom properties for the same dates across two known cities.
- Test minimum-space preferences in the destination-ID property workflow.
- Audit property-list identifiers before enriching selected accommodation records.
Frequently asked questions
Can I send city:20088325 as dest_id?
Use separate fields: the documented New York pair is dest_id=20088325 and dest_type=city. The prefixed query belongs to stays-search.
Does this return the same 20-row pages as the tested stay search?
That was not established. This is a different property-list route and its response was not live-validated. Inspect its actual page fields and rows.