Booking Discover Hotel Review Sort Options API

Retrieve documented review sorting metadata for hotel_id with optional language_code and currency_code. Documentation references categories[].id values for the sort input in get-hotel-review, including relevance, recency, and score orderings. These handoffs were not live-validated. Inspect actual supported identifiers before enabling newest-first collection or presenting a score-based ordering choice.

API Features

Review-order metadata lookup Request sorting choices specifically for review pages, not hotel listings.

Documented category ID handoff Inspect categories[].id before setting the review sort parameter.

Recency-order support check Validate the actual newest-first choice before a monitoring-oriented collection.

Displayed sort labels kept separate Preserve machine sort IDs when localizing review-order labels.

Live API Demo

GET /api/project/booking/get-hotel-review-sort

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/get-hotel-review-sort?key=<API_KEY>&hotel_id=180769'

curl -X GET 'https://api.opendata-api.com/api/project/booking/get-hotel-review-sort?key=<API_KEY>&hotel_id=180769'

📢

Need Help?

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

Use Cases

Populate a review-order selector from a selected hotel's metadata.
Verify newest-first sorting before a bounded recent-feedback audit.
Check whether score-based review ordering is actually offered.
Audit accidental use of hotel-list ranking tokens in review requests.

Frequently asked questions

Which values are documented for review sorting?

Examples include sort_most_relevant, sort_recent_desc, sort_recent_asc, and sort_score_desc. Check actual metadata identifiers for the selected hotel before use.

Are these hotel-search sorters?

No. This operation supplies review ordering choices for get-hotel-review, not hotel-list ranking tokens. Its live response was not validated.

Related operations

Guides

View Subscription Plans →