Get rental rates for a dated stay and guest count
View all Tripadvisor Hotel, Rental & Travel Data endpoints →Request rate information for a known vacation rental with required rentalId, adults, startDate and endDate query parameters. adults is the numeric guest-count input; startDate is check-in and endDate is checkout, both formatted YYYY-MM-DD. Optional currencyCode selects a documented currency code, with USD supplied as an example rather than an asserted server default. No observed probe response was supplied for this operation. The unverified source example has top-level data, message, status and timestamp fields. data contains rapData, rapRate, view, errors and validationError. Example rapData fields include baseRate, bookingFee, ownerFees, deposit, subtotal and tax, with companion currency fields and several formatted rate values. Example rapRate fields include amount, currency, details, minStay, instantBook and paymentSchedule. Each details item includes amount, currency, optional, refundable, ruleDescription, ruleType, type and typeName; paymentSchedule items include amount, currency and dueDate. The example view includes adults, guests, stayLength, checkInDate, checkOutDate and stay or availability blocking indicators. Some example fields are null. Treat these as source-example fields, not a verified response contract: inspect fee, tax, currency and amount semantics before displaying totals. This is a rate lookup, not a reservation or a guarantee of current availability or a bookable price.
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-rates API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-rates?key=<API_KEY>&adults=<adults>&endDate=<endDate>&rentalId=<rentalId>&startDate=<startDate>'
Query Result
Use Cases
- Compare two stay windows for the same rentalId while holding adults and currencyCode constant, checking returned fee and tax semantics before comparing totals.
- Build a stay-length sensitivity notebook that stores the property ID, dates, adults and requested currency alongside each rate response.
- Prepare an itemized rental-budget worksheet from returned rate components, clearly separating optional or refundable items when those flags are available.
- Create a review screen for minimum-stay indicators and payment-schedule entries before a traveler proceeds to an independent booking process.
Frequently asked questions
Which inputs are required for a rental-rate request?
Provide the complete rentalId, the numeric adults value, startDate and endDate. startDate is check-in and endDate is checkout; both dates use YYYY-MM-DD. currencyCode is optional.
Does adults include a separate child-count setting?
adults is the exposed numeric input described as the number of guests. This operation has no separate children parameter. Although the source example contains additional guest-related response fields, those fields do not establish another supported request input or a child-pricing rule.
Is USD the default currency when currencyCode is omitted?
USD is the documented example. The supplied parameter facts do not specify a server default. The documentation points to the currency-configuration lookup for currency codes; inspect returned currency fields rather than assuming that omitting currencyCode always yields USD.
Can I treat rapRate.amount as the nightly price or add every fee field together?
Not safely from the supplied evidence alone. The source example includes rapRate.amount and currency, rapRate.details, and rapData baseRate, subtotal, tax and fee fields, but their arithmetic and period semantics have not been verified. Check actual response meanings and avoid double-counting formatted or overlapping amounts.
Are the returned rates guaranteed to be available for booking?
No. This endpoint retrieves rate information and does not create a reservation. The source example includes minimum-stay, payment-schedule and blocking fields, but no observed rental-rates probe was supplied. A source example does not establish live inventory, a guaranteed final total or a bookable offer.