Concert Archives Scraper - Concerts & Tour History

Scrape concert and tour history from Concert Archives, the fan-built live-music database. Look up a band, a venue or a city and get its complete concert history: past dates going back decades, upcoming shows, the billed line-up, tours, venues, locations, ticket links and the songs actually played.

Built for the questions a ticketing feed cannot answer. Where has this band played, and when were they last in my city? What has this venue hosted? What did they play on the night?

What you get

One row per concert:

Group	Fields
Identity	kind, recordId, concertId, url, slug, title
When	startDate, endDate, dateText, isUpcoming, eventStatus
Who	headliner, lineup, performers (name, page link, genre, image), artistGenres
Where	venueName, venueUrl, venueAddress, venueCity, venueRegion, venueCountry, locationText, locationUrl
Context	tourName, description, imageUrl, labels, hasSetlist, hasPhotos
Tickets	ticketUrl, ticketVendor
Community	lineupCount, attendeeCount, photoCount, setlistCount
Setlists	setlists: per band, the songs in order, plus a link to the setlist page
Monitoring	changeType, changedFields, firstSeenAt, lastSeenAt

Sample row (fictional values)

{
  "kind": "concert",
  "recordId": "00000000",
  "concertId": "00000000",
  "url": "https://www.concertarchives.org/concerts/sample-band--00000000",
  "title": "Sample Band",
  "startDate": "2027-01-15",
  "isUpcoming": true,
  "tourName": "Sample World Tour",
  "headliner": "Sample Band",
  "lineup": ["Sample Band", "Sample Support"],
  "venueName": "Sample Arena",
  "venueUrl": "https://www.concertarchives.org/venues/sample-arena",
  "venueCity": "Sample City",
  "venueRegion": "Sample State",
  "venueCountry": "Sample Country",
  "ticketVendor": "Sample Tickets",
  "attendeeCount": 42,
  "setlistCount": 1,
  "changeType": "NEW"
}

How to use it

Search mode (default)

Type a keyword and pick what it 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.

The keyword is matched against the site's own index and the top result is used, so red rocks finds the amphitheatre without you looking up its page first.

URL mode

Paste links, 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 works too.

Filters (both modes)

• Upcoming or past concerts narrows the history to only upcoming or only past dates. Works on band, venue and location pages.
• Year returns only concerts from one year. Works on band and venue pages. Location pages do not support it: the site accepts the setting there and ignores it, so rather than hand you an unfiltered result that looks filtered, the run says so in the log and returns every year. Use a band or venue page when you need a single year.

Depth and cost

• Max items defaults to 20. Set it to 0 for the whole history, which for a long-running band can be thousands of concerts across dozens of pages.
• Max pages per scope defaults to 0, meaning no page limit, so Max items is the only cap that stops a run early.
• Fetch concert details (on by default) reads 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 counts. It adds a per-concert surcharge, so turn it off for a fast, cheap list-only pull.
• Include setlists (off by default) adds the songs played, per band, for concerts that have a setlist. It costs one extra read per concert, so runs take longer. It does not add a second surcharge.

Recurring monitoring

Turn on Incremental changes for scheduled runs and run this on a schedule. The first run returns everything as NEW. Later runs return only what moved:

• NEW first time this concert was seen
• UPDATED something changed; changedFields names what
• REAPPEARED back after having gone missing
• UNCHANGED returned only when you turn on Emit unchanged
• EXPIRED returned only when you turn on Emit expired, and only after a run that scanned the whole tracked history without hitting a limit or an error

State is kept separately for each search, link and filter setup, so a run filtered to one year never tombstones the concerts that filter excludes. Use State key to name a campaign, or to deliberately share state between two differently configured runs.

Resume from a previous run is a different thing: paste a run or dataset ID to continue ONE interrupted pull without collecting the same concerts twice.

Send results into your apps (MCP connectors)

Optionally pipe the results straight into the tools you already use, over Model Context Protocol. Authorize a connector under Apify, Settings, API & Integrations, then set:

• mcpConnectors the connector IDs to send to, one per line
• notionParentPageUrl the Notion page to create item pages under, for the Notion connector
• maxNotifyListings how many items to send per connector per run

Notion gets a page per concert. Other connectors get a best-effort write or a digest. This never changes the dataset, and a connector problem never fails the scrape.

What this actor deliberately does not collect

Concert Archives is a community site: concerts carry attendee lists, comments and user-uploaded photos, all attached to real people's accounts. This actor collects the counts of those (attendeeCount, photoCount) and never the names, usernames or comment text behind them.

Notes

• No account and no API key is needed.
• The default proxy setting works on every Apify plan.
• Dates come from an archive maintained by fans. Very old entries can be approximate, and startDate is left empty rather than guessed when the site does not publish a parseable date.