# Viator Tours, Activities & Review Extractor (`vexaloom-labs/viator-tours-activities-and-review-extractor`) Actor

Browse Viator tours and activities by destination or category, look up specific experience listings, and collect traveler reviews, with price, rating and duration filters.

- **URL**: https://apify.com/vexaloom-labs/viator-tours-activities-and-review-extractor.md
- **Developed by:** [vexaloom-labs](https://apify.com/vexaloom-labs) (community)
- **Categories:** Travel, Automation, 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 $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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?

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

## Viator Tours, Activities & Review Extractor

Viator is a large marketplace for bookable tours, activities, day trips and travel experiences. This actor reads Viator's public pages without an account, cookie or API key, and returns clean JSON for keyword searches, destination and category browsing, individual experience details, and traveler reviews.

### Modes

| Mode | What it collects |
| --- | --- |
| `search` | Experiences matching a keyword query, e.g. `Eiffel Tower tour`, `pasta making class`, `Seine cruise`. |
| `byDestination` | Experiences from a destination's things-to-do listing, e.g. Paris, Rome, New York City. |
| `byCategory` | Experiences in an activity category, optionally scoped to a destination. |
| `getExperience` | Full details for experience URLs you already have. |
| `getReviews` | Traveler reviews for experience URLs, or the review shelf on a destination URL. |

### Filters and ordering

- `minPrice` / `maxPrice` – from-price bounds.
- `minRating` – average traveler rating floor (0–5).
- `minDurationHours` / `maxDurationHours` – shortest listed duration bounds.
- `minReviewCount` – minimum number of traveler reviews.
- `sortBy` – Viator order, price low/high, highest rated, or most reviewed.
- `maxItems` – cap on experience records.
- `maxReviewsPerExperience` – cap on reviews returned for each experience URL.

Filters are applied before the cap, so `maxItems` counts matching records rather than raw listing rows. When `sortBy` is not the default, sorting is applied to the scanned listing window before the cap.

### Pagination

- Search results follow Viator's `/searchResults/all/{page}` paging (Viator exposes up to 200 results per query).
- Destination and category listings follow Viator's listing pages, 24 experiences per page, until `maxItems` matching records are collected.
- Reviews are paged through Viator's public review query in batches of 30 until `maxReviewsPerExperience` is reached.
- Duplicate products and reviews are removed by Viator's product code and review id.

### Output per experience (search, byDestination, byCategory, getExperience)

| Field | Description |
| --- | --- |
| `recordType` | `experience`. |
| `scrapedAt` | ISO timestamp of capture. |
| `productCode` | Viator product code. |
| `url` | Canonical Viator experience URL. |
| `title` | Experience title. |
| `description` | Overview text from the listing or detail page. |
| `highlights` | Bullet highlights from a detail page. |
| `images` | Supplier/listing photo URLs. |
| `price` | Current from-price. |
| `priceOriginal` | Pre-discount from-price when Viator shows one. |
| `currency` | Currency code (USD by default). |
| `isOnSale` | Present when a discount is active. |
| `rating` | Average traveler rating (0–5). |
| `reviewCount` | Number of traveler reviews behind the rating. |
| `durationHours` | Shortest listed duration in hours. |
| `durationHoursMax` | Longest listed duration when a range is shown. |
| `durationText` | Duration label as Viator writes it. |
| `destination` | Destination city/region. |
| `destinationId` | Viator destination id. |
| `country` | Destination country when published. |
| `freeCancellation` | Present when free cancellation is offered. |
| `likelyToSellOut` | Present when Viator flags the experience. |
| `privateTour` | Present for private experiences. |
| `newOnViator` | Present for new listings. |
| `mobileTicket` | Present when a mobile ticket is accepted. |
| `languages` | Offered guide/audio languages. |
| `badges` | Viator merchandising badges, e.g. `SPECIAL_OFFER`. |
| `travelerImageCount` | Traveler photo count on a detail page. |
| `meetingPoints` | Meeting points with address, instructions and coordinates. |
| `itineraryStops` | Stops with duration, coordinates and admission flag. |
| `inclusions` / `exclusions` | Included and excluded items. |
| `additionalInfo` | Practical traveler notes. |
| `faqs` | Question/answer pairs when published. |
| `timeZone` | Local time zone. |
| `nextAvailableDate` | Next bookable date when published. |
| `maxTravelersPerBooking` | Booking size limit when published. |
| `productType` | Viator product type, e.g. `TOUR`. |

### Output per review (getReviews)

| Field | Description |
| --- | --- |
| `recordType` | `review`. |
| `scrapedAt` | ISO timestamp of capture. |
| `reviewId` | Viator/TripAdvisor review id. |
| `productCode` | Product code of the reviewed experience. |
| `productTitle` | Reviewed experience title. |
| `url` | Experience URL the review belongs to. |
| `reviewerName` | Reviewer display name. |
| `rating` | Reviewer rating (0–5). |
| `reviewTitle` | Review headline when supplied. |
| `reviewBody` | Full review text. |
| `reviewLanguage` | Review language code. |
| `publishedDate` | Publication timestamp. |
| `travelDate` | Date the reviewer traveled, when published. |
| `helpfulVotes` | Helpful-vote count. |
| `travelerType` | Reviewer party type, e.g. `FAMILY`. |
| `isTripadvisor` | Present when the review came from TripAdvisor. |
| `machineTranslated` | Present when Viator marks the review as translated. |
| `photos` | Traveler photo URLs attached to the review. |
| `ownerResponse` | Operator response text and date. |

### Inputs

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | select | `search` | One of the five modes above. |
| `searchQuery` | text | `Eiffel Tower tour` | Keyword(s) for `search`. |
| `destination` | text | `Paris` | City/region for `search`, `byDestination`, `byCategory`. |
| `startUrls` | string list | `[]` | Viator experience, destination or category URLs. |
| `category` | select | – | Activity category for `byCategory`. |
| `sortBy` | select | `default` | Result order. |
| `minPrice` / `maxPrice` | number | – | Price bounds. |
| `minRating` | number | – | Rating floor. |
| `minDurationHours` / `maxDurationHours` | number | – | Duration bounds. |
| `minReviewCount` | integer | – | Review-count floor. |
| `maxItems` | integer | `20` | Experience-record cap (prefill 3). |
| `maxReviewsPerExperience` | integer | `50` | Per-URL review cap (prefill 5). |

#### Examples

```json
{
  "mode": "search",
  "searchQuery": "Eiffel Tower tour",
  "maxItems": 20
}
```

```json
{
  "mode": "byCategory",
  "destination": "Paris",
  "category": "Food-and-Drink",
  "minRating": 4.5,
  "maxPrice": 120,
  "sortBy": "price-asc"
}
```

```json
{
  "mode": "getReviews",
  "startUrls": [
    "https://www.viator.com/tours/Paris/Eiffel-Tower-Small-Group-Tour/d479-3731EIFFELTOWER"
  ],
  "maxReviewsPerExperience": 100
}
```

### Backward compatibility

Saved tasks from earlier versions keep working. Older input keys such as `query`, `search`, `keyword`, `city`, `location`, `urls`, `productUrls`, `categoryName`, `sort`, `orderBy`, `priceMin`, `priceMax`, `ratingMin`, `durationMin`, `durationMax`, `minReviews`, `limit`, `max`, `maxReviews` and `reviewsPerExperience` are mapped in code. Existing output fields keep their names; new fields are added beside them.

### Use cases

- Travel agencies and OTAs benchmarking Viator prices, ratings and inclusions for a destination.
- Tour operators monitoring their own and competitors' listings.
- Market researchers comparing categories and destinations.
- Reputation and sentiment teams collecting review text, ratings and traveler photos.
- Content and itinerary builders sourcing descriptions, photos and booking links.

### FAQ

**Does this need a Viator account, cookie or API key?** No. It reads the same public pages a visitor sees.

**Why does keyword search stop at 200 results?** Viator's public search page itself caps a query at 200 results. Split a broad keyword into narrower queries or browse the destination/category listing for deeper coverage.

**Why might a sorted result look different from Viator's own sort?** Viator does not expose its server-side sort to cookieless clients, so the actor sorts the scanned listing window (up to 60 pages, about 1,440 experiences) before applying `maxItems`. For the default order it reads listing pages directly.

**Why are some fields missing on a record?** Viator does not publish every field for every experience. Missing values are omitted, never filled with nulls or placeholders.

**Why did a destination URL or category return nothing?** Some destinations have no public products, and category pages move over time. Try the destination name, a nearby major city, or a keyword search.

**Does this book anything or return live availability?** No. It returns publicly displayed prices and the next-published availability date; it does not reserve or book experiences.

**Is this affiliated with Viator?** No. This is an independent tool and is not affiliated with, endorsed by, or sponsored by Viator or TripAdvisor.

# Actor input Schema

## `mode` (type: `string`):

What to collect: keyword search, destination browse, category browse, experience details, or traveler reviews.

## `searchQuery` (type: `string`):

Keyword(s) for mode=search. Examples: Eiffel Tower tour, pasta making class, Seine cruise.

## `destination` (type: `string`):

City or region for mode=search, byDestination or byCategory. Examples: Paris, Rome, New York City.

## `startUrls` (type: `array`):

Viator experience, destination or category URLs. Used by getExperience, getReviews, byDestination and byCategory.

## `category` (type: `string`):

Category for mode=byCategory. Legacy Viator labels are accepted and mapped to the closest live category.

## `sortBy` (type: `string`):

Order of the returned experience records. Filters are applied first, then this order, then maxItems is applied.

## `minPrice` (type: `number`):

Keep experiences whose from-price is at or above this amount in the listing currency (USD by default).

## `maxPrice` (type: `number`):

Keep experiences whose from-price is at or below this amount in the listing currency (USD by default).

## `minRating` (type: `number`):

Keep experiences rated at or above this value (0 to 5).

## `minDurationHours` (type: `number`):

Keep experiences whose shortest listed duration is at least this many hours.

## `maxDurationHours` (type: `number`):

Keep experiences whose shortest listed duration is at most this many hours.

## `minReviewCount` (type: `integer`):

Keep experiences with at least this many traveler reviews.

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

Maximum number of experience records to return. Review mode uses maxReviewsPerExperience instead.

## `maxReviewsPerExperience` (type: `integer`):

Maximum number of traveler reviews to return for each experience URL (mode=getReviews).

## Actor input object example

```json
{
  "mode": "search",
  "searchQuery": "Eiffel Tower tour",
  "destination": "Paris",
  "startUrls": [],
  "sortBy": "default",
  "maxItems": 3,
  "maxReviewsPerExperience": 5
}
```

# Actor output Schema

## `records` (type: `string`):

Dataset containing experience records and, in getReviews mode, review records. Fields that Viator does not publish for a record are omitted rather than returned empty.

# 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 = {
    "mode": "search",
    "searchQuery": "Eiffel Tower tour",
    "destination": "Paris",
    "startUrls": [],
    "sortBy": "default",
    "maxItems": 3,
    "maxReviewsPerExperience": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("vexaloom-labs/viator-tours-activities-and-review-extractor").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 = {
    "mode": "search",
    "searchQuery": "Eiffel Tower tour",
    "destination": "Paris",
    "startUrls": [],
    "sortBy": "default",
    "maxItems": 3,
    "maxReviewsPerExperience": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("vexaloom-labs/viator-tours-activities-and-review-extractor").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 '{
  "mode": "search",
  "searchQuery": "Eiffel Tower tour",
  "destination": "Paris",
  "startUrls": [],
  "sortBy": "default",
  "maxItems": 3,
  "maxReviewsPerExperience": 5
}' |
apify call vexaloom-labs/viator-tours-activities-and-review-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/viator-tours-activities-and-review-extractor"
        }
    }
}
```

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/SyTxJi37J7eXIbysu/builds/r8VBpMvAChEhyptup/openapi.json
