Pollstar Scraper at a glance
Pollstar Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes kind, recordid, eventid, url and title, 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.50 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.50 on paid plans
- Output
- Documented below · JSON, CSV, Excel
- Inputs
- 22 options
Scrape Pollstar upcoming concerts and tour dates: play date, venue with full address and coordinates, artist line-up, genres, ticket links and market. Search artists, venues or cities, or paste Pollstar links. Newly-announced filter, incremental monitoring, resume and MCP export.
What Pollstar Scraper can do
- One schema across every surface. The same event record shape covers artist tour schedules, venue calendars and whole-market calendars, so you never write three different parsers.
- Rich venue data on every row. Venue name, type, street, city, state, postal code, country, coordinates, market, and the venue's own published phone and website come with each event, with no second request per event.
- Full line-up, not just the headliner. Every billed act with its sequence, genres and headline flag, plus a flat support-act list.
- Newly announced watch. "Newly announced only" narrows a calendar to the dates Pollstar announced in the last few days, which is the cheapest possible daily tour-announcement feed.
- Metro widening. "Include nearby cities" turns a single-city search into a whole surrounding market in one request.
- Artist profile enrichment, on request. Optionally add the headline artist's photo, official website, activity status and a touring trivia line; each artist is read once per run and reused across all of their dates.
Choose what to collect
These inputs let you configure Pollstar Scraper - Concert Tours, Venues & Events. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | Search resolves a keyword to a Pollstar artist, venue or city and returns its upcoming events. URL mode reads the specific Pollstar pages you paste. |
querystring | Search mode: the name to look up, for example an artist, a venue or a city. The closest Pollstar match is used and its name is logged. |
searchTypestring | Search mode: what the keyword should resolve to. Artists returns a tour schedule, Venues returns a venue calendar, Cities returns everything booked in a market. |
urlsarray | URL mode: Pollstar pages to read, one per line. Artist, venue, city and company pages are paged forward; a single event page is read as one record. Every link must end in the numeric Pollstar id. Alternate spellings of the same page (bare host, no slug, venue vs company with the same id) are read once. Multi-value supported. |
fromDatestring | First play date to include. Leave empty for today. Pollstar licenses historical data, so a date before today is moved forward to today and the run says so in its log. |
toDatestring | Last play date to include. Leave empty for one year after the start date. |
newOnlyboolean | Return only dates Pollstar announced in the last few days. Ideal for a daily tour-announcement watch. |
Show 15 more inputs
| Input | What it controls |
|---|---|
includeNearbyCitiesboolean | Widen a city search to the surrounding metro area, adding events at venues in neighbouring cities. Ignored for artist, venue and event scopes. |
sortOrderstring | Read the calendar from the nearest date forward, or from the furthest date backward. Pollstar only orders this feed by play date, so that is the only ordering offered. |
sortBystring | Order the calendar by play date (default) or group it by venue name. Combine with the date order above. Pollstar applies only these two orderings. |
fetchArtistProfilesboolean | Read each headline artist's Pollstar profile to add their photo, official website, activity status and a touring trivia line. Adds a per-event surcharge (see the section caption below); each artist is read once per run and reused across their other dates. |
maxItemsinteger | Stop after this many events (0 = no limit; the run then stops when the calendar runs out). |
maxPagesinteger | Upper bound on how many pages each artist, venue, city or link is walked through. Defaults wide open so Max items is the only cap that stops a run early. |
resumeFromRunIdstring | Paste a previous run ID or dataset ID to continue a large pull without returning events already collected there. |
incrementalModeboolean | 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. An event counts as UPDATED when any returned field changes (date, time, venue, artists, tickets and ticket vendors, genres, notes, artist profile fields); list order is ignored. Never compared: announcedHoursAgo (a counter that rises every run) and any field you list in Ignore fields. 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 events 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 events that were present in a previous run but are no longer listed, marked EXPIRED. Only produced once a run has fully scanned the tracked calendar. |
ignoreFieldsForChangesarray | Output field names that should NOT make an event count as UPDATED, even when they change. Matches a field name at any nesting depth (for example genres inside artists). Ignored fields are still returned in the output. Built in: announcedHoursAgo (a counter that rises every run) is always ignored. |
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.
kindkindrecordIdrecordIdeventIdeventIdurlurltitletitleplayDateplayDateplayTimeplayTimeisFestivalisFestivalhasBoxOfficeReporthasBoxOfficeReportannouncedHoursAgoannouncedHoursAgonotenoteheadlineArtistheadlineArtistShow 38 more fields
headlineArtistIdheadlineArtistIdheadlineArtistUrlheadlineArtistUrlheadlineArtistTypeheadlineArtistTypegenresgenressupportActssupportActsartistsartistsvenueIdvenueIdvenueNamevenueNamevenueUrlvenueUrlvenueTypesvenueTypesvenueMarketvenueMarketvenueStreetvenueStreetvenueCityvenueCityvenueStatevenueStatevenueStateNamevenueStateNamevenuePostalCodevenuePostalCodevenueCountryvenueCountryvenueLatitudevenueLatitudevenueLongitudevenueLongitudevenuePhonevenuePhonevenueEmailvenueEmailvenueWebsitevenueWebsiteticketsticketsticketUrlticketUrlticketVendorsticketVendorsheadlineArtistImageUrlheadlineArtistImageUrlheadlineArtistWebsiteheadlineArtistWebsiteheadlineArtistIsActiveheadlineArtistIsActiveheadlineArtistSortNameheadlineArtistSortNameheadlineArtistNoteheadlineArtistNoteheadlineArtistTriviaheadlineArtistTriviascopeKindscopeKindscopeIdscopeIdscopeNamescopeNamechangeTypechangeTypechangedFieldschangedFieldsfirstSeenAtfirstSeenAtlastSeenAtlastSeenAtExample output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"kind": "event",
"recordId": "00000000",
"eventId": "00000000",
"url": "https://www.pollstar.com/events/sample-artist-at-sample-arena-00000000",
"title": "Sample Artist at Sample Arena",
"playDate": "2027-06-18T00:00:00",
"playTime": "8:00 PM",
"isFestival": false,
"hasBoxOfficeReport": false,
"announcedHoursAgo": 36,
"note": null,
"headlineArtist": "Sample Artist",
"headlineArtistId": "00000000",
"headlineArtistUrl": "https://www.pollstar.com/artists/sample-artist-00000000",
"headlineArtistType": "Band",
"genres": [
"Pop / Rock"
],
"supportActs": [
"Sample Support Act"
],
"artists": [
{
"artistId": "00000000",
"name": "Sample Artist",
"url": "https://www.pollstar.com/artists/sample-artist-00000000",
"isHeadline": true,
"genres": [
"Pop / Rock"
],
"artistType": "Band",
"sequence": 1
}
],
"venueId": "00000000",
"venueName": "Sample Arena",
"venueUrl": "https://www.pollstar.com/companies/sample-arena-00000000",
"venueTypes": [
"Arena"
],
"venueMarket": "Sample City, ST",
"venueStreet": "1 Sample Road",
"venueCity": "Sample City",
"venueState": "ST",
"venueStateName": "Sample State",
"venuePostalCode": "00000",
"venueCountry": "United States",
"venueLatitude": 36.1,
"venueLongitude": -115.1,
"venuePhone": "(000) 000 0000",
"venueEmail": "bookings@sample-arena.example",
"venueWebsite": "www.sample-arena.example",
"tickets": [
{
"vendor": "Sample Ticket Vendor",
"url": "https://tickets.example/sample",
"doorTime": "8:00 PM"
}
],
"ticketUrl": "https://tickets.example/sample",
"ticketVendors": [
"Sample Ticket Vendor"
],
"headlineArtistImageUrl": "https://static.example/artist-photos/sample.jpg",
"headlineArtistWebsite": "www.sample-artist.example",
"headlineArtistIsActive": true,
"headlineArtistSortName": "SAMPLE ARTIST",
"headlineArtistNote": null,
"headlineArtistTrivia": "Sample Artist has headlined 70% of performances since 2006",
"scopeKind": "city",
"scopeId": "00000",
"scopeName": "Sample City"
}Ways to use this data
- Booking agents and promoters: track a market's full calendar to spot open dates and see what else is already booked nearby.
- Music journalists and tour-news blogs: watch newly announced dates for a city or artist to publish first.
- Ticket resale and pricing tools: feed upcoming event, venue and ticket-link details into a pricing or alerting system.
- Artist managers and agencies: monitor a whole roster's tour schedule and venue contact details in one feed.
- Venue and market analysts: build a picture of everything booked in a metro area, including nearby cities, without visiting each venue page by hand.
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 Pollstar Scraper return?
The documented output for Pollstar Scraper includes kind, recordid, eventid, url, title, playdate, playtime and isfestival. Availability of each field depends on the source page and the selected mode.
How much does Pollstar Scraper cost?
It costs $2.00 per 1,000 results on the Apify Free plan and from $1.50 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 watch a market or artist for newly announced dates on a schedule?
Yes. Schedule the actor from the Schedules tab, turn on Newly announced only and Incremental changes for scheduled runs. Each run then returns only NEW, UPDATED and REAPPEARED dates; unchanged ones are skipped and not billed unless you also turn on Emit unchanged.
Why did my date window get moved forward, or my run fail instead of returning an empty dataset?
Pollstar licenses dates before today; this actor moves a past start date forward to today and logs the change. A window that ends entirely in the past is refused, and the run fails with a message naming the licence boundary rather than reporting an empty calendar, so "nothing booked" is never confused with "the request itself was refused". If only part of a run was refused, you still get what could be read, and the run's status message names how much was blocked.
Why didn't an incremental run report any EXPIRED dates I expected?
EXPIRED detection only fires after a run that fully scanned its tracked scope with nothing capped, resumed or refused. In url mode with several links, Max items is split per link, so one especially active link using up its own share before its last page is enough to skip EXPIRED for the whole run that cycle, even though the other links finished naturally; that cycle's tombstoning is simply deferred. The opposite edge case also exists: if a link's share runs out partway through its final page while the run stays under Max items overall, the unread rest of that page can be reported as EXPIRED and then return as REAPPEARED later (see "Resume and recurring updates" above). For reliable EXPIRED rows in url mode with several links, set Max items to 0 or run each link on its own.
What is the difference between Resume and Incremental mode?
Resume continues ONE specific interrupted run so you don't pay to re-collect what it already gathered. Incremental mode is for running the same search or links again and again (for example daily) and getting only what is new or changed since last time. They are independent and can be combined.
