# Tripadvisor Reviews Scraper — Hotels, Restaurants & Attractions (`foxlabs/tripadvisor-reviews-scraper`) Actor

Scrape Tripadvisor reviews for hotels, restaurants, and attractions by URL. Extracts full review text, bubble rating, 6 subratings, stay date, trip type, author profile, management responses, rating breakdown, and AI review summary. No login required.

- **URL**: https://apify.com/foxlabs/tripadvisor-reviews-scraper.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Travel, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 tripadvisor reviews

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

<p align="center">
  <img src="https://img.shields.io/badge/Pay--Per--Event-Reviews_%2B_Place_Summary-00C853?style=for-the-badge" alt="Pay-Per-Event" />&nbsp;
  <img src="https://img.shields.io/badge/Hotels_%C2%B7_Restaurants_%C2%B7_Attractions-48_Structured_Fields-2962FF?style=for-the-badge" alt="48 Structured Fields" />&nbsp;
  <img src="https://img.shields.io/badge/AI_Agent_Ready-MCP_%26_x402-7C4DFF?style=for-the-badge" alt="MCP & x402 Ready" />&nbsp;
  <img src="https://img.shields.io/badge/Dual_Runtime-Batch_%2B_Standby_API-FF6D00?style=for-the-badge" alt="Batch + Standby API" />
</p>

## Tripadvisor Reviews Scraper — Hotels, Restaurants & Attractions 🚀

**foXLabs Hospitality, Reputation & Local Intelligence Series:** [Booking.com Hotels Scraper](https://apify.com/foxlabs/booking-hotels-scraper) · [Airbnb Scraper](https://apify.com/foxlabs/airbnb-scraper) · [Yelp Business Leads Scraper](https://apify.com/foxlabs/yelp-business-scraper) · [Google Maps Leads](https://apify.com/foxlabs/google-maps-scraper) · [Trustpilot Reviews](https://apify.com/foxlabs/trustpilot-reviews-scraper)

🎉 Turn any **Tripadvisor hotel (`Hotel_Review`), restaurant (`Restaurant_Review`) or attraction (`Attraction_Review`) URL** into clean, analytics-ready **48-column guest review & venue datasets** — capturing **full review text, bubble ratings (`1–5`), 6 category subratings, stay dates, trip types, reviewer contribution history, owner/management responses, 1–5 star rating distributions, Tripadvisor AI review summaries, phone numbers, addresses and GPS coordinates** with **zero login and zero cookies**.

Built for hotel & restaurant reputation managers, hospitality VoC (Voice of Customer) analytics teams, multi-location franchise operators, B2B hospitality SaaS lead generation and travel AI agents.

### 🔍 What is the Tripadvisor Reviews Scraper — and when should you use it?

Tripadvisor hosts over a billion traveler reviews across global hotels, restaurants and attractions, making it the richest public source of hospitality guest sentiment, service defect signals and management response benchmarks. However, manual exports are impossible, official content APIs cap you at 3–5 recent snippets per location, and browser-based scrapers burn gigabytes of RAM paginating multi-page venues.

This Actor extracts both **venue-level intelligence (`rowType: "place"`)** and **paginated guest reviews (`rowType: "review"`)** cleanly inside a lightweight `256 MB` container:

- **Unified Coverage + Keyword/City Venue Discovery (`searchQueries`)** — pass `Hotel_Review`, `Restaurant_Review` and `Attraction_Review` URLs in `placeUrls`, OR discover ranked venues automatically via `searchQueries` (`"Rome hotels"`, `"Barcelona restaurants"`, `"Louvre Museum"`) up to `maxPlacesPerQuery`.
- **Complete 38-Field Venue Summary (`includePlaceSummary: true`)** — emits one structured `place` record per venue containing `locationId`, `placeType`, `placeName`, `website`, `email`, `telephone`, `description`, `overallRating`, `totalReviewCount`, full 1–5 star `ratingDistribution`, `placeSubratings`, `rankingString` (`rankingPosition` / `rankingDenominator`), `awards[]`, Tripadvisor's synthesized `aiReviewSummary`, `priceRange`, `cuisines[]`, `dietaryRestrictions[]`, `mealTypes[]`, `amenities[]`, `roomCount`, `openingHours`, `isOpenNow`, `neighborhoods[]`, street/postal address and `latitude`/`longitude`.
- **Deep Traveler & Management Context** — every `review` record includes `reviewId`, `rating`, `title`, full `text`, `language` / `originalLanguage` / `isTranslated`, `isPinnedFavorite`, `stayDate` (`YYYY-MM`), `tripType` (`COUPLES`, `FAMILY`, `BUSINESS`, `SOLO`, `FRIENDS`), `confirmedBooking`, up to 6 category `subratings`, author profile stats, `photoUrls[]` and the full `ownerResponse` object.
- **Precision Date, Language, Sentiment & Response Filtering** — set `lastReviewDate` (`YYYY-MM-DD` cutoff with early pagination stop), filter by `languages` (`["en", "fr"]`), isolate `1–2` star complaints (`maxRating: 2`), or audit management engagement (`withOwnerResponseOnly: true`).

**Use it when you need:** multi-property VoC & defect root-cause analysis; competitor hotel/restaurant benchmarking; hospitality reputation-management B2B prospecting (spotting venues with low `overallRating` or `hasOwnerResponse: false`); or real-time guest sentiment grounding for AI travel assistants.

**Use something else when:** you need **live room rates, check-in availability and tax/discount breakdowns** across an entire city search (use [Booking.com Hotels Scraper](https://apify.com/foxlabs/booking-hotels-scraper) or [Airbnb Scraper](https://apify.com/foxlabs/airbnb-scraper) for live rate & inventory intelligence).

### 🤖 Use with AI agents (MCP, Claude, Cursor & x402)

**Already connected to the Apify MCP server?** Ask your AI assistant to call `foxlabs/tripadvisor-reviews-scraper`.

- **Hosted MCP URL (zero install):** `https://mcp.apify.com?tools=foxlabs/tripadvisor-reviews-scraper`
- **Local stdio config (Claude Desktop, Cursor, Cline, Windsurf):**

```json
{
  "mcpServers": {
    "tripadvisor-reviews-scraper": {
      "command": "npx",
      "args": ["-y", "@apify/actors-mcp-server", "--tools", "foxlabs/tripadvisor-reviews-scraper"],
      "env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }
    }
  }
}
```

**Your agent can pay for its own runs.** This Actor uses transparent pay-per-event pricing (`$0.002` per `review`, `$0.0035` per `place` summary, `$0.00` for diagnostic `status` rows) and supports autonomous micropayments over **x402 (USDC on Base)** or **Skyfire** alongside standard Apify API tokens.

Copy-paste prompt for Claude, ChatGPT, Cursor or any MCP-enabled assistant:

```text
Use the Apify Actor `foxlabs/tripadvisor-reviews-scraper` to extract guest reviews, category subratings, owner responses, rating distributions and AI review summaries from Tripadvisor URLs.

Input fields:
- `placeUrls`: array of Tripadvisor Hotel_Review, Restaurant_Review or Attraction_Review URLs
- `maxReviewsPerPlace`: integer 1..2000 (default 20)
- `includePlaceSummary`: boolean (default true) — emits a `place` summary row with overall rating, 1-5 breakdown, AI review summary, phone & coordinates
- `minRating`: integer 0..5 (default 0 = keep all)
- `maxRating`: integer 1..5 (default 5 = keep all; set 2 for 1-2 star negative reviews)
- `withOwnerResponseOnly`: boolean (default false)

Start with:
{"placeUrls":["https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html"],"maxReviewsPerPlace":25,"includePlaceSummary":true}
```

**Things you can ask your AI agent:**

- *"Scrape the latest 50 reviews of Le Bristol Paris on Tripadvisor and summarize recurring comments on room cleanliness, service speed and breakfast."*
- *"Pull 1-star and 2-star reviews (`maxRating: 2`) across these 5 competitor restaurants in New York and measure what percentage received an `ownerResponse`."*
- *"Compare the `ratingDistribution`, `aiReviewSummary` and `subratings` of three boutique hotels in Rome before booking."*

The machine-readable Actor summary, MCP tool definition and input/output schema live at `https://apify.com/foxlabs/tripadvisor-reviews-scraper.md`.

### 📋 Overview

Everything needed to turn Tripadvisor hotel, restaurant and attraction pages into structured VoC & venue datasets — in one 48-field schema.

| Property | Details |
|---|---|
| **Public data source** | Public Tripadvisor venue & review pages (`tripadvisor.com` and regional Tripadvisor domains) |
| **Supported venue types** | Hotels (`Hotel_Review`), Restaurants (`Restaurant_Review`), Attractions (`Attraction_Review`) |
| **Authentication required** | None — zero Tripadvisor login, API keys or browser cookies |
| **Container footprint** | Lightweight `256 MB` HTTP runtime (fast startup, low compute overhead) |
| **Output row types (`rowType`)** | `review` (`$0.002` / item), `place` (`$0.0035` / venue summary), `status` (`$0.00` diagnostic) |
| **Deduplication & restart safety** | Deterministic `rowKey` (`ta:review:<reviewId>` & `ta:place:<locationId>`) — zero duplicate charges |
| **Execution modes** | Standard Batch Dataset runs + synchronous Standby HTTP API (`GET /`, `GET /health`, `POST /scrape`) |

**Why teams pick this Actor:**

- 🏨 **Hotels, Restaurants & Attractions in one run** — mix any combination of Tripadvisor venue URLs without switching scrapers or schemas.
- 🧠 **Venue AI summary + 1–5 star histogram included** — `place` rows capture Tripadvisor's `aiReviewSummary`, exact `ratingDistribution` (`five`, `four`, `three`, `two`, `one`), `telephone`, `priceRange` and GPS coordinates.
- 💬 **Full management reply tracking** — extracts `hasOwnerResponse` plus the nested `ownerResponse` (`responseId`, `text`, `responderRole`, `language`, `submittedDateTime`) for reputation SLA audits.
- ⭐ **6 granular hospitality subratings** — captures `value`, `rooms`, `location`, `cleanliness`, `service` and `sleep_quality` wherever reviewers scored them, using honest `null` when absent.
- 💸 **All-inclusive PPE pricing** — Apify Proxy protection is baked directly into `$2.00 / 1,000` reviews with zero external proxy setup.

### ✨ Key Features

- 🍽️ **Dynamic Vertical Pagination** — Automatically steps by `10` reviews per page on hotels/attractions (`-or10-`, `-or20-`) and `15` reviews per page on restaurants (`-or15-`, `-or30-`) with strict `reviewId` deduplication.
- 📊 **Rich 48-Column Dataset** — Covers venue contact & coordinates, full review text, translation metadata (`language`, `originalLanguage`, `isTranslated`), `helpfulVotes`, `stayDate`, `tripType`, `confirmedBooking`, reviewer profile metrics and review `photoUrls[]`.
- 🎯 **Targeted Complaint & Advocacy Filters** — Combine `minRating`, `maxRating` and `withOwnerResponseOnly` to extract pure negative defect streams (`1–2` bubbles) or management reply datasets.
- ⚡ **Standby Real-Time Endpoint** — Query `POST /scrape` synchronously from AI agents, Slack/Teams reputation bots, Clay tables or custom dashboards.
- 🛡️ **Null-Safe Output Discipline** — Reviews without category subratings or owner responses emit `subratings: null` and `ownerResponse: null` rather than misleading `0` values.

### 🎬 Quick Start (API & Standby HTTP)

**1. Synchronous Batch API call (returns JSON array directly):**

```bash
curl -X POST "https://api.apify.com/v2/acts/foxlabs~tripadvisor-reviews-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"placeUrls":["https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"],"maxReviewsPerPlace":20,"includePlaceSummary":true}'
```

**2. Real-time Standby HTTP API (`POST /scrape`):**

```bash
curl -X POST "https://foxlabs--tripadvisor-reviews-scraper.apify.actor/scrape?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"placeUrls":["https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html"],"maxReviewsPerPlace":10}'
```

### 🚀 Getting Started (3 steps)

1. **Paste Tripadvisor venue URLs** — Add one or more `Hotel_Review`, `Restaurant_Review` or `Attraction_Review` links in **Place URLs** (`placeUrls`).
2. **Set review depth & rating filters** — Choose `maxReviewsPerPlace` (e.g., `50`), keep `includePlaceSummary: true` for venue metadata, and optionally filter by `minRating`, `maxRating` or `withOwnerResponseOnly`.
3. **Run & export** — Click **Start** and download structured `place` and `review` rows in JSON, CSV, Excel, Parquet or XML.

### 📥 Input & Filters

```json
{
  "placeUrls": [
    "https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html",
    "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
  ],
  "searchQueries": [],
  "maxPlacesPerQuery": 5,
  "maxReviewsPerPlace": 30,
  "includePlaceSummary": true,
  "lastReviewDate": "2026-01-01",
  "languages": ["en"],
  "minRating": 0,
  "maxRating": 5,
  "withOwnerResponseOnly": false
}
```

| Field | Type | Default | Description |
|---|---|---|---|
| `placeUrls` | `array<string>` | 2 sample URLs | List of Tripadvisor `Hotel_Review`, `Restaurant_Review` or `Attraction_Review` URLs to scrape. |
| `searchQueries` | `array<string>` | `[]` | Optional keyword or city+category discovery queries (`"Rome hotels"`, `"Barcelona restaurants"`, `"Louvre Museum"`). |
| `maxPlacesPerQuery` | `integer` | `5` | Maximum Tripadvisor venues discovered per `searchQueries` entry (`1`–`30`). |
| `maxReviewsPerPlace` | `integer` | `20` | Maximum number of published reviews collected per Tripadvisor venue (`1`–`1000`). |
| `includePlaceSummary` | `boolean` | `true` | Emit one `rowType: "place"` venue summary row (website, ranking, hours, cuisines, amenities, awards, AI summary, GPS) per venue. |
| `lastReviewDate` | `string` | `""` | Optional `YYYY-MM-DD` cutoff; skips older reviews and stops pagination once chronological reviews pass this date. |
| `languages` | `array<string>` | `[]` | Optional 2-letter language codes to keep (e.g. `["en", "fr"]`). Leave empty for all. |
| `minRating` | `integer` | `0` | Optional minimum bubble rating filter (`1` to `5`). Leave `0` to keep all ratings. |
| `maxRating` | `integer` | `5` | Optional maximum bubble rating filter (`1` to `5`; set `2` to capture `1–2` star complaints). |
| `withOwnerResponseOnly` | `boolean` | `false` | Keep only reviews where the property owner, general manager or agency posted a response. |
| `proxyConfiguration` | `object` | `{"useApifyProxy": true}` | Managed automatically via Apify Proxy. |

**Copy-paste input recipes:**

- **City-wide hotel & restaurant discovery + reviews (`searchQueries`):**
  `{"placeUrls":[],"searchQueries":["Rome hotels","Barcelona restaurants"],"maxPlacesPerQuery":5,"maxReviewsPerPlace":15,"includePlaceSummary":true}`
- **Negative review & service defect audit since a specific date (`maxRating: 2` + `lastReviewDate`):**
  `{"placeUrls":["https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"],"maxReviewsPerPlace":50,"lastReviewDate":"2026-06-01","minRating":1,"maxRating":2,"includePlaceSummary":true}`
- **Management response tone & SLA benchmark (`withOwnerResponseOnly: true`):**
  `{"placeUrls":["https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html"],"maxReviewsPerPlace":40,"withOwnerResponseOnly":true,"includePlaceSummary":false}`

### 📤 Output Schema & Real Sample Record

Each item carries `rowType` (`"place"`, `"review"` or free diagnostic `"status"`) and a deterministic `rowKey` (`ta:place:<locationId>` or `ta:review:<reviewId>`).

| Field Group | Fields (65 Columns Total) |
|---|---|
| **Venue Summary (`place`)** | `rowType`, `rowKey`, `locationId`, `placeType` (`HOTEL` / `RESTAURANT` / `ATTRACTION`), `placeName`, `url`, `website`, `email`, `telephone`, `description`, `overallRating`, `totalReviewCount`, `publishedLocaleReviewCount`, `ratingDistribution`, `placeSubratings`, `rankingString`, `rankingPosition`, `rankingDenominator`, `awards[]`, `aiReviewSummary`, `priceRange`, `cuisines[]`, `dietaryRestrictions[]`, `mealTypes[]`, `amenities[]`, `roomCount`, `openingHours`, `isOpenNow`, `streetAddress`, `neighborhoods[]`, `city`, `region`, `postalCode`, `country`, `latitude`, `longitude`, `imageUrl`, `searchQuery`, `scrapedAt` |
| **Review Content (`review`)** | `reviewId`, `rating` (`1..5`), `title`, `text`, `language`, `originalLanguage`, `isTranslated`, `isPinnedFavorite`, `helpfulVotes`, `submittedDateTime`, `stayDate` (`YYYY-MM`), `tripType`, `confirmedBooking`, `subratings`, `reviewUrl`, `placeUrl`, `searchQuery` |
| **Reviewer Profile** | `authorUserId`, `authorUsername`, `authorName`, `authorHometown`, `authorContributions`, `authorHelpfulVotes`, `authorProfileUrl` |
| **Owner Reply & Media** | `hasOwnerResponse`, `ownerResponse` (`responseId`, `text`, `responderRole`, `language`, `submittedDateTime`), `photoCount`, `photoUrls[]` |

#### Real sample records (from verified platform pre-publish run `miNyGNbFKcleMfBHj`, 2026-11-14)

```json
[
  {
    "rowType": "place",
    "rowKey": "ta:place:478965",
    "locationId": 478965,
    "placeType": "RESTAURANT",
    "placeName": "Gallaghers Steakhouse",
    "url": "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html",
    "overallRating": 4.4,
    "totalReviewCount": 6281,
    "publishedLocaleReviewCount": 3895,
    "ratingDistribution": {
      "five": 3997,
      "four": 1377,
      "three": 483,
      "two": 227,
      "one": 197
    },
    "aiReviewSummary": "Gallaghers Steakhouse is a hit with many travelers who appreciate its classic New York ambiance, complete with dark wood, historical photos, and red leather booths that create a warm and timeless setting.",
    "priceRange": "$$$$",
    "telephone": "+1 212-586-5000",
    "streetAddress": "228 W 52nd St",
    "city": "New York City",
    "region": "New York",
    "postalCode": "10019-5802",
    "country": "US",
    "latitude": 40.762848,
    "longitude": -73.98386,
    "imageUrl": "https://dynamic-media-cdn.tripadvisor.com/media/photo-o/1b/23/e7/a4/gallaghers-new-york-steakhouse.jpg?w=500&h=-1&s=1",
    "scrapedAt": "2026-11-14T05:07:39.155Z"
  },
  {
    "rowType": "review",
    "rowKey": "ta:review:1084512882",
    "reviewId": 1084512882,
    "locationId": 478965,
    "placeType": "RESTAURANT",
    "placeName": "Gallaghers Steakhouse",
    "rating": 5,
    "title": "Excellent night",
    "text": "Excellent service thank you to the fellow Irish man Nicholas M amazing service.",
    "language": "en",
    "originalLanguage": "en",
    "isTranslated": false,
    "helpfulVotes": 0,
    "submittedDateTime": "2026-11-05T23:32:40.313Z",
    "stayDate": "2026-11",
    "tripType": "COUPLES",
    "confirmedBooking": false,
    "subratings": null,
    "authorUserId": "EC157E15367E13A0C1D342883619B93E",
    "authorUsername": "kestineu",
    "authorName": "Kestine U",
    "authorHometown": null,
    "authorContributions": 1,
    "authorHelpfulVotes": 0,
    "authorProfileUrl": "https://www.tripadvisor.com/Profile/kestineu",
    "hasOwnerResponse": true,
    "ownerResponse": {
      "responseId": 1084943791,
      "text": "Thank you for your review, Kestine. We are delighted to hear that you had an excellent experience, and we will be sure to pass along your praise to Nicholas for providing such amazing service.",
      "responderRole": "Agency / Consultant",
      "language": "en",
      "submittedDateTime": "2026-11-09T18:28:22.318Z"
    },
    "photoCount": 0,
    "photoUrls": [],
    "reviewUrl": "https://www.tripadvisor.com/ShowUserReviews-g60763-d478965-r1084512882-Gallaghers_Steakhouse-New_York_City_New_York.html",
    "placeUrl": "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
  }
]
```

Every run also writes a `SOURCE_REPORT` summary JSON to the default Key-Value Store.

### 🧪 Data Quality — Measured

Verified on the Apify platform across multi-vertical QA runs (`3u6TilkjW4r8FKlaU`, `YJ2dqQ7gUmyMp6A4p`, `Wa4zQDbsZezZ83cih`) and pre-publish live billing verification (`miNyGNbFKcleMfBHj` on 2026-11-14):

- **100% review & venue uniqueness:** Verified across Hotel, Restaurant and Attraction URLs (`58` sampled rows across `3u6TilkjW4r8FKlaU` and `YJ2dqQ7gUmyMp6A4p`, `0` duplicates).
- **100% core field completeness:** `reviewId`, `rating`, `title`, `text`, `submittedDateTime`, `stayDate`, `authorUsername` and `hasOwnerResponse` populated at `100%` on review rows; `overallRating`, `totalReviewCount`, `ratingDistribution`, `aiReviewSummary`, `telephone`, `streetAddress` and GPS coordinates populated at `100%` on sampled hotel/restaurant `place` rows.
- **Verified dual-event PPE accuracy:** Settled `chargedEventCounts` on run `miNyGNbFKcleMfBHj` matched `place` and `review` deliveries `1:1`, with empty-input `status` rows verified at `$0.00`.

### ⏱️ Performance — Measured

Measured on the Apify platform at the default **`256 MB`** memory tier:

- **Low-memory HTTP execution:** Default two-venue run (`40` reviews + `2` place summaries across Paris & New York, run `3u6TilkjW4r8FKlaU`) completed cleanly in `92.8s` inside `256 MB` RAM with zero headless browser overhead.
- **Migration-safe deduplication:** Container restarts automatically hydrate delivered `ta:review:<reviewId>` and `ta:place:<locationId>` keys from the Dataset to prevent duplicate items or repeat charges.

### 💼 Use Cases

1. **Multi-Property Hotel & Restaurant Reputation Monitoring**
   - *Input:* `{"placeUrls":["https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html"],"maxReviewsPerPlace":50,"includePlaceSummary":true}`
   - *Output:* Weekly stream of new guest reviews, `subratings`, `tripType`, `stayDate` and `ownerResponse` timestamps.
   - *Business action:* Alert GMs when `cleanliness` or `service` subratings dip or when negative reviews go unanswered past 48 hours.

2. **Hospitality Reputation Agency Lead Generation**
   - *Input:* Scrape `20` recent reviews + `place` summary across 100 target independent hotels or steakhouses.
   - *Output:* `overallRating`, `ratingDistribution`, `telephone`, `streetAddress` and owner response rate (`hasOwnerResponse`).
   - *Business action:* Pitch reputation management services to high-volume venues (`totalReviewCount > 500`) that never reply to `1–3` star reviews (`hasOwnerResponse: false`).

3. **Competitor Menu & Guest Experience Defect Mining**
   - *Input:* `{"placeUrls":["https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"],"maxReviewsPerPlace":100,"maxRating":3}`
   - *Output:* Filtered `1–3` bubble reviews with `stayDate`, `tripType` and full `text`.
   - *Business action:* Quantify wait-time complaints, pricing pushback or service bottlenecks at rival venues by season.

4. **AI Travel Concierge & Venue Due Diligence (MCP / Standby)**
   - *Input:* Call `POST /scrape` with `maxReviewsPerPlace: 15` and `includePlaceSummary: true`.
   - *Output:* Instant `aiReviewSummary`, `ratingDistribution`, recent `COUPLES` / `FAMILY` reviews and exact coordinates.
   - *Business action:* Answer nuanced traveler questions (*"Is it noisy at night?"*, *"How do recent families rate the rooms?"*) with verified traveler evidence.

### 🔗 Integrations (Node.js, Python, n8n, Make & Clay)

#### JavaScript / Node.js (`apify-client`)

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('foxlabs/tripadvisor-reviews-scraper').call({
    placeUrls: [
        'https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html',
    ],
    maxReviewsPerPlace: 25,
    includePlaceSummary: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Fetched ${items.length} Tripadvisor items`, items[0]);
```

#### Python (`apify-client` v3)

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("foxlabs/tripadvisor-reviews-scraper").call(
    run_input={
        "placeUrls": [
            "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
        ],
        "maxReviewsPerPlace": 25,
        "includePlaceSummary": True,
    }
)

for item in client.dataset(run.default_dataset_id).iterate_items():
    if item["rowType"] == "review":
        print(item["rating"], item["stayDate"], item["title"], "-> reply:", item["hasOwnerResponse"])
```

*(Written for `apify-client` v3 where `call()` returns a `Run` object exposing `run.default_dataset_id`; on `apify-client` v1/v2 use `run["defaultDatasetId"]`.)*

#### n8n, Make, Zapier & Clay

- **Automated VoC Slack/Email alerts (n8n / Make / Zapier):** Schedule daily runs for your portfolio's `placeUrls` with `maxReviewsPerPlace: 15` → filter new `reviewId`s where `rating <= 3` → route to Slack, Zendesk or HubSpot.
- **Clay & AI enrichment:** Hit `https://foxlabs--tripadvisor-reviews-scraper.apify.actor/scrape` synchronously to enrich hospitality prospect domains with Tripadvisor ratings, review counts and owner-reply ratios.

### 📊 Pricing (Pay-Per-Event)

Transparent **Pay-Per-Event (PPE)** pricing — pay per unique review delivered and optional venue summary:

| Event Name | Trigger | Price per Item | Price per 1,000 |
|---|---|---|---|
| `review` | Once per unique Tripadvisor traveler review (`rowType: "review"`) | **$0.002** | **$2.00 / 1,000** |
| `place` | Once per unique venue summary record when `includePlaceSummary: true` (`rowType: "place"`) | **$0.0035** | **$3.50 / 1,000** |
| `status` *(diagnostic)* | Empty input, malformed URL, or zero-match filter note | **$0.00 (Free)** | **$0.00** |

**Worked cost examples:**

- **100 reviews + 1 hotel summary (`includePlaceSummary: true`):** `(100 × $0.002) + (1 × $0.0035)` = **$0.2035**
- **500 reviews across 10 restaurants (`includePlaceSummary: false`):** `500 × $0.002` = **$1.00**
- **1,000 reviews + 20 venue summaries:** `(1,000 × $0.002) + (20 × $0.0035)` = **$2.07**

**Billing guarantees:**

- **Proxy protection included:** Managed Apify Proxy traffic is included inside the per-event price above — zero external proxy charges.
- **Skip `place` charge anytime:** Set `includePlaceSummary: false` if you only want `review` rows (`$0.002` each).
- **Hard spend cap support:** Set **Maximum cost per run** in Apify Console or API options; `ChargingManager` halts delivery cleanly at your budget limit. *(Note: if Apify applies its platform `apify-actor-start` fee on your plan, that start event applies when a run starts, including zero-result runs.)*

### ❓ Frequently Asked Questions (FAQ)

#### Do I need a Tripadvisor account, Content API key, or residential proxies?

No. Tripadvisor's official Content API returns at most 5 recent reviews per location and requires partner approval. This Actor collects full paginated public review histories, owner responses and venue metadata directly on our managed infrastructure with zero login, zero cookies and zero user-supplied proxies.

#### Which types of Tripadvisor URLs are supported in `placeUrls`?

You can pass any public Tripadvisor **Hotel** (`Hotel_Review-g...-d...-Reviews-...`), **Restaurant** (`Restaurant_Review-g...-d...-Reviews-...`) or **Attraction / Thing to Do** (`Attraction_Review-g...-d...-Reviews-...`) URL — including regional Tripadvisor domains (such as `.co.uk`, `.fr`, `.de`, `.es`, `.it`, `.com.tr` or `.ca`). You can mix all three venue types in the same run.

#### Why is `publishedLocaleReviewCount` smaller than `totalReviewCount` on `place` rows?

`totalReviewCount` reflects reviews written across **all global languages** (for example, `6,281` total reviews on Gallaghers Steakhouse), whereas `publishedLocaleReviewCount` (`3,895`) shows how many reviews are published in the language/locale of the Tripadvisor domain URL you supplied (e.g., English on `tripadvisor.com`, French on `tripadvisor.fr`). To collect reviews in another primary language, pass the corresponding regional Tripadvisor URL.

#### How does rating filtering (`minRating`, `maxRating`, `withOwnerResponseOnly`) affect pagination and billing?

Filters are evaluated before Dataset delivery, and you are billed **only** for reviews that match your filter criteria and are written to the Dataset. Note that Tripadvisor paginates reviews chronologically on the page stream; if you filter for rare `1`-star reviews on a `4.8`-star luxury hotel, the Actor scans chronological review pages up to internal page budgets and delivers every matching `1`-star review found.

#### Why is `subratings` populated on some reviews and `null` on others?

Category subratings (`value`, `rooms`, `location`, `cleanliness`, `service`, `sleep_quality`) are optional fields in Tripadvisor's review submission form — and primarily appear on hotel stays rather than quick mobile restaurant reviews. Whenever a reviewer did not score sub-categories, the Actor outputs `subratings: null` rather than fabricating `0` scores.

#### Does the Actor capture Tripadvisor's AI Review Summary?

Yes. When `includePlaceSummary: true` (the default), the `place` row includes `aiReviewSummary` whenever Tripadvisor displays an AI-synthesized traveler consensus on the venue page, alongside the exact `ratingDistribution` (`five`, `four`, `three`, `two`, `one`).

#### How is `ownerResponse` structured when a manager replies to a guest?

Every review includes `hasOwnerResponse` (`true` / `false`). When `true`, `ownerResponse` provides a structured object containing `responseId`, full reply `text`, `responderRole` (such as `"General Manager"`, `"Owner"` or `"Agency / Consultant"`), `language` and `submittedDateTime` ISO timestamp — ideal for measuring management response speed (`ownerResponse.submittedDateTime` minus `submittedDateTime`).

#### Can I disable the `place` summary row if I only want `review` rows in my CSV?

Yes. Set `"includePlaceSummary": false` in your input configuration. Every emitted item will then be a uniform `rowType: "review"` record billed strictly at `$0.002` per review (with zero `$0.0035` `place` summary charge), giving you a flat single-entity table ready for direct CSV, Excel, Snowflake or BigQuery ingestion.

#### What happens if one URL in a 20-URL batch is broken or isn't a venue page?

Invalid or non-venue URLs (for example, a city overview page without a `-d<locationId>-` identifier) emit a free diagnostic `rowType: "status"` row identifying the bad URL and error reason, while all valid `Hotel_Review`, `Restaurant_Review` and `Attraction_Review` URLs in the same batch complete normally.

#### Can I call this Actor synchronously from an AI agent or webhook?

Yes. Connect via `https://mcp.apify.com?tools=foxlabs/tripadvisor-reviews-scraper` for MCP tool calling, use the `run-sync-get-dataset-items` REST endpoint, or send a `POST /scrape` request to the Actor's Standby HTTP URL (`https://foxlabs--tripadvisor-reviews-scraper.apify.actor/scrape`).

#### How does deduplication work if a run migrates mid-pagination?

Every venue summary is keyed by `ta:place:<locationId>` and every review is keyed by `ta:review:<reviewId>`. On startup or container migration, the Actor reads existing `rowKey` values from the run's Dataset and skips already-delivered items so nothing is duplicated or double-charged.

#### How can I combine Tripadvisor review intelligence with live hotel room prices?

Pair this Actor with [Booking.com Hotels Scraper](https://apify.com/foxlabs/booking-hotels-scraper) (for live OTA nightly rates, taxes, room deals and cancellation windows) or [Yelp Business Leads Scraper](https://apify.com/foxlabs/yelp-business-scraper) (for external restaurant websites, business emails and social media profiles).

### 🐛 Troubleshooting

- **Dataset contains only a `rowType: "status"` row with `"EMPTY_INPUT"`:** `placeUrls` was empty. Provide at least one Tripadvisor `Hotel_Review`, `Restaurant_Review` or `Attraction_Review` URL.
- **`UNSUPPORTED_URL` status row:** You pasted a city directory URL (`Tourism-g...` or `Restaurants-g...`) instead of an individual venue URL containing `-d<digits>-`. Open the specific hotel, restaurant or attraction page and copy its URL.
- **Fewer reviews returned than `totalReviewCount`:** Check `publishedLocaleReviewCount` on the `place` row (Tripadvisor partitions reviews by domain locale) and verify whether `minRating`, `maxRating` or `withOwnerResponseOnly` filtered out non-matching reviews.
- **`ownerResponse` or `subratings` is `null`:** That specific review has no management reply or optional category sub-scores on Tripadvisor.

### 🚧 What It Does Not Do

- Does **not** scrape live OTA room prices or booking calendars (use [Booking.com Hotels Scraper](https://apify.com/foxlabs/booking-hotels-scraper) or [Airbnb Scraper](https://apify.com/foxlabs/airbnb-scraper)).
- Does **not** log into private Tripadvisor Management Center accounts or post replies.

### ⚠️ Trademark Notice

This Actor is an independent data-extraction tool built by **foXLabs** and is not affiliated with, endorsed by, or sponsored by Tripadvisor LLC. "Tripadvisor" is a registered trademark of Tripadvisor LLC, referenced solely to describe compatibility with publicly accessible web pages.

### ⚖️ Is It Legal to Scrape Public Tripadvisor Reviews?

This Actor accesses only publicly published venue summaries, traveler reviews and management responses visible to unauthenticated web visitors — without logging into accounts or collecting private user data. Review authors' public display names/usernames appear on public reviews; if your analytics reside under GDPR/UK GDPR or CCPA, assess your lawful basis and consider dropping `author*` columns if you only need aggregate VoC metrics.

### 🤝 Support, Custom Data & Contact

- 🌐 **Website & full portfolio:** [data.foxlabs.com.tr](https://data.foxlabs.com.tr)
- 📧 **Custom data & enterprise inquiries:** info@foxlabs.com.tr
- 🐛 **Bug reports & feature requests:** open an issue in the Actor's **Issues** tab on Apify Store (include your Run ID)
- 🧰 **Browse all foXLabs Actors:** [apify.com/foxlabs](https://apify.com/foxlabs)

### Changelog

#### 0.1.3 (2026-11-14)

- Added `searchQueries`, `maxPlacesPerQuery`, `lastReviewDate` (`YYYY-MM-DD`) and `languages` filter options and expanded the dataset from 48 to 65 columns (`website`, `email`, `description`, `neighborhoods[]`, `rankingString`, `rankingPosition`, `rankingDenominator`, `awards[]`, `placeSubratings`, `cuisines[]`, `dietaryRestrictions[]`, `mealTypes[]`, `amenities[]`, `roomCount`, `openingHours`, `isOpenNow`, `isPinnedFavorite`, `searchQuery`) with zero PPE price increase.

#### 0.1.2 (2026-11-14)

- Upgraded Store README to full SIÁN standard with MCP & x402 AI agent integration, Standby HTTP `POST /scrape` examples, real platform dataset samples (`place` + `review`), worked PPE cost tables, and expanded 12-question FAQ.

#### 0.1.0 (2026-11-13)

- Initial release of `foxlabs/tripadvisor-reviews-scraper` supporting `Hotel_Review`, `Restaurant_Review` and `Attraction_Review` URLs, 6 subratings, owner responses, rating distributions, AI review summaries, and Batch + Standby HTTP modes.

# Changelog

This Actor's version history is a separate document: https://apify.com/foxlabs/tripadvisor-reviews-scraper/changelog.md

# Actor input Schema

## `placeUrls` (type: `array`):

List of Tripadvisor Hotel_Review, Restaurant_Review, or Attraction_Review URLs to scrape.

## `searchQueries` (type: `array`):

Discover Tripadvisor venues by keyword or city+category (e.g. 'Rome hotels', 'Barcelona restaurants', 'Louvre Museum'). Set placeUrls to \[] when running searchQueries only.

## `maxPlacesPerQuery` (type: `integer`):

Maximum number of Tripadvisor venues discovered per searchQueries entry (1–30).

## `maxReviewsPerPlace` (type: `integer`):

Maximum number of published reviews to collect per Tripadvisor venue.

## `includePlaceSummary` (type: `boolean`):

Emit a structured place summary record (overall rating, 1–5 star breakdown, AI review summary, website, ranking, hours, cuisines, amenities, awards, address, phone, coordinates) alongside individual reviews.

## `lastReviewDate` (type: `string`):

Optional ISO date cutoff (e.g. '2026-06-01'). Skips older reviews and stops pagination once chronological reviews pass this date.

## `languages` (type: `array`):

Optional 2-letter language codes to keep (e.g. \['en', 'fr', 'es']). Leave empty for all languages.

## `minRating` (type: `integer`):

Optional minimum bubble rating filter (1 to 5). Set 0 to keep all ratings.

## `maxRating` (type: `integer`):

Optional maximum bubble rating filter (e.g. set 2 to collect only 1-star and 2-star negative reviews). Set 5 for all.

## `withOwnerResponseOnly` (type: `boolean`):

When enabled, keeps only reviews where the property owner or manager posted a reply.

## `proxyConfiguration` (type: `object`):

Apify Proxy settings. Automatically uses Apify Unblocker when left on default.

## Actor input object example

```json
{
  "placeUrls": [
    "https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html",
    "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
  ],
  "searchQueries": [],
  "maxPlacesPerQuery": 5,
  "maxReviewsPerPlace": 20,
  "includePlaceSummary": true,
  "lastReviewDate": "",
  "languages": [],
  "minRating": 0,
  "maxRating": 5,
  "withOwnerResponseOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `sourceReport` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "placeUrls": [
        "https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html",
        "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
    ],
    "maxReviewsPerPlace": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/tripadvisor-reviews-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "placeUrls": [
        "https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html",
        "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html",
    ],
    "maxReviewsPerPlace": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("foxlabs/tripadvisor-reviews-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "placeUrls": [
    "https://www.tripadvisor.com/Hotel_Review-g187147-d188729-Reviews-Le_Bristol_Paris_Oetker_Hotels-Paris_Ile_de_France.html",
    "https://www.tripadvisor.com/Restaurant_Review-g60763-d478965-Reviews-Gallaghers_Steakhouse-New_York_City_New_York.html"
  ],
  "maxReviewsPerPlace": 20
}' |
apify call foxlabs/tripadvisor-reviews-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,foxlabs/tripadvisor-reviews-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/RnnRf2cSseMgWsJ8S/builds/gAHPRxmtugTbUjFCo/openapi.json
