Booking Discover Property List Sorters API

Inspect documented ordering metadata for the property-list family using dest_id, dest_type, and required check-in/check-out dates. Optional guest, room, category, currency, language, page, and sort inputs retain search context. This metadata response was not live-validated. Use only supported returned property-list sorter identifiers; do not copy tokens from hotel destination search or flight search without validating compatibility.

API Features

Property-list ordering discovery Inspect ranking choices in the dedicated property-list workflow.

Dated sorter context Keep both stay dates tied to the destination used for the metadata request.

Current-filter ordering review Evaluate sort choices under the same guest and category constraints as the list.

Property sorter token isolation Avoid silently substituting hotel or flight ordering identifiers.

Live API Demo

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

API Response (JSON)

{}

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

curl -X GET 'https://api.opendata-api.com/api/project/booking/properties-list-sorters?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.

Use Cases

Populate an ordering selector for a property-list search prototype.
Compare supported property-list rankings for one fixed destination and stay.
Check sorter coverage after changing a vacation-rental filter set.
Review cross-family sort-token reuse during an accommodation catalog migration.

Frequently asked questions

Are these the same sorters as search-by-dest-get-sorters?

No response parity was validated. These belong to the property-list workflow; inspect actual identifiers before reusing them.

Why are dates required for sorter discovery?

They are required by this endpoint's request contract. Keep them aligned with the property list instead of retrieving unrelated ordering metadata.

Related operations

Guides

View Subscription Plans →