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
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/search-by-dest-get-sorters 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'
Query Result
Use Cases
- Initialize a hotel sorting selector for a confirmed city search.
- Check whether a price ordering is offered for the chosen stay context.
- Evaluate returned guest-review ordering before ranking a travel shortlist.
- Audit stale sorter identifiers after migrating between hotel-search families.
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.