Read Paginated Hotel Reviews
View all Booking.com Hotel & Travel Data endpoints →Request review pages for hotel_id using page, page_size, and sort, with optional traveler-type, review-language, time-of-year, and topic filters. Documentation describes comma-separated filter values and defaults of page=1, page_size=25, and sort_most_relevant. Discover supported filter and sorter identifiers through the matching review-metadata operations. This review response was not live-validated; review row fields, totals, and paging behavior must be inspected rather than inferred from hotel search.
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/get-hotel-review API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/get-hotel-review?key=<API_KEY>&hotel_id=180769'
Query Result
Use Cases
- Collect a bounded review sample for a permitted internal accommodation quality audit.
- Compare family-with-children feedback with solo-traveler feedback for one hotel.
- Evaluate recent-review ordering for a traveler-service monitoring prototype.
- Study review-language coverage without treating an English-only sample as representative.
Frequently asked questions
How do filter_language and language_code differ?
filter_language is documented for filtering the language of reviews; language_code is a display-language preference. Validate the returned review content because this route was not live-tested.
Where do review sort and topic identifiers come from?
Use the matching hotel review sort and filter metadata endpoints for the same hotel. Documentation lists sort_most_relevant, sort_recent_desc, sort_recent_asc, and sort_score_desc, but actual available choices should be checked.