Get vacation rental details by rentalId
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Look up property content for one known vacation rental using the required rentalId query string. Preserve the full identifier; the parameter documentation points to a rental-search result as its source. This endpoint does not accept stay dates, guest counts or a page number. No observed probe response was supplied for this operation. The supplied source response example is truncated: its visible data object includes amenities, geoCoordinates.lat and geoCoordinates.lng, nearbyGeosInfo, overview and paymentStats.totalPayments, followed by the beginning of photos. Visible overview fields include name, descriptions, averageRatingNumber, userReviewCount, roomCount, bathCount, sleepCount, minStay, cancellationPolicy, carRequired, isInstantBook and isOnlineBookable. These are unverified source-example fields, not a complete validated schema or a guarantee of field availability. Inspect the returned structure before using content, coordinates or bookability indicators; this lookup does not make a reservation or provide a dated rate quote.
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-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-details?key=<API_KEY>&rentalId=VacationRentalReview-g60763-d24235431-Sonder_The_Industrialist_Queen_Room-New_York_City_New_York'
Query Result
Use Cases
- Enrich an existing known-ID vacation-rental catalog with returned names, descriptions and capacity fields rather than relying on rental discovery.
- Build a manual content-quality queue for known rentals, classifying unavailable records and request failures only after inspecting the actual lookup response.
- Add amenities and map coordinates to a property comparison view when those documented example fields are present in the returned data.
- Compare returned aggregate ratings and review counts with saved property snapshots to identify listings that need editorial attention.
Frequently asked questions
Where do I get the rentalId for a property-details request?
The parameter documentation points to a rental-search result in the Vacation Rentals collection. This detail lookup does not discover properties. Supply a rentalId already available in your records and preserve its complete string, including the VacationRentalReview prefix and remaining identifier segments.
Can I request details for specific stay dates or a guest count?
No. rentalId is the only exposed input for this operation. Dates and guest counts belong to the separate rental-rates request, not this property-content lookup.
Which property fields are documented in the response example?
The visible portion includes data.amenities, geoCoordinates.lat and lng, nearbyGeosInfo, overview and paymentStats.totalPayments. The overview shows fields for the property name, descriptions, capacity, stay policies and aggregate feedback. The example begins a photos field but is truncated, so it does not establish a complete photo structure or response schema.
Does the property overview include individual guest reviews?
The visible example documents averageRatingNumber and userReviewCount within overview, not individual review items. Use rental-reviews for a separate page-based guest-feedback lookup; do not treat aggregate overview fields as review records.
Have these rental-detail fields been verified by an observed call?
No observed probe was supplied for rental-details. The field descriptions come from a truncated source example and must be checked against actual returned data before you depend on their presence or meaning.