Eventbrite Scraper - Events, Ticket Prices & Sold-Out Monitor

Search Eventbrite events by city, keyword, category, date range and free/paid, and get each event's date and time, venue and address, organizer, price range as shown on the event page and ticket status (on sale, sold out, sales ended, not yet on sale, cancelled, postponed). Turn on monitor mode and every run returns only new events and events whose price, ticket status, start time, venue or title changed since the last run.

Unofficial. Reads only public Eventbrite pages, without logging in. Organizers are returned by name and Eventbrite organizer page only - no personal contact details.

What makes it different

• Keyword matches are checked. Eventbrite's keyword search is a ranking, not a filter: a made-up word such as qwxyzplokqq still returns "10,000 events" in New York, and deep pages of a jazz search are mostly other music (measured 2026-09-24). Every row has keywordMatch; by default only events whose title, summary, category or tags contain every word of the keyword are returned, and a search stops after 3 list pages in a row without a match.
• Prices as the buyer sees them. Price range and sold-out come from the same ticket panel the event page uses ("From $23.07"), not from the search-engine markup in the page source, which can differ (for one boat party it said $28.39-$374.34 while the page said from $23.07).
• Filters are verified. Eventbrite reports which filters it applied to each list page. If a category, date, price or keyword filter you asked for was not applied, the list is not sold as a filtered list - you get a free row saying so.
• Monitor mode that does not invent news. A watch only judges a list it could read to the end. A search larger than what Eventbrite shows (980 events) returns a free row asking you to narrow it, instead of selling events that merely moved into view as "new".
• No results, no charge. Unknown places, empty searches, unreadable pages and verification pages come back as free rows that say why. The run start fee is charged only when something was actually returned or a watch check was completed.

Input

Field	Type	Description
locations	list	City, ST in the US (Austin, TX), City, Country elsewhere (London, United Kingdom, Berlin, Germany), online, or the part after /d/ in an Eventbrite search link (ny--new-york). Each location is searched with each keyword (up to 10 searches per run). Empty everything = example search New York, NY.
keywords	list	Optional search words (jazz, wine tasting, startup).
category	select	Optional: business, food-and-drink, health, music, auto-boat-and-air, charity-and-causes, community, family-and-education, fashion, film-and-media, hobbies, home-and-lifestyle, arts, government, spirituality, school-activities, science-and-tech, holiday, sports-and-fitness, travel-and-outdoor, other.
dateRange	select	Optional: today, tomorrow, this-weekend, this-week, next-week, this-month, next-month.
startDate / endDate	date	Optional custom range (YYYY-MM-DD). Use this or dateRange, not both.
price	select	Optional: free or paid.
maxResultsPerSearch	number	Events per search, 1-980. Empty = 20.
includeDetails	checkbox	On (default): open each event page for price range, ticket status, organizer, UTC times, full address. Off: faster, search list only.
onlyKeywordMatches	checkbox	On (default): return only events matching every word of the keyword.
eventUrls	list	Optional Eventbrite event links or IDs (up to 50) to check directly.
onlyNew	checkbox	Monitor mode: only new and changed events.
watchName	text	Optional name to keep separate monitor memories (letters, digits, ., -, _).
resetMonitoringState	checkbox	Forget this watch's memory and start again.

Examples

Jazz this weekend in New York, free only:

{ "locations": ["New York, NY"], "keywords": ["jazz"], "dateRange": "this-weekend", "price": "free" }

Watch tech events in San Francisco and get only new ones and price/sold-out changes (schedule it daily):

{ "locations": ["San Francisco, CA"], "category": "science-and-tech", "onlyNew": true, "watchName": "sf-tech" }

Check the price and status of specific events:

{ "eventUrls": ["https://www.eventbrite.com/e/16th-annual-nyc-pizza-run-tickets-1995478167917"] }

Output

One row per event (status: "ok"), for example:

{
  "status": "ok",
  "changeType": null,
  "name": "16th Annual NYC Pizza Run",
  "eventId": "1995478167917",
  "eventUrl": "https://www.eventbrite.com/e/16th-annual-nyc-pizza-run-tickets-1995478167917",
  "startDate": "2026-09-27", "startTime": "11:00", "startUtc": "2026-09-27T15:00:00Z", "timezone": "America/New_York",
  "ticketStatus": "on-sale", "isSoldOut": false, "isFree": false,
  "priceMin": 80.81, "priceMax": 92.55, "currency": "USD", "ticketTypes": 2,
  "venueName": "Fort Greene Park", "venueAddress": "320 Myrtle Ave, Brooklyn, NY 11205", "city": "Brooklyn", "region": "NY", "country": "US",
  "organizerName": "NYC Pizza Run", "organizerUrl": "https://www.eventbrite.com/o/nyc-pizza-run-109137132381",
  "category": "Food & Drink", "format": "Race",
  "detailsRead": true, "keywordMatch": null
}

Main fields: name, eventId, eventUrl, summary, startDate, startTime, endDate, endTime, startUtc, endUtc, timezone, isOnline, ticketStatus (on-sale, sold-out, sales-ended, not-yet-on-sale, unavailable, cancelled, postponed, started, ended), isSoldOut, isFree, priceMin, priceMax, currency, ticketTypes, waitlistAvailable, salesStatus, salesMessage, fewTicketsLeft, goingFast, salesEndSoon, category, subcategory, format, tags, venueName, venueAddress, city, region, country, postalCode, latitude, longitude, organizerId, organizerName, organizerUrl, organizerVerified, organizerEventCount, isSeries, ticketsBy, hasExternalTickets, publishedAt, imageUrl, detailsRead, keywordMatch, positionInSearch, eventsInSearch, eventsInSearchIsCapped, searchLocation, searchKeyword, searchCategory, searchDateRange, searchPrice, searchUrl, watchName, checkedAt.

Monitor mode adds changeType (first-check, new, changed), changes (for example ticket status on-sale -> sold-out, price 80.81-92.55 USD -> 99.5-120.25 USD) and previousTicketStatus, previousPriceMin, previousPriceMax, previousStartUtc.

priceMin / priceMax are null (not 0) when Eventbrite no longer shows prices, for example after sales ended or for a cancelled event. eventsInSearch is the number Eventbrite reports for the search (null when it only says "10,000+"); for keyword searches that number includes Eventbrite's filler events.

Free rows (not charged) have another status and a note: no-results, no-keyword-matches, not-found, no-changes, too-broad-to-watch, not-checked, more-not-returned, incomplete, unreadable, blocked, budget-reached, bad-input.

How monitor mode works

1. The first run reads the whole list of each search, returns up to maxResultsPerSearch events (first-check) and remembers the whole list as the starting point.
2. Later runs read the whole list again and return events that were not on it before (new). Each run also re-opens up to 30 remembered events - first those whose list entry changed or that left the list, then the ones checked longest ago - and returns those whose price, ticket status, start time, venue or title changed (changed). An event whose page disappeared is returned once with ticketStatus: "removed".
3. Events that could not be returned (charge limit, a page that could not be opened) are not remembered, so a later run returns them.
4. new means new on this search's list. With a rolling date range (for example this-weekend), events also enter the list as the dates move; publishedAt tells a newly published event from one that just came into the date range.

Pricing

Pay per event: one fee per run start (charged when the first event row is returned, or when a watch has read and checked its whole list, even if nothing changed) plus one fee per event row. Free rows are never charged. If the maximum charge you set for a run has no room for the start fee plus one row, nothing is requested and nothing is charged.

Measured (2026-09-24, Apify, 256 MB)

• Default input (20 New York events with prices): 41 requests (list page, then each event page and its ticket panel), 35-50 s.
• Checked against the event pages in a browser (title, venue, organizer, date, "From" price, sold-out / cancelled wording, where the page shows them): Chicago comedy 29 of 29, New York default 24 of 24, London free events 24 of 24, specific links incl. sold-out and cancelled 21 of 21.
• Monitor mode, 32-event list: first check 7-17 s, next check (whole list plus 30 remembered event pages) 36-61 s.
• From Apify's own connection 50 of 50 Eventbrite pages loaded; Apify datacenter proxies got Eventbrite's human-verification page 40 of 40 times, so they are not used. When the plain connection is refused, the Actor asks again through a residential connection.

Limits

• Eventbrite shows at most 49 pages (980 events) for one search. Narrow big searches with a category, dates, free/paid or a smaller area. A keyword does not narrow the list (Eventbrite only reorders it), so it does not help a watch.
• Keyword matching looks at title, summary, category and tags - not the full description.
• When Eventbrite shows a human-verification (CAPTCHA) page, this Actor stops and says so. It does not solve or bypass it; events already returned are kept and charged, nothing else is.
• Two runs of the same watch at the same moment can both return the same new event. Avoid overlapping schedules for the same search and watch name.
• Private and password-protected events are not visible.

Support

Found a problem or need another field? Open an issue in the Issues tab.