# Viator Tour Search & Watchlist — Prices and Durations (`jpmarketdata/viator-tour-search-watchlist`) Actor

Monitor Viator destination and activity-category tour catalogues with displayed starting prices, actual currency, durations, cancellation flags and ratings. Bulk clean URLs, source pagination and unique-tour billing. Unofficial.

- **URL**: https://apify.com/jpmarketdata/viator-tour-search-watchlist.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Travel, Automation, Developer tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.80 / 1,000 viator tour delivereds

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

## Viator Tour Search & Watchlist

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by Viator**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Fetch public destination and activity-category tour catalogues with displayed starting prices, currency, durations, offered languages, cancellation flags and aggregate ratings. Built for tour operators and travel-content teams that rerun several catalogues and compare stable productCodes. From-prices are undated snapshots, not final booking or availability quotes.

### Input

`urls`: 1–10 clean destination or category catalogue URLs, default Paris and Rome. Supported paths are /City/d<ID>-ttd and /City-tours/Category/d<ID>-g<group>-c<category>. No query, fragment, credentials or arbitrary source URL. `maxItems`: 1–500 global delivered unique tours, default 48. `maxPagesPerSource`: 1–5, default 2. Source requests/rows are allocated fairly across catalogues, so the default reaches both cities. Deduplicate productCode across catalogues before billing. Follow source path pagination, never forbidden ?page/?currency/?sortBy filters.

### Output

One type=tour_listing row per unique productCode. Columns include exact source tour URL, short title, primary destination and ID, priceFrom/currency/priceAvailability, optional same-currency comparisonPrice, exact aggregate rating/reviewCount, source-unit durationMin/durationMax/durationUnit, freeCancellation, priceVariesByGroupSize, languageCodes, likelyToSellOut/newProduct/privateTour, first sourceUrl/sourcePage/sourcePosition, priceBasis and observedAt. Optional unknown fields are omitted, never replaced by false, zero or null. An intact no-price product is returned with priceAvailability=no_reported_amount and no priceFrom; source currency is required whenever priceFrom is reported. A missing pricingInfo container is structure-change.

The source can choose a different currency by region; preserve its actual numeric currency units without dividing by 100 or converting. Compare matching currency and priceBasis across runs. Source merchandising/relevance order is preserved within each source and bounded multi-source coverage is reported. It is not a random, complete, cheapest or demand-ranked market census. Product URLs are matched by exact productCode from TouristDestination or CollectionPage JSON-LD. Products marked shouldHideFromCrawlers are excluded and counted. A nonempty page containing only hidden products remains a scanned page and pagination continues; fail zero-results only if the whole requested scope yields no usable tours. Source badges and JSON-LD InStock do not establish booking availability. No maintained price history is stored; schedule downstream diffs by productCode.

Uncharged OUTPUT reports advertised source totals/pages, pages/cards scanned, delivered unique rows, skipped hidden cards, item/page/budget caps and stop reasons. A required source failure is surfaced explicitly, never silently omitted.

### Limits and failures

Lightweight Chrome TLS HTTP/embedded JSON, 256MB, no browser/proxy/paid external API. At most 61 GET attempts including robots and retries, 5MB decompressed per response, 25s/request, 180s/run and >=1s sequential pacing. Fetch live robots before catalogue pages and recheck source pagination/redirects. Source blocks/auth/challenges, rate limit, timeouts, URL/robots violations, missing identity/pricing/state, malformed or repeated pagination and zero delivered tours fail explicitly. Any required source failure is surfaced; a successful empty paid catalogue is not promised. DC reachability and cloud costs are unconfirmed before authorized release.

### Privacy and rights

Explicit field whitelist excludes copyrighted descriptions/itinerary prose/reviews/images, supplier/reviewer person names/contacts, unlabelled international telephone numbers and raw session/CSRF/nonce/cookie/user/tracking state. Respect shouldHideFromCrawlers. Current source Terms 4.2(b) restrict automation; the exact applicable excerpt and DR-0007 guard are recorded in the scout. This Actor is unaffiliated with Viator and performs no account, contact or booking action. The official Partner API is a separate partner/API-key option.

### Pricing

One viator-tour-delivered primary event at $0.0008 per unique tour actually delivered. No custom start or secondary event and no actor-defined free rows. Hidden, duplicate or undelivered cards are not charged. Platform memory/start charges may still apply. Require available event allowance to cover maxItems before source work; fail charge-limit if insufficient. Duplicate input URLs are normalized before requests.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
- **Delivered rows only.** One validated unique row is one billable event. Duplicates, summaries, failed acquisition and undelivered rows are not charged.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public source data only.** No login or member/applicant records. Contact patterns are screened before delivery; prose may still name people.

### More tools by the same author

- [Mercari Japan Sold Prices — What Items Really Sell For](https://apify.com/jpmarketdata/mercari-japan-price-checker)
- [Yahoo! Auctions Japan Sold Prices — Median, Range, Bids](https://apify.com/jpmarketdata/yahoo-auction-sold-comps)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by Viator**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

## `urls` (type: `array`):

1–10 clean https://www.viator.com destination /City/d<ID>-ttd or category /City-tours/Category/d<ID>-g<group>-c<category> URLs. No query, fragment, credentials, arbitrary paths or pagination suffix; Actor follows permitted source path pagination.

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

1–500 delivered unique tours across all catalogues, default 48. Results are allocated fairly across requested sources rather than exhausting the first catalogue.

## `maxPagesPerSource` (type: `integer`):

1–5 genuine path pages per source, default 2. Source order is merchandising/relevance, not cheapest or unbiased. Coverage and stop reasons are reported.

## Actor input object example

```json
{
  "urls": [
    "https://www.viator.com/Paris/d479-ttd",
    "https://www.viator.com/Rome/d511-ttd"
  ],
  "maxItems": 48,
  "maxPagesPerSource": 2
}
```

# Actor output Schema

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

Validated source records with original links and truthful source limits.

# 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("jpmarketdata/viator-tour-search-watchlist").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("jpmarketdata/viator-tour-search-watchlist").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 jpmarketdata/viator-tour-search-watchlist --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/viator-tour-search-watchlist"
        }
    }
}
```

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/gsarL5UMhngscs89R/builds/tcmucGhmu26GDV29L/openapi.json