Look up availability data for a known vacation rental
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Retrieve availability information for an already known Tripadvisor vacation-rental record using the required string rentalId query parameter. Obtain the full rentalId from a vacation-rental search result and preserve it as returned. This operation exposes no date, date-range, guest-count or pagination inputs, so it cannot express an arbitrary requested stay or a calendar update. No observed probe response is available for this operation. Its unverified, truncated source example shows a data object grouped by year, then abbreviated month, then YYYY-MM-DD date keys whose values are booleans. The example includes historical dates and does not establish current coverage, calendar completeness, the exact meaning of true versus false, or any additional envelope fields. Treat this nesting as an illustrative calendar shape rather than a guaranteed schema. Save retrieval time separately if collecting snapshots, derive calendar granularity only from verified responses and do not equate returned flags with confirmed inventory, prices or a reservation.
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-availability API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-availability?key=<API_KEY>&rentalId=<rentalId>'
Query Result
Use Cases
- Add an availability-inspection panel to a research tool after a user selects an existing vacation-rental record.
- Store rentalId-keyed availability snapshots with a separate retrieval time, without treating historical example dates as current inventory.
- Prototype a calendar parser against the illustrative year/month/date grouping, then validate its structure and flag meanings before production use.
- Explain why an arbitrary check-in/check-out filter cannot be applied at request time, because this lookup has no date query parameters.
- Compare successive verified snapshots for the same rental record while clearly distinguishing returned date flags from reservation confirmation.
Frequently asked questions
Where do I obtain the rentalId?
Use the rentalId from a vacation-rental search result. Pass the complete returned string, such as the documented VacationRentalReview-style identifier, rather than replacing it with a hotel id or destination geoId.
Can I request availability for specific check-in and check-out dates?
No date parameters are declared for this operation. It accepts only rentalId, so it cannot request an arbitrary stay window. Any dates you display must come from the returned data after its coverage has been verified.
What response structure is documented?
An unverified, incomplete source example shows data grouped by year, abbreviated month and YYYY-MM-DD date keys with boolean values. No successful probe is available to confirm that structure or the complete response envelope.
Does true mean that a rental can definitely be booked?
That interpretation is not established by the supplied evidence. The source example contains boolean date flags, but their exact meaning, currentness and inventory guarantees are unverified. Do not present them as booking confirmation.
How current or complete is the example calendar?
The example contains historical dates and is truncated. It does not establish the returned time horizon, refresh frequency or completeness. Record your own retrieval timestamp for any verified snapshots and avoid promising current inventory.
Can this endpoint reserve the rental or update its calendar?
No. This is a GET lookup with a rentalId input, not a booking or calendar-write operation. It does not expose reservation, pricing or calendar-update controls.