Tripadvisor Review Scraper

What does TripAdvisor Review Scraper do?

TripAdvisor Review Scraper extracts guest reviews from TripAdvisor hotel pages - anonymously, no login, no TripAdvisor account. Give it a hotel name, a city, a full TripAdvisor hotel URL, or a numeric hotel ID, and it returns full review text, rating, sub-ratings, reviewer info, dates, and management responses.

Why use this Actor?

• Reputation monitoring - pull a hotel's latest reviews on a schedule and track sentiment/rating trends over time.
• Competitive research - batch several competing hotels (hotelQueries) and compare review volume, rating, and guest sentiment in one dataset.
• Voice-of-guest analysis - full review text plus per-category sub-ratings (cleanliness, service, location...) feed straight into text analysis without extra parsing.

How to use it

1. Set hotelQuery (a hotel name, a city name, a full TripAdvisor hotel URL, or a bare numeric hotel ID) or hotelQueries for a batch.
2. Set maxItems to cap the number of review rows per hotel (defaults to 20).
3. Click Start.

hotelQueries wins over hotelQuery when filled; duplicates and blanks are dropped automatically.

Input

Field	Type	Description
hotelQuery	string	A hotel name, a city name (see below for the supported city list), a full TripAdvisor hotel URL, or a bare numeric hotel ID. Defaults to a demo hotel if left blank.
hotelQueries	array	Many hotel names, city names, URLs, or hotel IDs in one run. Wins over hotelQuery when filled.
maxItems	integer	Caps the number of review rows returned per hotel. Default 20. The first 10 review rows in a run are always free.
proxyConfiguration	object	A residential proxy is required - TripAdvisor is protected by DataDome and blocks datacenter IPs outright.

Resolving a hotel: URL/ID vs. free text

A full Hotel_Review-g<geoId>-d<hotelId>-... URL (with or without the https://www.tripadvisor.com prefix) resolves directly, as does a bare numeric hotel ID (the "d" number). Free text is matched against a curated table of major city names (Amsterdam, Bangkok, Barcelona, Berlin, Boston, Chicago, Dubai, Hong Kong, Istanbul, Las Vegas, London, Los Angeles, Miami, New York/New York City, Orlando, Paris, Rome, San Francisco, Seoul, Singapore, Sydney, Tokyo, Toronto, Washington DC) - the city name is stripped out of your query text and whatever's left is matched against hotel names in that city's listing page. For best results with an obscure/ambiguous hotel name, pass a direct TripAdvisor Hotel_Review URL or numeric hotel ID instead.

Output

One row per review, with a hotel-context row (status: "error" or "no_reviews") if a hotel can't be resolved or has no reviews.

Review row:

{
    "status": "success",
    "hotelQuery": "The Bryant Park Hotel, New York City",
    "geoId": "60763",
    "hotelId": "224214",
    "hotelName": "The Bryant Park Hotel",
    "hotelUrl": "https://www.tripadvisor.com/Hotel_Review-g60763-d224214-Reviews-The_Bryant_Park_Hotel-New_York_City_New_York.html",
    "totalReviewCount": 5077,
    "reviewId": "1012345678",
    "reviewerName": "Jane D",
    "reviewerUsername": "janed123",
    "rating": 5,
    "subratings": { "Service": 5, "Cleanliness": 5, "Location": 5 },
    "title": "Wonderful stay in Midtown",
    "reviewText": "The staff were incredibly helpful and the room was spotless...",
    "language": "en",
    "createdDate": "2026-08-01",
    "publishedDate": "2026-08-03",
    "mgmtResponseText": null
}

How it works

TripAdvisor embeds a large hydration payload - offers, reviews, and more - as a URL-percent-encoded, backslash-escaped JSON blob inside a <script src="data:text/javascript,..."> tag on every hotel review page. This Actor reads that embedded JSON directly (the ReviewsProxy_getReviewListPageForLocation GraphQL result) instead of scraping visible text, then follows TripAdvisor's own review pagination (an -orN- URL offset segment, 10 reviews per page) up to maxItems, 5 pages, or the hotel's own total review count - whichever comes first. Since TripAdvisor is protected by DataDome, requests run through Camoufox (a fingerprint-patched Firefox), with a warmed browser context reused across a run's requests and a fresh proxy exit IP retried on a blocked/failed fetch.

Limitations

• Only a curated list of major cities resolves free-text city names (see Resolving a hotel) - for a city not in that list, pass a direct hotel URL or numeric ID instead.
• Up to 50 reviews per hotel per run (5 pages x 10 reviews) - re-run with pagination offset built into a later version if you need a hotel's full review history beyond that.
• Review order and content reflect TripAdvisor's own review platform at fetch time.
• No customer-review filtering (e.g. by language or traveler type) is exposed as an input in this version.

Pricing

This Actor uses pay-per-event pricing - one small run-start charge, then a per-row charge for each review. See the Pricing tab for current rates. The first 10 review rows in a run are always free. Failed/no-review hotel lookups land as status: "error"/"no_reviews" rows and are never charged.

FAQ

Do I need a TripAdvisor account or API key? No - it runs entirely against TripAdvisor's public, logged-out hydration data.

Why did I get a status: "no_reviews" row? The hotel was resolved successfully but TripAdvisor's own hydration payload didn't include any review data for it at fetch time.

Why did I get a status: "error" row? Either the free-text query couldn't be resolved to a known city/hotel (see Resolving a hotel), or TripAdvisor's DataDome protection blocked the fetch after retries - try again, or pass a direct hotel URL/ID.

Disclaimer

This Actor is an independent tool, not affiliated with or endorsed by TripAdvisor. It only accesses data TripAdvisor serves publicly to anonymous visitors. Use it in compliance with TripAdvisor's terms of use and applicable law in your jurisdiction. Found a bug or have a feature request? Use the Issues tab on this Actor's page.