Bandsintown Scraper - Concerts, Artists & Venues
Pricing
from $1.00 / 1,000 event records
Scrape Bandsintown concert and festival dates: artist tour calendars, venue profiles, ticket links, lineups, RSVP counts and genres. Search by artist name or paste artist, venue or event links. MCP export included.
Search looks up upcoming concerts by artist name. URL mode reads specific Bandsintown artist, venue or event links you paste.
Search mode: one artist name per line, exactly as it appears on Bandsintown.
Search mode: which of the artist's dates to return.
URL mode: Bandsintown pages to read, one per line. Artist links (/a/...) and venue links (/v/...) are walked for their upcoming shows; a single event link (/e/...) is read as one record. Multi-value supported.
Adds the artist's and venue's own profile pages: follower/tracker counts, the venue's phone number and verified/premium status, and each artist's or venue's full upcoming and past show history. In Search mode this also reads the event's own page for timezone, genre, RSVP count and artist bio (all otherwise blank). In URL mode those four are already included for free from the pasted link itself. Adds a per-event surcharge when used (see the section caption below). SLOW: each detail page is a real browser load through this site's anti-bot check, roughly 10-15 seconds per event (measured live) even after caching each artist's and venue's page across its own events - a 20-event run typically takes 4-5 minutes. Turn this OFF for a fast, near-instant run that reads only the free public event-listing API, with fewer fields.
Stop after this many events. This is the run's only default cap (default 20). Set to 0 for no limit; the run then stops only when events run out.
Optional upper bound on how many pages each artist or venue calendar is walked through. Defaults to unlimited (0 = no limit) and does NOT cap the run by itself - it always defers to Max items, which is the only cap enforced by default. Set this only if you need a second, stricter limit per artist/venue.
Paste a previous run ID or dataset ID to continue a large calendar pull without returning or charging for events already collected there. Use this after an interrupted run. For recurring daily monitoring of the same artists or venues, use Incremental mode below instead.
Turn this on for daily or recurring monitoring. The first run returns every matching event as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED events, which is how a rescheduled date, a sold-out flip or a newly announced show is spotted. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately for each mode, artist list, link set, date range and detail setting; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.
Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the mode, artists, links, date range and detail setting, so different scopes never mix state with each other.
Off by default. Turn on to also return events that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you want the full snapshot every run.
Off by default. Turn on to also return events that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked scope, so never when Max items capped it or when Resume was used. This returns, and bills, extra synthetic rows, so leave it off unless you need cancellation tracking.
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.
URL or id of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.
Cap on items written to each connector per run. Does not affect the dataset.
