# TripAdvisor Attractions Scraper (`romy/tripadvisor-attractions-scraper`) Actor

Search TripAdvisor attractions and things-to-do for a destination, and fetch full detail plus genuinely paginated reviews for one or more attraction ids. Talks directly to TripAdvisor's internal mobile API; no account or API key needed. Derived from romy/tripadvisor-all-in-one-api.

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

## Pricing

from $2.34 / 1,000 attraction 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 Attractions Scraper do?

**TripAdvisor Attractions Scraper** searches attractions/things-to-do for a destination, and/or fetches full detail plus paginated reviews for specific attraction ids — one dataset row per attraction (search) or per attraction id (detail).

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. No TripAdvisor account, no API key of your own — this is the attractions 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 Attractions Scraper?

- **Search or detail, in one Actor** — give a destination `geoId` for search results, or `attractionIds` for full detail, or both in one run
- **Real paginated reviews, not a fixed 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) pagination cursor, wrapped so you don't have to reverse-engineer it yourself
- **One row per attraction id, sub-calls merged** — detail and (optionally) all requested review pages are fetched and merged into a single dataset row per id
- **No account needed** — every request works fully anonymously
- **Use cases:** things-to-do content aggregation, review analysis, destination research bots, rating monitoring

### Input

| Field             | Type     | Description                                                                                                                                                      |
| ----------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `geoId`           | string   | Destination geo id (e.g. `"293916"` for Bangkok, from the parent API's `/search` endpoint). If set, runs an attraction search for this destination.              |
| `minRating`       | string   | `"1"`-`"5"`. Only applies to the `geoId` search.                                                                                                                 |
| `sort`            | string   | Sort order (see a response's `filters.availableSorts` for values that apply to attractions). Only applies to the `geoId` search.                                 |
| `maxPages`        | integer  | Default `10`. Stop after this many search result pages. **See Known limitations — genuine pagination beyond page 1 is not confirmed to work.**                   |
| `maxItems`        | integer  | Stop once this many attractions have been pushed from the search. Default: unlimited (bounded by `maxPages`).                                                    |
| `attractionIds`   | string\[] | Attraction content ids (from a `geoId` search, or the parent API). For each id, fetches full detail.                                                             |
| `includeReviews`  | boolean  | Default `false`. If true, also paginates and includes reviews for each id in `attractionIds`.                                                                    |
| `reviewsMaxItems` | integer  | Stop once this many reviews have been fetched for a given attraction id. Default: unlimited (all available reviews). Only applies when `includeReviews` is true. |
| `currency`        | string   | ISO code, default `GBP`. Confirmed live to change returned prices where applicable.                                                                              |

At least one of `geoId` or `attractionIds` is required (validated at run time, not by the input schema, so both can be supplied together in one run).

Example — search:

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

Example — detail + reviews:

```json
{ "attractionIds": ["450971", "311043"], "includeReviews": true, "reviewsMaxItems": 40 }
```

### Output

**Search** (`geoId` set) — one row per attraction, e.g.:

```json
{
    "cardTitle": { "string": "Chatuchak Weekend Market" },
    "bubbleRating": { "rating": 4.3, "numberReviews": { "string": "(18,374)" } },
    "cardLink": { "route": { "params": { "contentId": "450971", "contentType": "attraction" } } },
    "...": "full AppPresentation_HorizontalStandardCard fields"
}
```

**Detail / reviews** (`attractionIds` set) — one row per attraction id:

```json
{
    "attractionId": "450971",
    "attraction": { "...": "full QueryHotelAppDetail response" },
    "reviews": [
        {
            "userProfile": { "displayName": "Rwo H" },
            "bubbleRating": { "rating": 5 },
            "htmlTitle": { "htmlString": "Plan Ahead for Chatuchak Weekend Market" },
            "htmlText": { "htmlString": "Chatuchak was the perfect last stop..." },
            "publishedDate": { "string": "4 days ago" },
            "...": "full AppPresentation_UserReviewSection fields"
        }
    ]
}
```

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

### How it connects to the parent

This Actor is a narrow spin-off of [TripAdvisor All-in-One API](https://apify.com/romy/tripadvisor-all-in-one-api) (a Standby REST API covering hotels, restaurants, and attractions), scoped to the attractions/things-to-do vertical only — derived from its `GET /attractions`, `GET /attractions/{id}`, and `GET /attractions/{id}/reviews` endpoints. Unlike the parent, this is a normal batch-run Actor: give it input, get dataset rows out.

### Known limitations

- **Attraction list search only reliably returns page 1.** Confirmed live during this Actor's own testing: the `AppPresentation_queryAppListV2` response for `contentType=attraction` never carries an `updateToken`/continuation cursor at all (unlike the reviews endpoint), and re-requesting without one returns byte-identical items. This matches the parent Actor's README, which flags `update_token` on `/attractions` as exposed but not fully wrapped. This Actor attempts to thread a cursor via `extractUpdateToken()` (the same mechanism that works for reviews) and will page further if a future TripAdvisor response ever includes one that demonstrably advances — but as of this writing it caps at 1 page and logs a warning rather than silently re-fetching the same results.
- **Reviews pagination is genuinely non-trivial, and this Actor handles it for you.** Confirmed live: page 2 returned 20 genuinely new reviews with zero overlap with page 1, using an opaque continuation cursor threaded internally — you don't need to understand TripAdvisor's own token format.
- **This Actor only wraps guest-accessible endpoints.** No login flow is implemented — features requiring a real TripAdvisor account are out of scope by design.
- 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 `attraction` — charged once for each attraction returned by search and once for each attraction 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 id (e.g. "293916" for Bangkok, from the parent TripAdvisor All-in-One API's /search endpoint). If set, runs an attraction search for this destination.

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

Confirmed live filter values "1"-"5". Only applies to the geoId search.

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

Confirmed live values include BEST\_VALUE, PRICE\_LOW\_TO\_HIGH (per the parent API's docs; attraction-relevant sort values may differ — check a response's filters.availableSorts). Only applies to the geoId search.

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

Stop after this many result pages from the geoId search. Note: list pagination beyond page 1 is not confirmed to work by TripAdvisor's API — see README Known Limitations. Each page is typically a handful of attractions.

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

Stop once this many attractions have been pushed from the geoId search. Leave empty to only bound by maxPages.

## `attractionIds` (type: `array`):

TripAdvisor attraction content ids (from a geoId search, or the parent API). For each id, fetches full detail and pushes one dataset row.

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

If true, also paginate and include reviews for each id in attractionIds.

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

Stop once this many reviews have been fetched for a given attraction id. Leave empty to fetch all available reviews. Only applies when includeReviews is true.

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

ISO currency code. Confirmed live to change returned prices where applicable.

## Actor input object example

```json
{
  "geoId": "293916",
  "maxPages": 10,
  "attractionIds": [
    "450971"
  ],
  "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 = {
    "geoId": "293916",
    "attractionIds": [
        "450971"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/tripadvisor-attractions-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 = {
    "geoId": "293916",
    "attractionIds": ["450971"],
}

# Run the Actor and wait for it to finish
run = client.actor("romy/tripadvisor-attractions-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 '{
  "geoId": "293916",
  "attractionIds": [
    "450971"
  ]
}' |
apify call romy/tripadvisor-attractions-scraper --silent --output-dataset

```

## MCP server setup

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