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

Destination pair in the property family Keep dest_id and dest_type together for this property-list workflow.
Mandatory property-list stay window Supply both dates for destination-based property retrieval.
Minimum space preferences by destination Use this route's documented bedroom, bathroom, and bed inputs.
Property-list pagination kept independent Inspect returned paging rather than copying the observed stays-search behavior.

Live API Demo

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

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-dest?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

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.

Related operations

Guides

View Subscription Plans →