Booking Search Properties by Location API

Search the documented property-list workflow with location and required checkin_date/checkout_date. Optional adults, children, children_age, rooms, min_bedrooms, min_bathrooms, min_beds, category filters, currency, language, page, and sort support accommodation research. Keep the exact categories-filter parameter name for this family. This location-based property response was not live-validated; inspect returned geography, property identities, and capacity semantics before using it for family stays.

API Features

Required dates for location property lists Supply both stay dates rather than relying on hotel-search defaults.

Family and group property inputs Use documented child count and ages alongside adults and rooms.

Minimum capacity preference fields Inspect behavior of min_bedrooms, min_bathrooms, and min_beds before using them as guarantees.

Property-family category spelling Preserve categories-filter for this endpoint instead of the hotel family's underscore spelling.

Live API Demo

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

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-location?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&location=<location>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-location?key=<API_KEY>&checkin_date=<checkin_date>&checkout_date=<checkout_date>&location=<location>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Evaluate apartment-oriented accommodation discovery for a confirmed destination.
Prototype a multi-bedroom family-stay shortlist with explicit dates.
Inspect how bed and bathroom preferences affect property-list results.
Test child-count and age combinations before designing family accommodation filters.

Frequently asked questions

Are stay dates required for this property list?

Yes. checkin_date and checkout_date are required, together with location. This differs from hotel routes with optional date inputs.

Can I reuse hotel-search parameter names unchanged?

Not blindly. This family uses categories-filter and minimum-capacity inputs with its own names. Validate the actual property response because this route was not live-tested.

Related operations

Guides

View Subscription Plans →