Pricing

Rating

Developer

Actor stats

Categories

Share

Ticketmaster Concert Event Scraper

Collect structured Ticketmaster event data from discover and search pages by pasting a Ticketmaster URL. The actor turns category pages, keyword searches, and location-filtered discover URLs into clean event datasets with pagination, venue details, status flags, and artist information. Residential Apify Proxy is the recommended default for reliable hosted runs.

Features

• URL-driven input - Paste a Ticketmaster discover or search URL instead of configuring multiple fields.
• Category and search coverage - Works with category URLs, keyword search URLs, country-filtered URLs, and DMA or location-filtered discover URLs.
• Clean datasets - Removes null values, empty strings, and empty objects before saving each record.
• Built-in pagination - Keeps requesting result pages until it reaches your result cap or page cap.
• Residential proxy default - Uses Apify residential proxy settings in the default actor input for more reliable Ticketmaster API access.

Use Cases

Category Monitoring

Track a Ticketmaster category or minor classification over time. This is useful for niche genre pages, local concerts, or curated discover pages.

Keyword Research

Search Ticketmaster for artists, tours, venues, or topics by using a search URL. The actor returns matching event cards as structured records ready for analysis.

Local Market Coverage

Use a discover URL with a dma_id or country filter to monitor event availability for a specific market. This is useful for venue calendars, local dashboards, and regional alerting.

Input Parameters

Output Data

Each dataset item contains clean Ticketmaster event data.

Usage Examples

Minor Category URL

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

Search URL

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

Location-Filtered Discover URL

{
"startUrl":"https://www.ticketmaster.com/discover/concerts?dma_id=324&countryCode=US",
"results_wanted":100,
"max_pages":5,
"proxyConfiguration":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"]
}
}

Residential Proxy Request

{
"startUrl":"https://www.ticketmaster.com/discover/concerts?classificationId=KnvZfZ7vAve",
"results_wanted":50,
"max_pages":3,
"proxyConfiguration":{
"useApifyProxy":true,
"apifyProxyGroups":["RESIDENTIAL"]
}
}

Sample Output

{
"title":"Denim and Diamonds Tour w/ Sir Charles Jones, Jay Morris and Myia B",
"id":"1B0062B206496DE0",
"discoveryId":"G5viZblFk3pMO",
"url":"https://www.ticketmaster.com/...",
"startDate":"2025-06-30T00:00:00Z",
"onsaleDate":"2025-05-23T15:00:00Z",
"venueName":"Minglewood Hall",
"venueCity":"Memphis",
"venueState":"TN",
"venueCountryCode":"US",
"artistNames":[
"Sir Charles Jones"
],
"cancelled":true,
"soldOut":false
}

Tips For Best Results

Use Real Ticketmaster Result URLs

Paste a URL you already verified in the browser. The actor supports Ticketmaster discover and search result pages, not arbitrary event-detail pages.

Start Small, Then Scale

Use results_wanted: 20 while testing a new URL, then increase to 50 or 100 after the URL behaves as expected.

Use Proxy For Cloud Runs

Residential Apify Proxy improves stability on hosted runs, especially for larger result caps or repeated schedules.

Keep Residential Proxy Enabled

The default actor input already uses RESIDENTIAL. Keep that setting unless you have another proxy source that is already working for Ticketmaster.

Frequently Asked Questions

What URL types are supported?

Discover URLs, category URLs that carry classificationId, Ticketmaster keyword search URLs, and location-filtered discover URLs such as dma_id and country-based filters.

Does the actor parse HTML?

No. The actor uses Ticketmaster JSON event feeds directly and only maps the URL into the correct API request.

How do I send requests through residential proxy?

Pass proxyConfiguration.useApifyProxy: true with apifyProxyGroups: ["RESIDENTIAL"]. That is the default input shipped with the actor for both local testing and hosted runs.

Does pagination respect my input?

Yes. The actor starts from the URL page if one is present, then continues until it reaches results_wanted, max_pages, or the last available API page.

Why are some fields missing in some records?

Ticketmaster does not provide every field for every event. Empty values are removed before saving, so the dataset stays clean.

Support

Use the Apify Console issue and support channels for run-specific help, scheduling, integrations, and troubleshooting.

Legal Notice

Use this actor responsibly and make sure your data collection complies with the target site's terms and applicable laws.