🧳

Tripadvisor Hotel, Rental & Travel Data APIs

Turn a city name into a Tripadvisor geoId, search dated hotels, then read the photo and amenity collections for one selected hotel. The same project also lists rental-car, vacation-rental, restaurant, flight-input and cruise reference routes, with live validation limited to the hotel flow.

Open the standalone Tripadvisor demo

Your first destination lookup

Replace <API_KEY> with your authorized platform API key from the dashboard. The request URL contains your key; keep it out of shared links, screenshots and logs.

The example calls search-location with query=New York. Read the suggestions directly from data, keep each integer geoId separate from any hotel id, and let the traveler choose when a name is ambiguous. Suggestions can change and no live result is guaranteed.

Base URL https://api.opendata-api.com

curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-location?key=<API_KEY>&query=New+York'
Hotel and travel request basics
  • search-location returns destination suggestions, and each integer geoId identifies a place, not a property. Pass it to hotel search as a string. The id that hotel details expects is a hotel identifier from a hotel search row; verify which field of the selected row carries it, and never send a geoId as id.
  • Use future YYYY-MM-DD checkIn and checkOut dates and keep adults, rooms, childrenAges and currency identical between the search and the details request. childrenAges is an array of ages from 0 to 17, with 0 meaning under one year. Hotel search names its currency input currencyCode while hotel details names it currency. No default is documented for guests or currency; USD is only an example.
  • Hotel search accepts array filters (amenity, brand, class, deals, healthSafety, neighborhood, style, type) and sort, rating, price and distance inputs, but accepted tokens, scales and units are not documented. Inspect the get-hotels-filter metadata first and leave unverified optional values unset. Cabin, sort and order values on flight and car routes lack a documented list too.
  • Rental details, availability, rates and reviews need a complete rentalId, restaurant details need a restaurantsId, cruise details need a shipId and seoName pair, and car searches need a placeId and location type. Bring these from your own earlier results and pass them unchanged. The rental and restaurant location lookups have no recorded response, so check what they return before relying on them.
  • Only destination lookup, dated hotel search and hotel details have recorded successful runs. Hotel filters, coordinate search, rental cars, vacation rentals, restaurants, flights, cruises, currencies and the status check are documented but not live-validated here. Treat their example fields as unverified and test each route with your own inputs.
  • Responses are content and price snapshots from the moment of the request, not reservations, confirmed inventory or guaranteed checkout prices. Photo and amenity lists do not prove availability, completeness or image-use rights, so check display permissions and repeat the request when freshness matters.

Check status before reading travel data

Check the HTTP status separately from the gateway's code/message/data business status: code 200 indicates gateway business success, but HTTP 200 alone does not. Then inspect the payload inside data, because its shape differs by route. Destination suggestions are an array in data, hotel search rows sit in data.data, and hotel details return photos and amenitiesScreen arrays inside a data object. An empty array is a valid no-match or no-content result, not proof that a hotel lacks a facility.

Choose a travel-data workflow
Resolve a destination and search dated hotels

Start with search-location and keep the integer geoId from the chosen suggestion. search-hotels needs that geoId (sent as a string) plus checkIn and checkOut; adults, rooms, childrenAges, currencyCode and pageNumber are optional, and the hotel list sits in data.data rather than data. search-hotels-by-location takes latitude and longitude instead of a geoId, and get-hotels-filter returns filter metadata for a destination and stay. Destination lookup and dated hotel search have recorded successful runs; the coordinate and filter routes do not.

Read photos and amenities for one selected hotel

get-hotel-details needs a hotel id taken from a hotel search result plus checkIn and checkOut in YYYY-MM-DD, and it works best with the same adults, rooms, childrenAges and currency as the search. A recorded run returned photos and amenitiesScreen arrays inside data. Their item fields and completeness are not established, so keep each item as returned and treat an empty or missing array as unknown rather than as proof that a facility is absent.

Search rental cars with the same or a different return

Use search-cars-same-drop-off when the car returns to the pickup place and search-cars-different-drop-off for a one-way trip. Both need a pickUpPlaceId, pickUpLocationType, dates, times and an order value; the one-way route also needs the drop-off placeId and location type, and the airport code applies when the location type is AIRPORT. This project lists no rental-car location lookup, so bring place identifiers you already hold. The time-of-day format and accepted order values are not documented, and neither route has a recorded response.

Look up known vacation-rental records

search-vacation-rental-location resolves a place name, while rental-details, rental-availability, rental-rates and rental-reviews each need a complete rentalId that you already hold. rental-rates also requires startDate, endDate and adults, and rental-reviews accepts an optional page number. None of these routes has a recorded response, so verify the envelope, fee semantics and last-page behavior with your own identifiers.

Find a restaurant and read its details

search-restaurant-location looks up restaurant places and venues by name. get-restaurant-details-v2 and the legacy get-restaurant-details-deprecated both require a restaurantsId from your own restaurant results, and V2 is the better starting point for a new integration. Neither details route has a recorded response, and the effect of currencyCode on the result is unverified.

Prepare airports, filters and multi-city legs

Use search-airport to get airportCode values, then call get-filters with the source and destination codes, a date, itineraryType (ONE_WAY or ROUND_TRIP) and classOfService. search-flights-multi-city takes legs as a JSON array in the query string, plus classOfService and sortOrder. Accepted cabin and sort values are not documented and none of these routes has a recorded response, so fares and availability are not guaranteed.

Browse cruise destinations, lines and ships

get-cruises-location and get-cruises-quick-links take no inputs and list reference records. get-cruises-details needs a shipId and seoName pair from cruise search or quick-link records, sent unchanged. These routes have no recorded response, so treat their documented fields as unverified.

Check currency codes and service status

get-currency lists currency codes and labels for the currency inputs on search routes, and test-api is a simple availability check. Neither takes parameters. Use them for setup and diagnostics, not as proof that a data route will return results.

Car Rentals

GET /api/project/tripadvisor-data/search-cars-different-drop-off

Search car rentals with different pickup and return locations

Full docs β†’
Details

Search for a car rental with separate pickup and drop-off locations. Supply pickUpPlaceId, pickUpLocationType, pickUpDate, pickUpTime, dropOffPlaceId, dropOffLocationType, dropOffDate, dropOffTime, and the required order string. Location IDs and location types come from rental-car location search results; include the corresponding airport code when a location is an AIRPORT. Optional inputs are driverAge, currencyCode, and page, whose documented default is 1. Dates use YYYY-MM-DD. The documentation also labels the time strings YYYY-MM-DD, so a usable time-of-day format is not established by the supplied evidence. No saved live probe covers this operation. A truncated documentation example shows a data.cars array with displayPricing.breakDown fields including basePrice, oneWayFee, payAtPickupPrice, payNowPrice, pricePerDay, totalPrice, and youngDriverFee; pickup and return location objects; fees; a price object; purchaseLink; and supplier address information. These are unverified example fields, not guaranteed live response fields. Fee fields may be null, which must not be treated as proof that a fee is zero. This is a search interface, not a booking or payment action, and it does not establish current availability.

Test this travel endpoint 9 required Β· 5 optional
ParameterInValue
query
query
query
query
query
query
query
query
query
query
query
query
query
Optional guests, filters and paging (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-cars-different-drop-off?key=<API_KEY>&dropOffDate=<dropOffDate>&dropOffLocationType=<dropOffLocationType>&dropOffPlaceId=<dropOffPlaceId>&dropOffTime=<dropOffTime>&order=<order>&page=1&pickUpDate=<pickUpDate>&pickUpLocationType=<pickUpLocationType>&pickUpPlaceId=<pickUpPlaceId>&pickUpTime=<pickUpTime>'
GET /api/project/tripadvisor-data/search-cars-same-drop-off

Search car rentals returned to the pickup location

Full docs β†’
Details

Search for a car rental that returns to the same location as pickup. Supply pickUpPlaceId and pickUpLocationType from rental-car location search results, plus pickUpDate, pickUpTime, dropOffDate, dropOffTime, and the required order string. There are no separate return-place or return-location-type parameters on this operation. Include pickUpAirportCode for an AIRPORT pickup, and optionally driverAge, currencyCode, and page. The documented page default is 1. Dates use YYYY-MM-DD; the documentation repeats that date pattern for the required time strings, so no verified time-of-day format is supplied. No saved live probe covers this operation. Its truncated documentation example shows data.cars with displayPricing.breakDown, fees, pickUpLocation, dropOffLocation, price, purchaseLink, supplier, supplierRating, and tags. The supplier example includes hasShuttle and coordinates; supplierRating includes averageRating, cleanliness, collectTime, condition, dropOffTime, efficiency, locating, and valueForMoney. These are unverified example fields, not a complete or guaranteed live schema. Availability, current prices, rating scales, and bookability are not established by this evidence. The request searches data and does not make a reservation.

Test this travel endpoint 7 required Β· 4 optional
ParameterInValue
query
query
query
query
query
query
query
query
query
query
Optional guests, filters and paging (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-cars-same-drop-off?key=<API_KEY>&dropOffDate=<dropOffDate>&dropOffTime=<dropOffTime>&order=<order>&page=1&pickUpDate=<pickUpDate>&pickUpLocationType=<pickUpLocationType>&pickUpPlaceId=<pickUpPlaceId>&pickUpTime=<pickUpTime>'

Cruises

GET /api/project/tripadvisor-data/get-cruises-details

Get cruise details for a known ship ID and SEO name

Full docs β†’
Details

Retrieve cruise detail data using the required shipId and seoName strings, with optional currencyCode. The documentation identifies cruise search results and cruise quick links as sources of the shipId and seoName values. Preserve the supplied seoName rather than assuming it must be converted into a URL slug; the documented example is MSC Magnifica with shipId 15691635. USD is the documented currency example. No saved live probe covers this operation. The truncated documentation response shows data.itineraries.list: entries contain cruiseLine, destination, id, itinerary.results with day and port objects, length, lowestPricedSailing, portDeparture, sailings, ship, and title. Sailing records show departureDate, id, and priceId, and sailings has totalResults. These are unverified example fields, not a complete or guaranteed live schema. A priceId is a reference rather than a documented monetary amount, and a listed departure is not proof of current availability. The supplied evidence does not establish deck plans, cabin details, reservation actions, or a complete ship-profile response.

Test this travel endpoint 2 required Β· 1 optional
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-cruises-details?key=<API_KEY>&seoName=<seoName>&shipId=<shipId>'
GET /api/project/tripadvisor-data/get-cruises-location

List cruise destination reference locations

Full docs β†’
Details

Request the cruise-location reference list with a GET call and no endpoint-specific parameters. The supplied HTTP 200 source example contains a data array whose items have numeric destinationId and locationId fields and a name string. Its envelope also includes a boolean status, a message string, and a numeric timestamp; the example shows status true and message Success, but does not document the timestamp unit. Labels such as Caribbean and Bahamas illustrate the kind of destination reference returned, not guaranteed coverage. This operation has no saved probe call, so these are source-example fields rather than observed execution results, and field requiredness is unverified. Preserve destinationId and locationId separately; their interchangeability or use with other endpoints is not established. The list does not document sailings, departure ports, coordinates, fares, or booking availability.

Test this travel endpoint 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-cruises-location?key=<API_KEY>'

Flights

GET /api/project/tripadvisor-data/get-filters

Get flight-filter metadata for a route and travel dates

Full docs β†’
Details

Retrieve flight-search filter metadata using required string query parameters classOfService, date, destinationAirportCode, itineraryType, and sourceAirportCode. Departure date uses YYYY-MM-DD. Documented itineraryType values are ONE_WAY and ROUND_TRIP. returnDate is an optional string in YYYY-MM-DD format; the evidence does not establish conditional validation rules for return journeys. Airport codes can be obtained from the airport-search operation; BOM and DEL are documented input examples. No accepted classOfService value list is supplied. The truncated HTTP 200 source example shows data.filters as an array of groups with param, title, and nested filters fields. Categorical entries contain label and value strings; time-range entries contain numeric index, rangeMin, and rangeMax plus title and subTitle strings. Visible groups concern stops, change/cancellation policies, flight times, airlines, alliance, duration, layover airports, and price; some nested filters arrays are empty. These fields come from an incomplete source example, not a saved probe call. The complete envelope, range units, required response fields, and current filter availability remain unverified. Returned param names and values are metadata, not additional declared inputs to this operation or proof of compatibility with another endpoint. This response is not a list of flight itineraries, a fare quote, or a booking result.

Test this travel endpoint 5 required Β· 1 optional
ParameterInValue
query
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-filters?key=<API_KEY>&classOfService=<classOfService>&date=<date>&destinationAirportCode=<destinationAirportCode>&itineraryType=ONE_WAY&sourceAirportCode=<sourceAirportCode>'
GET /api/project/tripadvisor-data/search-airport

Find airport and city suggestions by location name

Full docs β†’
Details

Search airport suggestions with the required query string, documented as the name of the location where an airport is situated; london is the supplied input example. The truncated, unverified source response example shows a data array whose records include airportCode and may contain children for individual airports within a city-level result. Example child records include coords, title, shortName, isChild, and details fields such as name, geo_name, parent_name, and parent_ids. Use these as a guide to parsing and disambiguation, not as a verified response contract: no saved operation-specific probe is available. Inspect the returned record before choosing a code for a flight leg; a city grouping is not necessarily a single airport. This is an airport lookup, not a flight availability or booking request.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-airport?key=<API_KEY>&query=<query>'
GET /api/project/tripadvisor-data/search-flights-multi-city

Search a multi-city flight itinerary with ordered travel legs

Full docs β†’
Details

Search multiple flight legs with required classOfService, sortOrder, and legs query parameters. Each leg uses sourceAirportCode, destinationAirportCode, and date; the documented representation is a JSON array of leg objects, although the declared legs parameter type remains object. The saved example contains historical October 2025 dates and must be replaced for a current trip. currencyCode is optional and is documented as obtainable from Get Currency. Optional pageLoadUid, searchHash, and searchId are documented as values to reuse from a previous call for a complete response; their returned locations and continuation timing are not verified. The truncated, unverified source example shows data.complete and data.flights. Example flight records contain itineraryTag, purchaseLinks with currency, totalPrice, totalPricePerPassenger, and tax fields, plus segments with legs containing departureDateTime, arrivalDateTime, originStationCode, destinationStationCode, and carrier information. No saved operation-specific probe confirms these fields, accepted cabin or sort values, live fares, or booking availability.

Test this travel endpoint 3 required Β· 4 optional
ParameterInValue
query
query
query
query
Optional guests, filters and paging (3)
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-flights-multi-city?key=<API_KEY>&classOfService=<classOfService>&legs=%5B%7B%22sourceAirportCode%22%3A%22BOS%22%2C%22destinationAirportCode%22%3A%22LON%22%2C%22date%22%3A%222025-10-18%22%7D%2C%7B%22sourceAirportCode%22%3A%22LON%22%2C%22destinationAirportCode%22%3A%22BOS%22%2C%22date%22%3A%222025-10-26%22%7D%5D&sortOrder=<sortOrder>'

Reference Data

GET /api/project/tripadvisor-data/get-currency

List currency codes and labels for travel search forms

Full docs β†’
Details

Retrieve currency reference data with a GET request and no declared input parameters. The truncated, unverified source response example shows a data object with majorCurrencies and minorCurrencies arrays; example entries contain code, name, and symbol strings. These are documented sample fields, not operation-specific probe observations, because no saved probe call is available for this endpoint. Use the codes actually returned to populate a travel-form currency selector, retaining the code separately from the display name and symbol. The multi-city flight operation documents this list as a source for its currencyCode input. If another travel operation names its currency input differently, map it explicitly in the client rather than assuming identical parameter names. This endpoint documents currency metadata, not exchange rates, converted totals, or guaranteed currency acceptance by every travel search.

Test this travel endpoint 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-currency?key=<API_KEY>'

Hotels

GET /api/project/tripadvisor-data/get-hotel-details

Get one hotel’s photos and amenity collections

Full docs β†’
Details

Retrieve hotel content for a required hotel id and stay dates checkIn and checkOut in YYYY-MM-DD format. Obtain the hotel identifier through hotel search and verify the selected result identifier before passing it as id. Optional adults, rooms, childrenAges and currency keep the request aligned with the intended party and stay. The documented childrenAges input is an array of ages from 0 to 17, using 0 for a child under one year. A saved successful HTTP 200 probe returned a JSON object with status=true, a message string, an integer timestamp and a data object containing photos and amenitiesScreen arrays. The probe metadata establishes these collections, not their item-level schemas or completeness. A separate, truncated documentation example also shows data.about with title, tags and content, amenitiesScreen sections with title and content, and data.attractionsNearby.content; those additional fields were not confirmed by the supplied probe metadata. Handle empty or absent collections explicitly rather than treating missing content as proof that an amenity is unavailable. This is a content lookup, not a booking confirmation or a guarantee of room inventory, prices, reviews or complete property coverage.

Test this travel endpoint 3 required Β· 4 optional
ParameterInValue
query
query
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-hotel-details?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&id=<id>'
GET /api/project/tripadvisor-data/get-hotels-filter

Get hotel filter metadata for a destination and stay

Full docs β†’
Details

Request hotel-search filter metadata using a required geoId plus checkIn and checkOut dates in YYYY-MM-DD format. Use the geoId returned by the hotel location-search operation and keep it as the required string input here. No probe observation was supplied for this operation. The truncated documentation example shows a data object containing datePicker and a filters array; these are documentation-only fields, not verified probe results. The example datePicker contains configuration fields maxAdultsPerRoom, maxChildrenPerRoom, maxRooms and maxStayLength, as well as lastSelectableDate and timeZoneOffset. Example filter entries include name and title, nested filters, and, on some entries, minValue, maxValue, selectedRangeStart and selectedRangeEnd. Inspect the actual returned structures before exposing controls or mapping values into hotel-search parameters. Do not hard-code a universal list of facets, numeric limits, selectable dates or value encodings from the example. Refresh or invalidate cached choices when the destination or either stay date changes. This endpoint describes search controls; it does not return the hotel result list or confirm that a room can be booked.

Test this travel endpoint 3 required Β· 0 optional
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-hotels-filter?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&geoId=<geoId>'
GET /api/project/tripadvisor-data/search-hotels

Search hotels by destination, dates and optional filters

Full docs β†’
Details

Search for hotels with a required destination geoId and checkIn and checkOut dates in YYYY-MM-DD format. Obtain geoId through hotel location search and supply it as a string. Optional adults, rooms and childrenAges describe the party; currencyCode selects a currency from the currency lookup; pageNumber selects a result page and has a documented default of 1. The contract also accepts sort, priceMin, priceMax, rating, distFrom, distFromMaxDistance and the array filters amenity, brand, class, deals, healthSafety, neighborhood, style and type. The supplied documentation does not define accepted filter tokens, sort values, rating scale or distance units. Inspect applicable filter metadata before mapping controls, and leave unverified optional values unset. A saved successful HTTP 200 probe returned status=true, a message string, an integer timestamp and a data object containing a data array: the observed hotel-list path is data.data, not the outer data object. A separate truncated documentation example shows rows with id, title, bubbleRating, cardPhotos, isSponsored, primaryInfo, secondaryInfo, priceDetails, priceForDisplay, priceSummary and strikethroughPrice; those row fields were not confirmed by the supplied probe metadata and should not be assumed present. Verify a selected row’s hotel identifier before forwarding it to the hotel-details id input. No total-count, page-size, stable ordering, booking, exhaustive inventory or live-price guarantee is established by the supplied evidence.

Test this travel endpoint 3 required Β· 19 optional
ParameterInValue
query
query
query
query
query
query
query
query
Optional guests, filters and paging (14)
ParameterInValue
query
query
query
query
query
query
query
query
query
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-hotels?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&geoId=<geoId>&pageNumber=1'
GET /api/project/tripadvisor-data/search-hotels-by-location

Search hotels around latitude and longitude

Full docs β†’
Details

Search for Tripadvisor hotel listings around a coordinate pair for a specified stay. Required query inputs are latitude and longitude as strings plus checkIn and checkOut in YYYY-MM-DD format. Optional inputs cover adults, rooms, childrenAges, pageNumber, currencyCode, priceMin, priceMax, rating, sort and array-based hotel filters. The documented default pageNumber is 1; accepted filter identifiers, rating semantics, sort keys and distance units are not specified. Use coordinates, not a destination geoId, for latitude and longitude. This operation has no observed probe response in the supplied evidence. Its unverified, truncated source example shows hotel cards in data.data, including string id and title, boolean isSponsored and accentedLabel, bubbleRating with string count and numeric rating, and cardPhotos entries with a sizes object containing maxHeight, maxWidth and urlTemplate. It also shows badge, provider, secondaryInfo and nullable display fields. priceForDisplay, priceDetails, priceSummary, strikethroughPrice and primaryInfo are null in that example. The complete envelope is not established, and neither response compatibility with other hotel-search operations nor live prices, bookable inventory or a defined search radius is guaranteed.

Test this travel endpoint 4 required Β· 19 optional
ParameterInValue
query
query
query
query
query
query
query
query
query
Optional guests, filters and paging (14)
ParameterInValue
query
query
query
query
query
query
query
query
query
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-hotels-by-location?key=<API_KEY>&checkIn=<checkIn>&checkOut=<checkOut>&latitude=<latitude>&longitude=<longitude>&pageNumber=1'
GET /api/project/tripadvisor-data/search-location

Find hotel destinations and their geoId values

Full docs β†’
Details

Resolve a typed hotel destination into Tripadvisor location suggestions using the required string query parameter. Use the returned location information to let a traveler choose a destination, then retain its geoId separately from any individual hotel id. This operation looks up locations; it does not search hotel inventory or return an individual property detail record. An observed successful probe with query=New York returned HTTP 200 and a JSON object with status=true, message as a string, timestamp as an integer and data as an array of location objects. Declared location fields are documentId, secondaryText, title and trackingItems, all strings when present. The observed response additionally included integer geoId values. Read suggestions directly from data, not data.data. The unverified source example shows the declared fields and HTML-style bold markup in title, but does not establish geoId; geoId is supported by the observed probe instead. Treat result labels as display content, handle ambiguous destinations through explicit selection and tolerate missing optional fields. Timestamp units and a maximum result count are not documented.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-location?key=<API_KEY>&query=<query>'

Vacation Rentals

GET /api/project/tripadvisor-data/rental-availability

Look up availability data for a known vacation rental

Full docs β†’
Details

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.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-availability?key=<API_KEY>&rentalId=<rentalId>'
GET /api/project/tripadvisor-data/rental-details

Get vacation rental details by rentalId

Full docs β†’
Details

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.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
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'
GET /api/project/tripadvisor-data/rental-rates

Get rental rates for a dated stay and guest count

Full docs β†’
Details

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.

Test this travel endpoint 4 required Β· 1 optional
ParameterInValue
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
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>'
GET /api/project/tripadvisor-data/rental-reviews

Get a page of reviews for a known vacation rental

Full docs β†’
Details

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.

Test this travel endpoint 1 required Β· 1 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/rental-reviews?key=<API_KEY>&page=1&rentalId=<rentalId>'
GET /api/project/tripadvisor-data/search-vacation-rental-location

Search vacation rental destinations by place name

Full docs β†’
Details

Look up vacation-rental destination suggestions from a typed place name using the required string query parameter. Send a city, region or country name and read the returned location records so a user can choose a place for a rental-focused interface. This operation resolves destinations only: it does not return rental listings, prices, availability or reviews, and it accepts no dates, guest counts or page number. No observed probe response was supplied for this operation, so the response description comes from a truncated source example and is unverified. The example shows a data array of location objects with geoId, locationId, isGeo, localizedName, localizedAdditionalNames, locationV2, placeType, latitude, longitude and a thumbnail.photoSizeDynamic object holding maxHeight, maxWidth and a urlTemplate that contains {width} and {height} placeholders. Example placeType values include CITY, STATE, COUNTRY and MUNICIPALITY, and example entries include New York City, New Orleans, Newport and New Zealand. Envelope fields around data, the maximum result count, ordering and error behavior are not established by the supplied evidence. Inspect the actual response before relying on any field, treat labels as display text, and confirm in the documentation of any other operation that a returned identifier is accepted there before passing it on.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-vacation-rental-location?key=<API_KEY>&query=<query>'

Restaurants

GET /api/project/tripadvisor-data/get-restaurant-details-deprecated

Get restaurant details by restaurantsId (legacy path)

Full docs β†’
Details

Retrieve the detail record for one known Tripadvisor restaurant through the deprecated restaurant-details path. The required restaurantsId string is documented as coming from a restaurant search result, and the optional currencyCode string is documented as coming from the currency reference lookup, with USD as the example. Existing clients can keep this request shape while they plan a move to the V2 details operation; new integrations should start with V2. This lookup returns details for a single restaurant only and does not search for restaurants, list menus or take reservations. No observed probe response was supplied, so the response description comes from a truncated source example and is unverified. The visible part shows a data object with hours and location. The hours object includes allOpenHours (days and times), currentHoursText, hoursTodayText, openStatus, openStatusText and an addHoursLink. The location object includes address, address_obj (street1, street2, city, state, postalcode, country), ancestors, category, cuisine, dietary_restrictions, description, display_hours, a nested hours object with timezone and week_ranges (open_time and close_time), latitude, longitude, location_id, location_string, name, neighborhood_info, num_reviews, awards, open_now_text and a photo object with image renditions. Latitude, longitude, location_id and num_reviews appear as strings. The example is cut off, so remaining fields, error responses and any effect of currencyCode are not established. The visible portion matches the V2 example; differences in schema or status behavior, if any, are not documented, so compare real responses before swapping paths.

Test this travel endpoint 1 required Β· 1 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-restaurant-details-deprecated?key=<API_KEY>'
GET /api/project/tripadvisor-data/get-restaurant-details-v2

Get restaurant details by restaurantsId (V2)

Full docs β†’
Details

Retrieve the detail record for one known Tripadvisor restaurant using the V2 restaurant-details path. The required restaurantsId string is documented as coming from a restaurant search result, and the optional currencyCode string is documented as coming from the currency reference lookup, with USD as the example. Use it to enrich a restaurant you have already identified with address, cuisine, opening-status and photo data. It does not search for restaurants, return menus, provide review text or make reservations. No observed probe response was supplied, so the response description comes from a truncated source example and is unverified. The visible part shows a data object with hours and location. The hours object includes openStatus, openStatusText, currentHoursText, hoursTodayText, allOpenHours (days and times) and an addHoursLink. The location object includes name, description, address, address_obj (street1, street2, city, state, postalcode, country), ancestors, category, cuisine, dietary_restrictions, display_hours, a nested hours object with timezone and week_ranges (open_time and close_time), latitude, longitude, location_id, location_string, neighborhood_info, num_reviews, awards, parent_display_name and a photo object with large, medium, original, small and thumbnail renditions. Latitude, longitude, location_id and num_reviews appear as strings, and several fields are null in the example. The example is cut off, so remaining fields, error responses and any effect of currencyCode are not established. Inspect the actual response before choosing which fields to display or store.

Test this travel endpoint 1 required Β· 1 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/get-restaurant-details-v2?key=<API_KEY>'
GET /api/project/tripadvisor-data/search-restaurant-location

Search restaurant locations and venues by name

Full docs β†’
Details

Look up dining-location suggestions from a typed name using the required string query parameter. Send a city or area name, or part of a venue name, and read the returned location records so a user can pick a place in a restaurant-focused interface. The parameter is documented as the name of the location where the restaurant is situated. This operation returns suggestion records only: it does not return restaurant details, menus, opening hours, reviews or reservations, and it accepts no filter, language or page inputs. No observed probe response was supplied for this operation, so the response description comes from a truncated source example and is unverified. For the query mumbai, the example shows a data array of location objects with documentId, locationId, isGeo, localizedName, placeType, latitude, longitude, localizedAdditionalNames.longOnlyHierarchy, locationV2 (names.longOnlyHierarchyTypeaheadV2, placeType and a vacationRentalsRoute that is either an object with a url or null), streetAddress.street1 and a thumbnail.photoSizeDynamic object holding maxHeight, maxWidth and a urlTemplate with {width} and {height} placeholders. The first example record is the city Mumbai with isGeo true and placeType CITY; the other visible records have isGeo false and placeType EATERY, such as Mumbai Kitchen in Indonesia and Mumbai Masala branches in Spain, so one response can mix place records and individual venue records. The example is cut off, so the full result count, ordering, envelope fields beyond data and error behavior are not established. Treat labels as display text, inspect a real response before relying on any field, and do not assume that locationId or documentId can be passed as restaurantsId to another operation without checking that operation's own input documentation.

Test this travel endpoint 1 required Β· 0 optional
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/search-restaurant-location?key=<API_KEY>&query=<query>'

Service Status

GET /api/project/tripadvisor-data/test-api

Check that the API server is up and running

Full docs β†’
Details

Send a parameter-free GET request to confirm that the Tripadvisor data API server is reachable and answering. The operation is documented as a test that the server is up and running. It takes no query, path, header or body inputs from the caller and returns no travel data: no hotels, restaurants, flights, cruises or rentals. No observed probe response was supplied for this operation, so the response description comes from a source example and is unverified. The example for a 200 response is a small JSON object with two fields, a message string reading Server is up and running and a boolean status set to true. Whether status can be false, what other fields may appear, and how errors or access problems are reported are not established by the supplied evidence. Treat a successful reply as a reachability signal only: it does not show that the hotel, restaurant, flight, cruise or rental operations are fresh, complete or healthy, so test the specific operation your application depends on as well.

Test this travel endpoint 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/tripadvisor-data/test-api?key=<API_KEY>'

Travel data capabilities and verification scope

Query Tripadvisor travel data for destination-to-hotel discovery, dated hotel searches and on-demand hotel photos and amenities, with additional routes for rental cars, vacation rentals, restaurants, flight inputs and cruise reference data.

  • Destination lookup: turn a city or place name into the geoId that hotel search expects
  • Hotel search: dated hotel lists by geoId or by latitude and longitude, with guest, room, price and filter inputs plus filter metadata
  • Hotel details: photo and amenity collections for one selected hotel and stay
  • Car rentals: same-location and one-way pickup and return searches with dates, times and driver age
  • Vacation rentals: location lookup plus details, availability, dated rates and review pages for a known rental ID
  • Restaurants and cruises: restaurant lookup and details by ID, plus cruise destination, quick-link and ship reference data
  • Flight inputs and reference data: airport suggestions, route filter metadata, multi-city itineraries and supported currency codes

Live validation covered location search, hotel search and hotel details only; the other routes are documented but not live-validated. Restaurant, standard flight, vacation-rental and cruise list searches are unavailable. This is an unofficial travel-data API, not a booking, payment or reservation integration. Prices and availability are snapshots, and photo or amenity lists may be incomplete or subject to image-use rights.

Guides