Concert Archives Scraper at a glance
Concert Archives Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes kind, recordid, concertid, url and slug, 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
- Other, Developer Tools, Travel
- Pricing
- $2.00 per 1,000 results (Free plan), from $1.20 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 19 options
Scrape Concert Archives concert and tour history: past and upcoming dates, venues, cities, line-ups, tours, genres, tickets and setlists. Search by band, venue or location, or paste links. Incremental monitoring with NEW, UPDATED, REAPPEARED, EXPIRED, resume and MCP export.
What Concert Archives Scraper can do
- Three ways to find a history. Search by band, venue or city name and the top matching page is walked automatically, or paste any Concert Archives link (band, venue, location, a single concert, a search link or an advanced search link) and skip the lookup entirely.
- Full history, not just upcoming shows. A walk follows a band, venue or location's concert table forward to its natural end, from decades-old shows to next month's dates.
- Concert-level depth on demand. Fetch each concert's own page for the full billed line-up with genres, the description, the poster image, the ticket seller and link, the event status and the community line-up, attendee and photo counts, only when you switch it on.
- Setlists included. Pull the songs actually played, per band, for concerts that have a setlist on the site.
- Filters that tell you the truth. Upcoming/past and Year filters apply wherever the site actually supports them, and a run says so out loud in the log rather than quietly handing back an unfiltered result labelled as filtered.
- Built for monitoring. Incremental mode returns only new, changed and reappeared concerts on repeat runs, and a blocked run fails loudly instead of returning an empty dataset.
Choose what to collect
These inputs let you configure Concert Archives Scraper - Concerts, Tours, Venues & Setlists. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | Search looks up a band, venue or location by keyword and returns its concert history. URL mode reads the specific Concert Archives pages you paste. |
querystring | Search mode: a keyword, for example a band name, a venue name or a city. Used together with Search type below. |
searchTypestring | Search mode: what the keyword should match. Bands returns that band's concert and tour history, Venues returns everything played at that venue, Locations returns everything played in that city or region. |
urlsarray | URL mode: pages to read, one per line. Band, venue and location pages are walked forward through their whole history. A single concert link is read as one record. A search link or an advanced concert-search link is also accepted. Multi-value supported. |
dateFilterstring | Narrow the concert history to only upcoming or only past concerts. Applies to band, venue and location pages in both modes. Leave on All to return the complete history. |
yearinteger | Return only concerts from this year, for example 2024. Leave at 0 for every year. Band and venue pages support this; location pages do not, and a run that asks for it on a location says so in the log and returns every year instead. |
fetchDetailsboolean | Read each concert's own page to add the full billed line-up with genres, the description, the poster image, the ticket seller and link, the event status and the community line-up, attendee and photo counts. Adds a per-concert surcharge (see the section caption above). |
Show 12 more inputs
| Input | What it controls |
|---|---|
includeSetlistsboolean | Also return the songs played, per band, for concerts that have a setlist on the site. Needs Fetch concert details to be on. This adds one extra read per concert, so runs take longer; it does not add a second surcharge. |
maxItemsinteger | Stop after this many concerts (0 = no limit; the run then stops when the history runs out). |
maxPagesinteger | Upper bound on how many pages each band, venue, location or link is walked through (0 = the built-in ceiling of 500 pages per scope, which is also the most any value can walk). Max items is the cap that normally stops a run early. |
resumeFromRunIdstring | Paste a previous run ID or dataset ID to continue a large pull without returning concerts already collected there. |
incrementalModeboolean | Turn this on for daily or recurring monitoring. The first run returns every matching concert as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED concerts. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately for each search, link and filter setup; use State key to name or deliberately share a monitoring campaign. |
stateKeystring | 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, link and filter settings. |
emitUnchangedboolean | Off by default. Turn on to also return concerts that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have. |
emitExpiredboolean | Off by default. Turn on to also return concerts that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked history. |
ignoreFieldsForChangesarray | Field names that should NOT make a concert count as UPDATED when only they change, for example ticketUrl. The community counters (attendeeCount, photoCount, setlistCount) are already left out by default. The fields stay in every row you receive; they are just not compared between runs. Use a dot for nested fields. Changing this list never causes a one-time wave of UPDATED rows. |
mcpConnectorsarray | 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. |
notionParentPageUrlstring | URL or id of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | 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.
kindkindrecordIdrecordIdconcertIdconcertIdurlurlslugslugtitletitlestartDatestartDateendDateendDatedateTextdateTextisUpcomingisUpcomingeventStatuseventStatustourNametourNameShow 28 more fields
headlinerheadlinerlineuplineupperformersperformersartistGenresartistGenresvenueNamevenueNamevenueUrlvenueUrlvenueAddressvenueAddressvenueCityvenueCityvenueRegionvenueRegionvenueCountryvenueCountrylocationTextlocationTextlocationUrllocationUrldescriptiondescriptionimageUrlimageUrlticketUrlticketUrlticketVendorticketVendorhasSetlisthasSetlisthasPhotoshasPhotoslabelslabelslineupCountlineupCountattendeeCountattendeeCountphotoCountphotoCountsetlistCountsetlistCountsetlistssetlistschangeTypechangeTypechangedFieldschangedFieldsfirstSeenAtfirstSeenAtlastSeenAtlastSeenAtExample output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"kind": "concert",
"recordId": "00000000",
"concertId": "00000000",
"url": "https://www.concertarchives.org/concerts/sample-band--00000000",
"slug": "sample-band--00000000",
"title": "Sample Band",
"startDate": "2027-01-15",
"endDate": "2027-01-15",
"dateText": "Jan 15, 2027",
"isUpcoming": true,
"eventStatus": "scheduled",
"tourName": "Sample World Tour",
"headliner": "Sample Band",
"lineup": [
"Sample Band",
"Sample Support"
],
"performers": [
{
"name": "Sample Band",
"url": "https://www.concertarchives.org/bands/sample-band",
"genre": "rock",
"imageUrl": null
}
],
"artistGenres": [
"rock",
"alternative"
],
"venueName": "Sample Arena",
"venueUrl": "https://www.concertarchives.org/venues/sample-arena",
"venueAddress": "Sample City, Sample State, Sample Country",
"venueCity": "Sample City",
"venueRegion": "Sample State",
"venueCountry": "Sample Country",
"locationText": "Sample City, Sample Country",
"locationUrl": "https://www.concertarchives.org/locations/sample-city",
"description": "A sample tour stop.",
"imageUrl": "https://img.example/sample.jpg",
"ticketUrl": "https://tickets.example/sample",
"ticketVendor": "Sample Tickets",
"hasSetlist": true,
"hasPhotos": true,
"labels": [
"Upcoming Concert",
"Has Setlist"
],
"lineupCount": 2,
"attendeeCount": 42,
"photoCount": 12,
"setlists": [
{
"artist": "Sample Band",
"songs": [
"Sample Song One",
"Sample Song Two"
],
"setlistUrl": null
}
],
"setlistCount": 1,
"changeType": "NEW",
"changedFields": [],
"firstSeenAt": "2026-09-29T00:00:00+00:00",
"lastSeenAt": "2026-09-29T00:00:00+00:00"
}Ways to use this data
- Fans and ticket buyers: check exactly when a band last played your city, and where the tour goes next.
- Promoters and venue bookers: review a venue's full booking history and genre mix before pitching a show.
- Music journalists and researchers: build tour timelines, genre trends and lineup histories for a band or a scene.
- Setlist and stats trackers: collect the songs played per show to spot patterns across a tour.
- Archivists and fan sites: back up a band's or a venue's concert record outside the site itself.
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 Concert Archives Scraper return?
The documented output for Concert Archives Scraper includes kind, recordid, concertid, url, slug, title, startdate and enddate. Availability of each field depends on the source page and the selected mode.
How much does Concert Archives 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 concerts on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new, updated and reappeared concerts, and unchanged ones are not billed unless you turn on Emit unchanged.
What is the difference between Resume and Incremental mode?
They solve different problems. Resume (resumeFromRunId) continues ONE specific interrupted pull so a large history does not need to be collected twice. Incremental mode is for running the SAME search or link set again and again (for example weekly) and getting only what changed since last time. Use Resume for a one-off retry, Incremental mode for ongoing monitoring.
Why did my run fail instead of returning an empty dataset?
If nothing could be read at all, the run fails with a clear message so "no concerts found" is never confused with "nothing could be read". Run it again in a few minutes. In search mode, a keyword that matches no band, venue or location also stops with a message telling you so: check the spelling or switch Search type. A band, venue or location that genuinely has no concerts for your filters still succeeds with an empty result.
Does this collect any personal data from concertgoers?
No. Concerts on Concert Archives carry attendee lists, comments and user-uploaded photos tied to real accounts. This actor returns only the counts of those (attendeeCount, photoCount, setlistCount) and never the names, usernames or comment text behind them.
