# TripAdvisor Restaurants Scraper (`romy/tripadvisor-restaurants-scraper`) Actor

Search TripAdvisor restaurants for a destination and fetch full detail plus genuinely paginated reviews for one or more restaurant ids, with real price/rating/sort filters. No account or API key needed. Derived from romy/tripadvisor-all-in-one-api.

- **URL**: https://apify.com/romy/tripadvisor-restaurants-scraper.md
- **Developed by:** [Romy](https://apify.com/romy) (community)
- **Categories:** Travel
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.34 / 1,000 restaurant result pusheds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What does TripAdvisor Restaurants Scraper do?

**TripAdvisor Restaurants Scraper** takes a destination geoId and/or a list of restaurant ids, and pushes restaurant search results, full restaurant detail, and paginated reviews to the dataset.

It talks directly to the same internal API the official [TripAdvisor](https://www.tripadvisor.com/) Android app uses, reverse-engineered by capturing live traffic from a real device. Unlike many reverse-engineered mobile APIs, TripAdvisor needs **no per-request signature at all** — just a static API key and self-generated device/session ids, confirmed live and standalone-reproducible. No TripAdvisor account, no API key of your own. This is the restaurants slice of [TripAdvisor All-in-One API](https://apify.com/romy/tripadvisor-all-in-one-api), split out as its own focused Actor.

### Why use TripAdvisor Restaurants Scraper?

- **Search or detail, in one Actor** — pass `geoId` for a restaurant list, `restaurantIds` for full detail, or both in the same run
- **Real filters that genuinely work** — price range, minimum rating, sort — confirmed live in the parent Actor
- **Real paginated reviews, not a 20-item cap** — confirmed live end-to-end: page 2 returns 20 genuinely new reviews with zero overlap with page 1, using TripAdvisor's own real (non-trivial) continuation cursor, wrapped so you don't have to reverse-engineer it yourself
- **No account needed** — every call works fully anonymously
- **Use cases:** restaurant discovery for a destination, price/rating monitoring, review analysis, dining research bots

### Input

| Field                   | Type     | Description                                                                                                                                                               |
| ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `geoId`                 | string   | Destination geoId from TripAdvisor search (e.g. `"293916"` for Bangkok). Required unless `restaurantIds` is set. Runs a restaurant list search.                           |
| `priceMin` / `priceMax` | integer  | Only used with `geoId`.                                                                                                                                                   |
| `minRating`             | string   | Only used with `geoId`. Confirmed live values `"1"`-`"5"`.                                                                                                                |
| `sort`                  | string   | Only used with `geoId`. Confirmed live values `BEST_VALUE`, `PRICE_LOW_TO_HIGH`.                                                                                          |
| `maxPages`              | integer  | Only used with `geoId`. Default `10`. See Known Limitations — list pagination beyond page 1 is not confirmed live and this actor caps at 1 page regardless of this value. |
| `maxItems`              | integer  | Only used with `geoId`. Stop once this many restaurants have been pushed. Leave empty to only bound by `maxPages`.                                                        |
| `restaurantIds`         | string\[] | TripAdvisor restaurant content ids (from a `geoId` search, or a TripAdvisor URL/app link). Required unless `geoId` is set. One dataset row per id.                        |
| `includeReviews`        | boolean  | Only used with `restaurantIds`. Paginates and attaches each restaurant's reviews. Default `false`.                                                                        |
| `reviewsMaxItems`       | integer  | Only used when `includeReviews` is `true`. Stop once this many reviews have been collected for a restaurant. Leave empty to fetch all reviews.                            |
| `currency`              | string   | ISO code, default `GBP`. Affects prices in returned data.                                                                                                                 |

At least one of `geoId` / `restaurantIds` is required; both may be set in the same run.

Example (search):

```json
{ "geoId": "293916", "maxItems": 20, "minRating": "4" }
```

Example (detail + reviews):

```json
{ "restaurantIds": ["24191839", "16726460"], "includeReviews": true, "reviewsMaxItems": 50 }
```

### Output

**List search** (`geoId`): one dataset row per restaurant — TripAdvisor's own map-pin object for that restaurant (`saveId.id` is the content id, `primaryInfo.text` the name, `secondaryInfo.text` the cuisine/type, `overlay.text` the rating), confirmed live against Bangkok (geoId `293916`).

**Detail / reviews** (`restaurantIds`): one dataset row per id:

```json
{
    "restaurantId": "24191839",
    "restaurant": { "AppPresentation_queryAppDetailV2": [{ "container": { "navTitle": "Bangkok'78" } }] },
    "reviews": [{ "htmlTitle": { "htmlString": "My lunch" }, "bubbleRating": { "rating": 5 } }]
}
```

`reviews` is omitted entirely when `includeReviews` is `false`.

### Known limitations

- **Restaurant list-search pagination beyond page 1 does not work, confirmed live.** The parent's README already flags `/restaurants` list pagination beyond page 1 as unwrapped; this Actor attempted to genuinely thread a continuation cursor the same way it does for reviews (which does work), but confirmed live against geoId `293916` (Bangkok): the restaurant list response never carries a continuation `updateToken` at all — only a "View all restaurants" deep link with its own separate filter parameter that the parent's `listContent()` has no field for. So this Actor caps the list search at 1 page regardless of the `maxPages` input, and logs a warning explaining why. Reviews pagination (`includeReviews`) is unaffected and works as documented above.
- **List search returns the map's restaurant pins, not a dedicated results array.** TripAdvisor's restaurant list-search response is structured like a mixed overview screen (a few "top restaurant" teaser cards plus an accompanying map). This Actor extracts the map's restaurant pins as the per-page result set — confirmed live to be a complete, homogeneous list of real restaurants (28 for Bangkok on an unfiltered search) with a usable content id, name, cuisine, and rating on each.
- **This Actor only wraps guest-accessible endpoints.** No login flow is implemented or planned.
- This is an unofficial, reverse-engineered integration, not affiliated with or endorsed by Tripadvisor LLC. Behavior may change if TripAdvisor changes its API.

### Pricing

Pay per event: **$0.003** per `restaurant` — charged once for each restaurant returned by search and once for each restaurant id's detail row (Free plan price; lower on paid Apify plans). See the Actor's Pricing tab for current tiered rates.

Found a bug or have a feature request? Use the Issues tab on this Actor's page.

# Actor input Schema

## `geoId` (type: `string`):

Numeric TripAdvisor destination geoId (e.g. "293916" for Bangkok). Required unless restaurantIds is set. Runs a restaurant list search for this destination.

## `priceMin` (type: `integer`):

Only used with geoId.

## `priceMax` (type: `integer`):

Only used with geoId.

## `minRating` (type: `string`):

Only used with geoId.

## `sort` (type: `string`):

Only used with geoId.

## `maxPages` (type: `integer`):

Only used with geoId. See README Known Limitations — list pagination beyond page 1 is not confirmed live and may cap at 1 page regardless of this value.

## `maxItems` (type: `integer`):

Only used with geoId. Stop once this many restaurants have been pushed. Leave empty to only bound by maxPages.

## `restaurantIds` (type: `array`):

TripAdvisor restaurant content ids (from a geoId search, or a TripAdvisor URL/app link). Required unless geoId is set. One dataset row is pushed per id.

## `includeReviews` (type: `boolean`):

Only used with restaurantIds. Paginates and attaches each restaurant's reviews.

## `reviewsMaxItems` (type: `integer`):

Only used when includeReviews is true. Stop once this many reviews have been collected for a restaurant. Leave empty to fetch all reviews.

## `currency` (type: `string`):

ISO currency code, affects prices in returned data.

## Actor input object example

```json
{
  "maxPages": 10,
  "includeReviews": false,
  "currency": "GBP"
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/tripadvisor-restaurants-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("romy/tripadvisor-restaurants-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 '{}' |
apify call romy/tripadvisor-restaurants-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/tripadvisor-restaurants-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/0cETKsijw2lKxsQxX/builds/b8FKC4MOGlx1TQIt1/openapi.json