Get a page of reviews for a known vacation rental
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Request guest-review data for one known vacation rental with the required rentalId query string and optional numeric page. The parameter documentation specifies a default page number of 1 and points to a rental-search result as the source of rentalId. Preserve the full property identifier when requesting successive pages. No response example or observed probe response was supplied for this operation, so the supplied evidence does not establish an envelope, review-item field names or types, a stable review identifier, page-size metadata or a last-page signal. Inspect actual returned data before designing a parser, choosing a deduplication key or defining pagination stop conditions. The documented inputs do not include language, rating, date-range, page-size or sort filters. This is a vacation-rental feedback lookup, not a hotel-review feed, and pagination does not establish coverage of all historical reviews.
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/tripadvisor-data/rental-reviews API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-reviews?key=<API_KEY>&page=1&rentalId=<rentalId>'
Query Result
Use Cases
- Support an opt-in property-quality review by retrieving successive pages for one rental and deduplicating only after a stable review identity has been verified.
- Develop a multilingual rental-feedback research corpus from fields actually returned and permitted for use, without assuming a language filter or complete history.
- Build an analyst reading queue that records rentalId and page with each result so the source request for a feedback segment remains traceable.
- Create review-theme summaries for a selected rental only after checking that returned content supports analysis, keeping human review separate from automatic moderation decisions.
Frequently asked questions
What do I need to request vacation-rental reviews?
Supply the complete rentalId for a known property. The parameter documentation points to a rental-search result as its source. page is optional and numeric; the documentation specifies a default of 1.
How do I paginate and determine when I have reached the end?
Keep rentalId unchanged and request successive page values, starting with the documented first page of 1. The supplied evidence does not specify page size, total-page metadata, a last-page marker or out-of-range behavior. Establish a stopping rule from the actual response rather than assuming an empty page or a fixed count.
Which review fields and identifiers can my parser rely on?
No response example or observed probe response was supplied for rental-reviews. The evidence therefore does not establish review-item field names, an envelope or a stable identifier. Inspect actual returned data before implementing a parser or selecting a deduplication key.
Can I filter reviews by language, rating or travel date?
No such inputs are documented for this operation. Its exposed parameters are rentalId and page only; there is also no page-size or sort parameter. Any local filtering must depend on fields actually returned and does not change the request contract.
Does paginating this endpoint return every historical review or hotel reviews?
Neither is established. This operation targets vacation-rental feedback by rentalId, not hotel reviews. The existence of a page parameter does not prove completeness, historical coverage or a particular ordering of returned reviews.