Ticketmaster Event Scraper 🎫

What does Ticketmaster Concert Event Scraper do?

Ticketmaster Concert Event Scraper is a Ticketmaster event scraper for collecting structured concert listings from public discover, category, search, and location-filtered URLs. Paste a Ticketmaster result URL into startUrl, choose how many events and pages to collect, and receive a clean dataset with event identity, dates, status flags, venues, locations, and artist information.

Use the results for concert discovery, venue calendars, local event monitoring, tour research, event aggregation, market analysis, and scheduled snapshots of Ticketmaster listings. The Actor removes empty values from saved records, so each dataset item contains the fields that Ticketmaster provides for that event.

Why use Ticketmaster Concert Event Scraper?

• URL-driven collection - Reuse a Ticketmaster discover or search URL with its category, keyword, date, country, region, or market filters.
• Structured event records - Collect event titles, stable IDs, direct event URLs, dates, on-sale dates, venue details, artist names, and availability flags.
• Location-aware datasets - Monitor a country, region, DMA, city market, or specific venue area when the source URL includes those filters.
• Controlled run size - Use results_wanted and max_pages for quick tests, targeted lists, or broader event datasets.
• Monitoring-ready output - Schedule repeat runs, compare event status over time, and connect results to dashboards, spreadsheets, alerts, or applications.
• Apify exports and integrations - Download JSON, CSV, Excel, or XML, or send completed run data to other services through Apify integrations.

What data can you extract from Ticketmaster?

Each dataset item represents one Ticketmaster event. Optional fields are omitted when the source does not provide a value.

Field	Type	Description
title	String	Event title shown by Ticketmaster.
id	String	Ticketmaster event identifier.
discoveryId	String	Ticketmaster discovery feed identifier when available.
url	String	Direct Ticketmaster event URL.
timeZone	String	Event time zone.
eventChangeStatus	String	Event status or change label.
startDate	String	Event start date and time in ISO format when available.
onsaleDate	String	Ticket on-sale date and time in ISO format when available.
dateDisplay	String	Ticketmaster's formatted date display value.
spanMultipleDays	Boolean	Whether the event spans multiple days.
cancelled	Boolean	Whether the event is marked as cancelled.
postponed	Boolean	Whether the event is marked as postponed.
rescheduled	Boolean	Whether the event is marked as rescheduled.
tba	Boolean	Whether the event date or time is to be announced.
local	Boolean	Whether Ticketmaster marks the event as local to the selected market.
sameRegion	Boolean	Whether the event is in the selected region.
soldOut	Boolean	Whether the event is marked as sold out.
limitedAvailability	Boolean	Whether Ticketmaster marks availability as limited.
virtual	Boolean	Whether the event is virtual.
partnerEvent	Boolean	Whether the event is identified as a partner event.
isPartner	Boolean	Partner classification flag when provided.
showTmButton	Boolean	Ticketmaster button display flag when provided.
venueName	String	Venue name.
venueCity	String	Venue city.
venueState	String	Venue state, province, or region.
venueCountryCode	String	Venue country code.
venueCountryName	String	Venue country name.
venueAddressLineOne	String	First venue address line.
venueCode	String	Ticketmaster venue code.
venueLatitude	Number	Venue latitude when available.
venueLongitude	Number	Venue longitude when available.
venueUrl	String	Ticketmaster venue URL.
artistNames	Array	Names of artists attached to the event.
artists	Array	Artist objects containing names, artist URLs, and image URLs when available.
majorCategoryId	String	Ticketmaster major category identifier when available.

How to scrape Ticketmaster event data

1. Open Ticketmaster and find a public discover, category, search, or location-filtered result page.
2. Copy the complete URL, including any filters you want to preserve.
3. Open Ticketmaster Concert Event Scraper on Apify and paste the URL into startUrl.
4. Set results_wanted and max_pages, or keep the defaults for a first run.
5. Leave the residential proxy configuration enabled for more reliable hosted runs, especially for repeated or larger collections.
6. Run the Actor, review the dataset preview, and download or connect the results to your workflow.

Supported URL patterns include /discover/concerts, discover URLs with classificationId, Ticketmaster keyword search URLs with q, and discover URLs using filters such as dma_id, countryCodes, region, startDate, or endDate.

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	Yes	https://www.ticketmaster.com/discover/concerts?classificationId=KnvZfZ7vAve	Public Ticketmaster discover, category, or search URL. The URL must use the ticketmaster.com domain.
results_wanted	Integer	No	20	Maximum number of event records to save.
max_pages	Integer	No	5	Maximum number of result pages to process.
proxyConfiguration	Object	No	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}	Apify Proxy settings. Residential proxy is enabled in the default input for more stable hosted runs.

The Actor accepts one startUrl per run. To collect different markets or categories, run separate URLs or create a schedule for each target URL.

Usage Examples

Basic Concert Category Collection

Collect up to 50 events from a Ticketmaster concert category and process no more than three pages.

{
  "startUrl": "https://www.ticketmaster.com/discover/concerts?classificationId=KnvZfZ7vAve",
  "results_wanted": 50,
  "max_pages": 3
}

Artist or Keyword Search

Use a Ticketmaster search URL to collect events matching an artist, tour, venue, or other keyword.

{
  "startUrl": "https://www.ticketmaster.com/search?q=taylor+swift&classificationId=KnvZfZ7vAeA",
  "results_wanted": 100,
  "max_pages": 5
}

Market and Date-Filtered Collection

Preserve Ticketmaster URL filters to collect events for a selected market and date window. The exact dma_id, dates, and country codes should come from the Ticketmaster URL you want to monitor.

{
  "startUrl": "https://www.ticketmaster.com/discover/concerts?dma_id=324&countryCodes=US&startDate=2026-09-01&endDate=2026-12-31",
  "results_wanted": 100,
  "max_pages": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Sample Output

This example shows one realistic dataset item. Fields that are not published for a particular event are left out of that item.

{
  "title": "Summer Sounds Live",
  "id": "1B0062B206496DE0",
  "discoveryId": "G5viZblFk3pMO",
  "url": "https://www.ticketmaster.com/summer-sounds-live-tickets/artist/1234567",
  "timeZone": "America/Chicago",
  "eventChangeStatus": "onsale",
  "startDate": "2026-09-18T19:30:00Z",
  "onsaleDate": "2026-06-12T15:00:00Z",
  "dateDisplay": "Fri, Sep 18, 2026",
  "cancelled": false,
  "postponed": false,
  "rescheduled": false,
  "soldOut": false,
  "limitedAvailability": true,
  "virtual": false,
  "venueName": "Minglewood Hall",
  "venueCity": "Memphis",
  "venueState": "TN",
  "venueCountryCode": "US",
  "venueCountryName": "United States",
  "venueAddressLineOne": "1555 Madison Avenue",
  "venueLatitude": 35.1432,
  "venueLongitude": -90.0184,
  "venueUrl": "https://www.ticketmaster.com/minglewood-hall-tickets/venue/12345",
  "artistNames": [
    "Example Artist"
  ],
  "artists": [
    {
      "name": "Example Artist",
      "url": "https://www.ticketmaster.com/example-artist-tickets/artist/987654",
      "imageUrls": [
        "https://s1.ticketm.net/dam/a/example-artist.jpg"
      ]
    }
  ],
  "majorCategoryId": "KZFzniwnSyZfZ7v7nJ"
}

Tips for Best Results

• Copy complete result URLs - Use a discover or search page URL that already contains the category, keyword, market, country, or date filters you need.
• Start with a small limit - Test with results_wanted: 20 before increasing the collection size.
• Match page and result limits - Increase max_pages when you need broader coverage, but keep it aligned with the number of events you want.
• Keep the proxy enabled for hosted runs - Residential Apify Proxy can improve consistency during larger or recurring collections.
• Review the dataset preview - Confirm that the URL returns the expected category, market, dates, venue, and artist coverage before scheduling the run.
• Expect optional fields - Ticketmaster does not publish every field for every event. Empty values are removed from the saved record rather than represented as empty strings or objects.
• Report source changes - Public event pages and their available fields can change. Use the Actor's Issues tab when a previously working URL no longer returns the expected records.

Integrations and Export Formats

• Google Sheets - Export event records for venue planning, reporting, and calendar preparation.
• Airtable - Build a searchable event database with dates, locations, artists, and status flags.
• Webhooks - Trigger downstream actions after a run finishes or new event data is available.
• Make or Zapier - Connect event collection to alerts, databases, email, or other no-code workflows.
• Apify API - Start runs and retrieve dataset items programmatically.
• JSON, CSV, Excel, and XML - Download the dataset in formats suited to applications, analysis, reporting, and system integrations.

Frequently Asked Questions

What Ticketmaster URLs are supported?

Ticketmaster discover and search result URLs are supported, including concert category URLs, keyword searches with q, classification filters, DMA filters, country filters, region filters, and date ranges. Individual event-detail URLs are not the intended input.

Can I search for an artist or tour?

Yes. Use a Ticketmaster /search URL with a q parameter containing the artist, tour, venue, or keyword you want to collect.

Can I filter events by location or date?

Yes. Copy a Ticketmaster URL that includes supported filters such as dma_id, countryCodes, region, startDate, or endDate. The Actor preserves those filters when collecting the results.

How many events can I collect?

The collection size is controlled by results_wanted and max_pages. The Actor stops when it reaches the requested result limit, the page limit, or the last available result page.

Why are some output fields missing?

Some fields are missing because Ticketmaster does not publish them for every event. The Actor removes empty values so the dataset contains only available information for each record.

Can I monitor changes over time?

Yes. Create an Apify Schedule for the same Ticketmaster URL and compare each dataset with earlier runs to monitor new events, cancellations, postponements, reschedules, sold-out flags, and venue coverage.

Can I export Ticketmaster data to CSV or Excel?

Yes. Apify datasets can be downloaded as CSV, Excel, JSON, XML, and other supported formats, or connected to integrations such as Google Sheets, webhooks, Make, and Zapier.

Is it legal to collect Ticketmaster data?

Public web data collection may be subject to Ticketmaster's terms, applicable laws, and privacy requirements. You are responsible for using this Actor lawfully, respecting access limits, and collecting only data you are authorized to use.

Related Actors

• Eventbrite Scraper - Collect event listings, dates, venues, categories, prices, and ticket URLs from Eventbrite.
• StubHub Event Scraper - Collect live event listings with venue, availability, and ticket-market fields from StubHub.
• Dice.fm Events Scraper - Collect music and DJ events with artists, venues, dates, prices, and ticket details from Dice.fm.
• Meetup Events Scraper - Collect public community and event listings with locations, dates, groups, attendance, and fee details from Meetup.

Support

For run issues, feature requests, or URL compatibility questions, use the Issues tab on the Actor page or contact the developer through Apify.

Legal Notice

This Actor is intended for legitimate collection of publicly available Ticketmaster event information. Users are responsible for complying with Ticketmaster's terms, applicable laws, privacy rules, and any restrictions that apply to their intended use of the data.