Discover Hotel Destination Sorters

View all Booking.com Hotel & Travel Data endpoints →

Retrieve documented ordering choices for a known dest_id/dest_type and search context. Documentation points to option names in the response for hotel sort values; it lists price, bayesian_review_score, distance, property-class orderings, and other choices. This sorter route was not live-validated. Render only returned options applicable to the current hotel destination workflow, not tokens copied from flight or property-list sorting.

API Features

Destination-aware ordering choices Inspect sort options for a particular destination and guest/date context.
Hotel-sort token selection Use documented hotel ordering names rather than display labels as request values.
Price versus guest-review ordering Evaluate supported ranking alternatives before exposing them to travelers.
Sorter-family isolation Keep hotel destination sorters distinct from flight and property-list metadata.

Live API Demo

GET /api/project/booking/search-by-dest-get-sorters

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/search-by-dest-get-sorters?key=<API_KEY>&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 a displayed sorter label as sort?

Use the returned machine option name described by the endpoint documentation, not a translated label.

Are these sorter tokens valid for flights too?

Do not assume that. Flight sorting uses its own documented choices; this route is for the hotel destination-search family and was not live-validated.

Related operations

Guides

View Subscription Plans →