Ticketmaster Scraper

Ticketmaster Scraper at a glance

Ticketmaster Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes kind, recordid, eventid, discoveryid and market, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Web data
Pricing: $2.00 per 1,000 results (Free plan), from $1.20 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 24 options

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.

What Ticketmaster Scraper can do

Two ways to find events. Search by keyword on one market, or paste search, venue and artist links to read exact listings without building URLs by hand.
Sixteen markets. us, uk, au, ca, ae, at, ch, cz, de, dk, fi, it, mx, nz, se and za, each read from its own Ticketmaster site.
Rich event records. Venue address and coordinates, the full artist lineup, every presale window, and status flags for cancelled, postponed, rescheduled, sold out and limited availability shows.
Narrow without extra requests. City and date filters trim the fetched rows down to just what you need.
Built for schedules. Incremental mode returns only new and changed events on recurring runs, and a refused run fails loudly instead of returning an empty dataset.
Resume anytime. Continue an interrupted crawl without paying twice for records you already collected.

Choose what to collect

These inputs let you configure Ticketmaster Scraper - Events, Artists & Venues. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string	Search looks up events by keyword on one market. URL mode reads the Ticketmaster pages you paste. Choices: search, url
`query`string	Search mode: a keyword, for example an artist, team, venue or city name.
`market`string	Search mode: which Ticketmaster market to read. Each market has its own site and listings. Choices: us, uk, au, ca, ae, at, ch, cz, de, dk, fi, it, mx, nz, se, za
`sort`string	Search mode: result order. Relevance is the site default, date orders by start date. Choices: relevance, date
`city`string	Narrow rows to a venue city, state or country substring, for example Chicago or TX. Applied after the fetch.
`dateFrom`string	Keep events starting on or after this date (YYYY-MM-DD). Applied after the fetch.
`dateTo`string	Keep events starting on or before this date (YYYY-MM-DD). Applied after the fetch.

Show 17 more inputs

More input fields
Input	What it controls
`startDate`string	Alias of dateFrom (YYYY-MM-DD); dateFrom wins when both are set.
`endDate`string	Alias of dateTo (YYYY-MM-DD); dateTo wins when both are set.
`urls`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`integer	Maximum event records returned. The only default cap: 0 means no limit.
`maxPages`integer	Maximum listing pages read per scope. 0 means no page cap set by you; the actor still stops at its built-in hard limit of 1000 pages per scope, or earlier at the natural end of the listing.
`resumeFromRunId`string	Continue an interrupted crawl: record ids from this run or dataset id are skipped. See Incremental mode below.
`incrementalMode`boolean	Track this search across runs: only new or changed events are returned, with changeType stamps. An event is UPDATED when any field of its record changes (title, dates, venue, artists, presale windows, status flags such as sold out, cancelled or postponed, image links), except fields you list under Ignore fields; the raw upstream object is never compared. Ticket prices are not part of the record. Cannot be combined with Resume from run when a baseline exists.
`stateKey`string	Custom baseline name for Incremental mode. Leave empty to derive one from the mode, market, query, filters and links; in search mode the pre-filled link list is ignored, and the ignore list and change scope are never part of it.
`emitUnchanged`boolean	Incremental mode: also return unchanged events, with changeType UNCHANGED. Returned rows are billed as usual.
`emitExpired`boolean	Incremental mode: also return events that vanished since the last run, with changeType EXPIRED. Only a complete scan can expire events: runs that were resumed, hit Max items or Max pages, or started from a link past the first page never do. A vanished listing may be a delisting or just a listing change. Returned rows are billed as usual.
`changeScope`string	All fields (default): any change to the event record returns an UPDATED row. Availability only: only on-sale date, sold out, limited availability, ticketing status, cancelled, postponed, rescheduled and presale window changes return an UPDATED row; changes to title, venue, artists or images never do. Ticket prices are not part of the record. Choices: all, priceAndStock
`compactUpdates`boolean	Off by default. When on, UPDATED and EXPIRED rows are short: record id, event id, url, title, start date and current availability flags, plus priceChanges and variantChanges showing the old and new value of each moved availability field and presale window. NEW rows always carry the complete record.
`expireAfterMissedScans`integer	Only used with Emit expired. An event is marked EXPIRED only after it has been missing from this many complete scans in a row (default 1). A returning event resets the count. A vanished listing may be a delisting or a listing change; the status flags report sold out or cancelled events.
`ignoreFieldsForChanges`array	Optional. Field names to exclude from UPDATED change detection, for example venueImageUrl or seatmapImageUrl if an image link keeps rotating. Use a dotted name such as presales.endDateTime to ignore a key inside every presale or artist element while the rest of the element is still compared. Ignored fields stay in the output. Changing this list does not mark saved events as updated.
`mcpConnectors`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`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`integer	Cap on items written to each connector per run. Does not affect the dataset.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

kindkind

recordIdrecordId

eventIdeventId

discoveryIddiscoveryId

marketmarket

urlurl

titletitle

startDatestartDate

onsaleDateonsaleDate

spanMultipleDaysspanMultipleDays

timeZonetimeZone

cancelledcancelled

Show 28 more fields

postponedpostponed

rescheduledrescheduled

soldOutsoldOut

limitedAvailabilitylimitedAvailability

ticketingStatusticketingStatus

virtualvirtual

venueNamevenueName

venueCityvenueCity

venueStatevenueState

venueCountryvenueCountry

venueCountryCodevenueCountryCode

venueAddressvenueAddress

venuePostalCodevenuePostalCode

venueLatitudevenueLatitude

venueLongitudevenueLongitude

venueUrlvenueUrl

venueImageUrlvenueImageUrl

artistsartists

artistNamesartistNames

presalespresales

seatmapImageUrlseatmapImageUrl

categoryIdcategoryId

changeTypechangeType

changedFieldschangedFields

firstSeenAtfirstSeenAt

lastSeenAtlastSeenAt

priceChangespriceChanges

variantChangesvariantChanges

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "kind": "event",
  "recordId": "us:SAMPLE0001A",
  "eventId": "SAMPLE0001A",
  "discoveryId": "sampleDiscoveryId1",
  "market": "us",
  "url": "https://www.ticketmaster.com/sample-arena-rock-night-sampleville/event/SAMPLE0001A",
  "title": "Sample Arena Rock Night",
  "startDate": "2027-06-12T19:30:00Z",
  "onsaleDate": "2027-01-05T14:00:00Z",
  "spanMultipleDays": false,
  "timeZone": "America/New_York",
  "cancelled": false,
  "postponed": false,
  "rescheduled": false,
  "soldOut": false,
  "limitedAvailability": false,
  "ticketingStatus": "onsale",
  "virtual": false,
  "venueName": "Sample Arena",
  "venueCity": "Sampleville",
  "venueState": "SV",
  "venueCountry": "Sample Country",
  "venueCountryCode": "SC",
  "venueAddress": "1 Sample Way",
  "venuePostalCode": "00000",
  "venueLatitude": 40,
  "venueLongitude": -75,
  "venueUrl": "https://www.ticketmaster.com/sample-arena-tickets-sampleville/venue/000000",
  "venueImageUrl": "https://example.invalid/sample-venue.jpg",
  "artists": [
    {
      "name": "Sample Act",
      "url": "https://www.ticketmaster.com/sample-act-tickets/artist/000000",
      "imageUrl": "https://example.invalid/sample-act.jpg"
    }
  ],
  "artistNames": [
    "Sample Act"
  ],
  "presales": [
    {
      "name": "Artist Presale",
      "startDateTime": "2027-01-03T14:00:00Z",
      "endDateTime": "2027-01-05T02:00:00Z"
    }
  ],
  "seatmapImageUrl": "https://example.invalid/sample-seatmap.png",
  "categoryId": "SampleCategoryId1",
  "raw": {}
}

Ways to use this data

Ticket resale and pricing tools: track lineups, sold out status and onsale dates to plan when to buy or list tickets.
Fan alert services: watch an artist or venue for newly announced shows and presale windows.
Event aggregators and listing sites: build a searchable calendar of concerts, sports and other live events across multiple markets.
Tour and venue analytics: track how often venues host events, and which cities an artist is touring through.
Marketing and CRM teams: match upcoming shows in a city to customer segments for local promotions.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does Ticketmaster Scraper return?

The documented output for Ticketmaster Scraper includes kind, recordid, eventid, discoveryid, market, url, title and startdate. Availability of each field depends on the source page and the selected mode.

How much does Ticketmaster Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.20 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Can I get only new or changed events on a schedule?

Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated, reappeared or expired records for that search or link set, and unchanged ones are not billed unless you turn that on too. Do not add Resume from run to these runs: records it skips are not added to the baseline and can come back later as NEW and be billed again. In URL mode with Emit expired on, a link that errors partway through can return still-live events as EXPIRED, so check the log for "errored" before acting on those rows, or leave Emit expired off.

Why did my run fail instead of returning an empty dataset?

If every request is refused, the run stops with a clear message so "no events found" is never confused with "nothing could be read". Run it again in a few minutes. If only some pages or links could be read, you still get what was found, and the run succeeds.

Can I use it with AI agents?

Yes. Call it from any Apify integration, or through Apify's API, and read the results from your own agent or app.