# Viagogo Scraper: Events, Venues, Availability & Monitoring (`abotapi/viagogo-events-scraper`) Actor

Scrape Viagogo events by artist, production, venue, city, category, or URL. Extract event names, dates, venues, locations, availability, and links. Track NEW, UPDATED, REAPPEARED, and EXPIRED events with incremental runs, resume, and MCP export.

- **URL**: https://apify.com/abotapi/viagogo-events-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 event records

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

## Viagogo Scraper - Live Event Discovery

Scrape Viagogo (viagogo.com), the global event ticket marketplace, directly
from the same service its website reads. Search any artist, production,
venue, city or category and get the live events behind it: names, dates,
times, venues, cities, countries, availability and canonical links, for
tens of thousands of events across 70+ countries. It also monitors the
events across runs (NEW, UPDATED, REAPPEARED, EXPIRED), resumes interrupted
pulls, and pipes results into your apps through MCP connectors.

### Why This Scraper?

- Real site-service data: each keyword returns the source's own served
  window of up to 20 events with venue, city, country, date and time in one
  record, plus a curated raw snapshot so nothing upstream is dropped.
- Keyword search across the whole catalogue: artists, productions, venues,
  cities and categories all work as search terms.
- Link mode: paste production, venue, category, city or search links and
  the actor reads them the same way.
- Availability monitoring: scheduled runs classify every event as NEW,
  UPDATED, UNCHANGED, REAPPEARED or EXPIRED, with per-campaign state you
  can name or share.
- MCP connector export: send results to Notion and other connectors without
  changing the dataset.
- Structured failures: a blocked or broken run fails loudly with a clear
  message instead of returning an empty dataset.

### Data You Get

> Sample shape: values are illustrative placeholders, not from a live listing.

| Field | Example value |
|---|---|
| kind | event |
| recordId | event-160895598 |
| eventId | 160895598 |
| title | Usher and Chris Brown |
| url | https://www.viagogo.com/Concert-Tickets/.../E-160895598 |
| dayOfWeek | Sat |
| formattedDate / formattedTime | Nov 07 2026 / 12:00 AM |
| startDateTimeUtc | 2026-11-07T05:00:00+00:00 |
| isDateConfirmed / isTimeConfirmed | true / false |
| isTbd / isMultidayEvent / isParkingEvent | false / false / false |
| venueTimeZoneOffsetHours | -5.0 |
| eventState / availabilityState | 1 / 1 |
| hasListings | true |
| allowPublicPurchase | true |
| venueId / venueName | 27372 / Mercedes-Benz Stadium |
| venueCity / venueLocation | Atlanta / Atlanta, GA, USA |
| countryCode / countryName | US / United States |
| searchKeyword | Usher |
| changeType | NEW |
| firstSeenAt / lastSeenAt | 2026-01-01T00:00:00.000Z |

With the matches toggle on you also get the search page's top production,
venue and category hits (kind=match: title, subtitle, entityType, rank,
url). Every record also carries a curated upstream snapshot (raw), from
which per-request session tokens, this-user flags and UI-copy blobs are
stripped so monitoring classifies real changes only.

Ticket seat-level listings (sections, rows, seat prices) live behind the
source's edge protection on event pages and are NOT part of this dataset;
the actor reads the open search lane only.

### How to Use

Zero setup: the search lane is open. Paste one or more search terms (an
artist such as Coldplay, a production, a venue, a city, or a category) and
run. Each term returns the source's served window of up to 20 events, best
matches first. For wide acts (Coldplay lists 400+ events) split your need
across narrower terms, city names, or production links. For recurring
alerting, switch on incremental mode and schedule the run.

### Input Parameters

| Parameter | Type | Default | Description |
|---|---|---|---|
| mode | select | search | search (keywords) or url (links) |
| queries | list | `Coldplay` | Artist, production, venue, city or category text, one per entry |
| urlInputs | list | empty | Production, venue, category, city or search links (url mode) |
| urls | list | empty | Alias for urlInputs, accepted under the usual Apify URL-mode name |
| includeMatches | boolean | false | Also emit top production/venue/category matches, kind=match |
| maxItems | integer | 20 | Stop after this many records (0 = no limit) |
| resumeFromRunId | string | empty | Continue one interrupted run, skipping collected ids |
| incrementalMode | boolean | false | Recurring monitoring with change detection |
| stateKey | string | empty | Name a monitoring campaign (incremental mode) |
| emitUnchanged | boolean | false | Also return UNCHANGED rows (returns and bills extra rows) |
| emitExpired | boolean | false | Also return EXPIRED rows after a complete scan |
| mcpConnectors | array | empty | Optional MCP connector export |
| notionParentPageUrl | string | empty | Notion parent page for the Notion connector |
| maxNotifyListings | integer | 50 | Cap per connector per run |
| proxyConfiguration | object | proxy on | Standard Apify proxy settings |

Filters apply to search mode only; link mode reads the links you name
directly. Source limit: one term serves at most 20 events and the source
ignores page parameters, so cover larger catalogues with several narrower
terms rather than one wide one. Event-only links (/E-<id>) are not readable
and are reported as skipped.

### Output Example

> Sample shape: values are illustrative placeholders, not from a live listing.

```json
{
  "kind": "event",
  "recordId": "event-160895598",
  "eventId": "160895598",
  "title": "Usher and Chris Brown",
  "url": "https://www.viagogo.com/Concert-Tickets/Rap-and-Hip-Hop-Music/Usher-Tickets/E-160895598",
  "dayOfWeek": "Sat",
  "formattedDate": "Nov 07 2026",
  "formattedTime": "12:00 AM",
  "startDateTimeUtc": "2026-11-07T05:00:00+00:00",
  "isDateConfirmed": true,
  "isTimeConfirmed": false,
  "eventState": 1,
  "availabilityState": 1,
  "hasListings": true,
  "allowPublicPurchase": true,
  "venueId": 27372,
  "venueName": "Mercedes-Benz Stadium",
  "venueCity": "Atlanta",
  "venueLocation": "Atlanta, GA, USA",
  "countryCode": "US",
  "countryName": "United States",
  "searchKeyword": "Usher",
  "raw": { "curated upstream event object" },
  "changeType": "NEW",
  "changedFields": [],
  "firstSeenAt": "2026-01-01T00:00:00.000Z",
  "lastSeenAt": "2026-01-01T00:00:00.000Z"
}
```

### Monitoring, Resume and MCP Export

Incremental mode keeps one baseline per search setup (keywords, mode and
matches toggle; or your own State key) in the actor's key-value store, with
an optimistic-concurrency check so a crashed run never clobbers it. The
first run returns everything as NEW; later runs return NEW, UPDATED and
REAPPEARED events, and mark EXPIRED ones only after a complete, uncapped,
non-resumed scan that saw at least one record. State commits only on the
normal success path. resumeFromRunId continues ONE interrupted pull by
seeding the dedup set from that run's or dataset's record ids. mcpConnectors
writes the same records into your authorized connectors (rich pages on
Notion, best-effort digest elsewhere), capped per connector by
maxNotifyListings; it never changes the dataset.

### Send results into your apps (MCP connectors)

Optionally pipe results into the apps you already use through Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape, and it never changes the dataset.

1. Authorize a connector once under **Apify, Settings, API and Integrations** (Notion, Linear, Airtable or Apify).
2. Select it in the **mcpConnectors** field. If the picker is empty, you have not authorized a connector yet.
3. For **Notion**, also set **notionParentPageUrl** to the URL or id of the page under which item pages are created.

### Plan Requirement and Terms Note

The actor uses the Apify proxy with automatic exit rotation; run it on any
plan that includes proxy access. The source is a public ticket marketplace:
the actor reads the same search service the site's own browser reads, and
automated reading may sit outside the source's terms of use, so keep volumes
reasonable and respect the source's terms.

# Actor input Schema

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

Search finds events for one or more keywords (artist, production, venue, city or category text). Link mode reads the events behind production, venue, category, city or search links.

## `queries` (type: `array`):

One entry per search: an artist (Coldplay), a production (The Lion King), a venue (Madison Square Garden), a city (Chicago) or a category (Concerts). Multi-value supported.

## `urlInputs` (type: `array`):

Link mode: production (.../Usher-Tickets), venue (.../\_V-27372), category (/Concert-Tickets), city (/Atlanta) or search (.../?q=coldplay) links. Event-only links (/E-<id>) are not readable and are reported as skipped.

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

Alias for Links, accepted under the name other Apify actors use for URL mode. Entries are read in order.

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

Stop after this many records (0 = no limit; the run then stops when the served windows run out). Event records and, optionally, match records share this budget, so matches do not crowd out the events you are after.

## `includeMatches` (type: `boolean`):

Off by default: the dataset then carries event records only. Turn on to also emit the search page's top production, venue and category matches, marked kind=match.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large pull without returning events already collected there.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or recurring monitoring. The first run returns every matching event as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED events. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately for each keyword, filter and lookup setup; use State key to name or deliberately share a monitoring campaign.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the search and filter settings.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return events that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return events that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API & Integrations, then select it here. Notion gets a rich page-per-item export; other connectors get a best-effort write or digest. Leave empty to skip; never changes the dataset output.

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which event pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

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

Apify Proxy settings. Works on every proxy plan; requests go through connection pools with automatic exit rotation.

## Actor input object example

```json
{
  "mode": "search",
  "queries": [
    "Coldplay"
  ],
  "urlInputs": [
    "https://www.viagogo.com/Concert-Tickets/Rap-and-Hip-Hop-Music/Usher-Tickets"
  ],
  "maxItems": 20,
  "includeMatches": false,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "maxNotifyListings": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `overview` (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 = {
    "mode": "search",
    "queries": [
        "Coldplay"
    ],
    "urlInputs": [
        "https://www.viagogo.com/Concert-Tickets/Rap-and-Hip-Hop-Music/Usher-Tickets"
    ],
    "maxItems": 20,
    "includeMatches": false,
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "maxNotifyListings": 50,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/viagogo-events-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 = {
    "mode": "search",
    "queries": ["Coldplay"],
    "urlInputs": ["https://www.viagogo.com/Concert-Tickets/Rap-and-Hip-Hop-Music/Usher-Tickets"],
    "maxItems": 20,
    "includeMatches": False,
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "maxNotifyListings": 50,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/viagogo-events-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 '{
  "mode": "search",
  "queries": [
    "Coldplay"
  ],
  "urlInputs": [
    "https://www.viagogo.com/Concert-Tickets/Rap-and-Hip-Hop-Music/Usher-Tickets"
  ],
  "maxItems": 20,
  "includeMatches": false,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "maxNotifyListings": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call abotapi/viagogo-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/viagogo-events-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/bq2TVYAXktcLi9OHu/builds/CbYhFf0jLlqD8giBv/openapi.json