TripAdvisor Reviews Scraper - Bulk Hotels, Restaurants

Pull every review from a list of TripAdvisor hotels, restaurants or attractions in one run. Hand the actor a batch of TripAdvisor location IDs or URLs, and get every individual review as its own clean dataset row - ready for CSV, Excel, sentiment analysis or a dashboard. No subscription, you only pay per review.

---

What this actor does

• Bulk by design - up to 200 locations per run, up to 5000 reviews each.
• IDs or URLs, mixed - paste numeric location_ids or full Hotel_Review / Restaurant_Review / Attraction_Review URLs; IDs are auto-extracted.
• Real filters - language (or all languages), star rating, traveler type (families / couples / solo / business / friends), free-text keyword search, and sort order.
• One flat row per review - rating, title, full text, reviewer, dates, trip type, helpful votes, photos. No nested objects to flatten.
• You only pay for reviews - locations that fail get a single free diagnostic row; the run keeps going.

Input

Field	Type	Required	Description
locations	array	Yes	Up to 200 TripAdvisor location_ids or review-page URLs (mixed).
maxReviewsPerLocation	integer	No	Cap per location (prefill 50; up to 10000).
language	string	No	Review language, or all for every language (default en).
sort	string	No	most_relevant / newest / oldest / highest / lowest.
ratingFilter	array	No	Keep only chosen star ratings (1-5). Empty = all.
travelerType	string	No	families / couples / solo / business / friends.
textSearch	string	No	Keep only reviews containing this text.
stopOnLocationError	boolean	No	Abort the whole run on the first failing location (default off).

Example: { "locations": ["1218720", "https://www.tripadvisor.com/Restaurant_Review-g187147-d12947099-Reviews-Septime-Paris.html"], "maxReviewsPerLocation": 100, "language": "en", "sort": "most_relevant" }

Output

One row per review. Columns: location_id, location_input, review_id, rating, title, text, language, published_date, stay_date, trip_type, reviewer_name, reviewer_location, helpful_votes, photos. Diagnostic rows (a whole location failed) carry error_code + error_message instead. A run-summary OUTPUT record reports locations succeeded/failed, reviews pulled and the estimated cost. Live per-review pricing is shown on this actor's Apify Store page.

Why this actor

• Reviews specialist - built for one job and does it at scale: thousands of reviews across hundreds of places in a single run.
• Export-ready - flat columns render as a real table you can sort, filter and download as CSV/Excel/JSON in one click.
• Honest billing - failed locations are free; you pay only for review rows actually delivered.
• Mix IDs and URLs - no pre-processing; throw in whatever you have.

More TripAdvisor tools

Part of the USP Ultimate TripAdvisor suite - pick the actor that fits the job:

• TripAdvisor Hotels, Restaurants & Cruises Scraper - search a whole destination across 5 verticals (hotels, restaurants, things to do, vacation rentals, cruises).
• TripAdvisor URL Parser - paste any TripAdvisor URLs and get the parsed payload per URL.

Prefer the raw API across all 21 TripAdvisor endpoints with your own key? See the USP Ultimate TripAdvisor API on RapidAPI.

Need help? Enterprise plans? Custom scraping?

I personally support every customer - drop a message on any channel.