Hotel Guest Reviews API - Property-Specific Pagination

Request the documented guest-review lookup with required hotelId and optional numeric page/limit query parameters. Use a property ID selected from hotel search. Review fields, pagination indexing, accepted limits and total coverage have not been independently verified, so do not assume a particular page origin, maximum page size or exhaustive review export. Inspect returned review records and any paging information before requesting another page. Keep reviews associated with the selected property, distinguish fetched review samples from the hotel's complete guest-feedback population, and only analyze review text when it is actually returned.

API Features

Property-specific guest feedback A required hotelId anchors the request to a selected property's reviews rather than a destination-wide accommodation search.

Explicit review-page inputs Optional page and limit values control the documented paging request; defaults, indexing and accepted bounds must be confirmed from actual behavior.

Review-record schema inspection Check available review attributes and text before designing a review explorer or assuming a fixed guest-rating structure.

Fetched-sample transparency Report how many records your application fetched without presenting a page or partial set as every review of the hotel.

Live API Demo

GET /api/project/skyscanner/hotels-get-hotel-reviews

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/hotels-get-hotel-reviews?key=<API_KEY>&hotelId=<hotelId>'

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/hotels-get-hotel-reviews?key=<API_KEY>&hotelId=<hotelId>'

📢

Need Help?

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

Use Cases

Create a property-specific review explorer that requests another page only after the current payload's pagination behavior is understood.
Compare guest-feedback themes across shortlisted hotels when review text is available, showing explicit fetched sample sizes.
Keep review pages linked to their hotelId so feedback from different properties cannot be accidentally mixed.
Let a traveler inspect an additional review sample without assuming a complete review archive is available in one request.

Frequently asked questions

Where does review page numbering start, and what is the maximum limit?

page and limit are optional numeric inputs, but indexing, defaults and accepted bounds have not been independently verified. Inspect the actual paging information and behavior before making bounded follow-up requests rather than inventing fixed rules.

Can I retrieve every review at once and analyze the text?

Complete review export is not guaranteed. Verify returned fields and coverage, disclose how many sample records were fetched, and associate each page with the correct hotelId. Analyze themes or sentiment only if actual review text is present; do not represent a partial sample as every guest's opinion.

Related operations

Guides

View Subscription Plans →

Retrieve Guest Reviews for a Hotel