TripAdvisor Hotel, Restaurant & Attraction Finder avatar

TripAdvisor Hotel, Restaurant & Attraction Finder

Pricing

from $0.49 / 1,000 results

Go to Apify Store
TripAdvisor Hotel, Restaurant & Attraction Finder

TripAdvisor Hotel, Restaurant & Attraction Finder

Search TripAdvisor by phrase or place URL for hotels, restaurants, and attractions, with rating, ranking, address, contact details, and pricing per place.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

Nimbryxo-studio

Nimbryxo-studio

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Look up hotels, restaurants, and attractions on TripAdvisor by search phrase or by pasting the place's own TripAdvisor URL. Each result comes back as a structured record with rating, ranking, address, contact details, pricing, and category-specific fields like hotel class or cuisine type.

What this actor does

  • Turns a search phrase such as hotels in Paris into a destination (here, Paris) and collects the places TripAdvisor lists for it
  • Scrapes specific places directly from their TripAdvisor URL instead of searching
  • Mixes search queries and direct URLs in the same run, returning each place only once
  • Uses placeType to pick hotels, restaurants, attractions, or a mixed destination overview for searches
  • Pulls category-specific detail when the source has it: hotel star class for hotels, cuisine types for restaurants
  • Fields TripAdvisor has no value for come back as an empty string rather than being dropped, so every record keeps the same set of columns

Output per place

All values are text, including numbers and flags (for example "4.5" or "False").

  • locationId — TripAdvisor's internal ID for the place
  • name, type, subcategory — place name, TripAdvisor's type key for it (e.g. hotel, restaurant, attraction), and sub-category label
  • address, street, city, state, country, postalCode — address, both as one string and broken out by component
  • latitude, longitude — geographic coordinates
  • rating, numberOfReviews — overall rating (0–5) and total review count
  • rankingPosition, rankingString — numeric rank and the full ranking text, e.g. #20 of 583 hotels in New York City
  • priceLevel, priceRange — price symbols (e.g. $$$$) and the price range text
  • phone, email, website — contact details, when published
  • hotelClass — star rating, hotels only
  • cuisine — cuisine types, restaurants only
  • hours — operating hours, when published
  • description — the place's description text
  • neighborhoods — neighborhood name(s) the place is located in
  • webUrl — the TripAdvisor page URL for the place
  • isClosed — "True" or "False", whether TripAdvisor marks the place as closed
  • photoUrl — main photo URL, when available
  • searchQuery — the search phrase that returned this place (empty string for places from startUrls)
  • scrapeTimestamp — when the run started (the same value on every record of a run)

Input

FieldTypeDefaultDescription
searchQueriesarray of strings–Search phrases naming a destination, e.g. hotels in Paris. Words such as "hotels", "best" or "in" are stripped to find the destination; the kind of place returned is set by placeType.
startUrlsarray of strings–Direct TripAdvisor place URLs (hotel, restaurant, or attraction review pages).
maxItemsinteger50Maximum places to return per search query (1–100).
placeTypestringallWhich TripAdvisor list to read for each search destination: hotel, restaurant, attraction, or all (the destination's overview page, which mixes hotels, restaurants, attractions and sometimes vacation rentals). Has no effect on startUrls.
proxyConfigurationobject–Proxy settings for search queries; if left unset, the actor provisions a residential proxy automatically. Direct URLs don't need one.

At least one of searchQueries or startUrls must be provided.

Example: scrape specific places by URL

{
"startUrls": [
"https://www.tripadvisor.com/Hotel_Review-g60763-d675616-Reviews-The_Plaza_New_York-New_York_City_New_York.html",
"https://www.tripadvisor.com/Restaurant_Review-g60763-d457808-Reviews-Daniel-New_York_City_New_York.html"
]
}

Example: search for hotels in a city

{
"searchQueries": ["hotels in Paris"],
"maxItems": 10,
"placeType": "hotel",
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Example: combine a search with a specific attraction URL

{
"searchQueries": ["best restaurants London"],
"startUrls": ["https://www.tripadvisor.com/Attraction_Review-g60763-d104365-Reviews-Empire_State_Building-New_York_City_New_York.html"],
"maxItems": 15,
"placeType": "restaurant",
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": ["RESIDENTIAL"]
}
}

Use cases

  • Travel planning — pull a shortlist of top-ranked hotels or restaurants for a destination into your own itinerary tool
  • Competitive benchmarking for hospitality — compare your property's rating and ranking against nearby competitors
  • Local business directories — populate a city guide with contact details and ratings for attractions and restaurants
  • Market research — track how many hotels or restaurants a city has at each price level
  • Lead generation — collect contact details for restaurants or attractions in a region for outreach

FAQ

Do I need a TripAdvisor account or API key? No. The actor reads TripAdvisor's publicly available place data; no login or API key is required.

Do I need a proxy? Direct URLs (startUrls) work without one. For searchQueries, the actor automatically provisions a residential proxy if you don't supply your own, since TripAdvisor's search pages run into anti-bot protection more often than direct place pages.

Why are some fields empty strings instead of missing? TripAdvisor doesn't publish every field for every place — a restaurant won't have hotelClass, and a hotel won't have cuisine. Rather than remove the field, the actor keeps it as an empty string so every record has the same columns.

How many results come back per search query? Up to maxItems per query (100 at most). The actor reads only the first page of TripAdvisor's list for the destination, so a query usually yields a few dozen places at most, and places already returned for an earlier query or URL are not repeated. Places whose details can't be loaded are skipped.

Why does best restaurants London return hotels too? The search phrase only identifies the destination. With placeType left at all, the actor reads London's overview page, which mixes place types. Set placeType to restaurant to get only restaurants.

What's the difference between rankingPosition and rankingString? rankingPosition is just the number (e.g. 20); rankingString is TripAdvisor's full ranking sentence (e.g. #20 of 583 hotels in New York City).

Can I filter search results to only one place type? Yes, set placeType to hotel, restaurant, or attraction. It only applies to searchQueries, not to places added via startUrls. If TripAdvisor's list page for the destination can't be read, the actor falls back to TripAdvisor's search suggestions, which return fewer places.

Is this affiliated with TripAdvisor? No. This is an independent, third-party actor that reads TripAdvisor's publicly available place data; it is not affiliated with or endorsed by TripAdvisor.