# Ticketmaster Scraper - Events, Artists & Venues (`abotapi/ticketmaster-event-discovery`) Actor

Discover and scrape Ticketmaster events across the US, UK, Australia and Canada. Search by keyword, artist or venue, filter by city and date, or paste URLs directly. Includes incremental monitoring and resume support for ongoing event tracking.

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

## Pricing

from $1.20 / 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?

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

## Ticketmaster Events Scraper

Discover upcoming events on Ticketmaster across the US, UK, Australia and
Canada. Search by keyword, walk venue and artist pages, and narrow by city
or date. Built to beat `ticketmaster-events-scraper` with multi-market
coverage, more fields per event, and incremental monitoring.

### What it returns

One row per event: title, start and onsale dates, venue (name, city,
state, country, address, coordinates), artists, presale windows, status
flags (cancelled, postponed, resold, sold out), the seatmap image link,
and the event URL.

Per-event ticket price tiers are not included: Ticketmaster serves its
event detail pages only to verified browsers and refuses automated reads
on every connection type. The listing cards carry no prices either.

### Input

- **Mode**: keyword search or pasted Ticketmaster links.
- **Market** (search mode): United States, United Kingdom, Australia,
  Canada. Each market reads its own site.
- **Sort** (search mode): relevance or date.
- **City, Start date from/to**: narrow the fetched rows after the read
  (the site ignores these parameters itself).
- **Ticketmaster links** (URL mode): search, venue or artist links. Each
  link is walked forward page by page. Event detail links cannot be read
  by automated clients and are skipped with a warning.
- **Max items** (default 20): the only default cap. **Max pages**
  (default 0, no cap).
- **Proxy**: residential is recommended. Datacenter exits are refused on
  most draws. Residential proxy needs a paid Apify plan; runs without it
  fail fast with a connection message instead of returning empty results.
- **Resume and recurring updates**: resume an interrupted crawl with
  Resume from run, or track a search across scheduled runs with
  Incremental mode (new, updated, reappeared and expired events are
  stamped with changeType).

### Example output (illustrative placeholder values, not live listings)

| title | startDate | venueCity | market |
|---|---|---|---|
| Sample Summer Fest Night One | 2027-06-12T19:30:00Z | Sampleville | us |
| Sample Arena Rock Evening | 2027-07-03T20:00:00Z | Sampleville | us |

### Cost

Pay per event record plus a small per-run start charge. No surcharges:
every field comes from the listing read.

# Actor input Schema

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

Search looks up events by keyword on one market. URL mode reads the Ticketmaster pages you paste.

## `query` (type: `string`):

Search mode: a keyword, for example an artist, team, venue or city name.

## `market` (type: `string`):

Search mode: which Ticketmaster market to read. Each market has its own site and listings.

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

Search mode: result order. Relevance is the site default, date orders by start date.

## `city` (type: `string`):

Narrow rows to a venue city, state or country substring, for example Chicago or TX. Applied after the fetch.

## `dateFrom` (type: `string`):

Keep events starting on or after this date (YYYY-MM-DD). Applied after the fetch.

## `dateTo` (type: `string`):

Keep events starting on or before this date (YYYY-MM-DD). Applied after the fetch.

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

URL mode: one or more Ticketmaster search, venue or artist links. Event detail links cannot be read by automated clients and are skipped with a warning.

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

Maximum event records returned. The only default cap: 0 means no limit.

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

Maximum listing pages read per scope. 0 means no page cap.

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

The source serves every route from the standard datacenter connection pool; no residential proxy is needed. Bring your own proxy if your runs require one.

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

Continue an interrupted crawl: record ids from this run or dataset id are skipped. See Incremental mode below.

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

Track this search across runs: only new or changed events are returned, with changeType stamps. Cannot be combined with Resume from run when a baseline exists.

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

Custom baseline name for Incremental mode. Leave empty to derive one from the mode, market, query, filters and links.

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

Incremental mode: also return unchanged events, with changeType UNCHANGED. Returned rows are billed as usual.

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

Incremental mode: also return events that vanished since the last run, with changeType EXPIRED. Returned rows are billed as usual.

## Actor input object example

```json
{
  "mode": "search",
  "query": "concerts",
  "market": "us",
  "urls": [
    "https://www.ticketmaster.com/search?q=concerts"
  ],
  "maxItems": 20,
  "maxPages": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}
```

# 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",
    "query": "concerts",
    "market": "us",
    "urls": [
        "https://www.ticketmaster.com/search?q=concerts"
    ],
    "maxItems": 20,
    "maxPages": 0,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/ticketmaster-event-discovery").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",
    "query": "concerts",
    "market": "us",
    "urls": ["https://www.ticketmaster.com/search?q=concerts"],
    "maxItems": 20,
    "maxPages": 0,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/ticketmaster-event-discovery").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",
  "query": "concerts",
  "market": "us",
  "urls": [
    "https://www.ticketmaster.com/search?q=concerts"
  ],
  "maxItems": 20,
  "maxPages": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}' |
apify call abotapi/ticketmaster-event-discovery --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/ticketmaster-event-discovery"
        }
    }
}
```

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/ZbVMBdvMV6iMnyzyx/builds/78X2MYPE7e05fE7jP/openapi.json