Eventbrite Events Scraper (city, date filters, venue geocodes)

Scrape Eventbrite's discovery search by city, keyword, category and date window — or paste a search URL you already built on the site — and get one flat row per event, venue coordinates included. No login and no Eventbrite API key.

What you get (example output)

One row per event. Real values from the example dataset of this actor:

Field	Example value
name	Magnitude 2026 - The Saturday Night Main Event of Folsom Street Fair™
startDate / startTime / endDate / endTime / timezone	2026-09-26 / 21:00 / 2026-09-27 / 04:00 / America/Los_Angeles
venueName / address	SVN West / 10 Van Ness Avenue, San Francisco, CA 94103
city / region / postalCode / country	San Francisco / CA / 94103 / US
lat / lon	37.7746775 / -122.4195802
isOnline / isPromoted	false / false
tags / categories	["EDM / Electronic", "Music", "Party or Social Gathering", "Folsom"] / ["Music"]
publishedAt	2025-10-27T06:30:08Z
ticketsUrl	https://www.eventbrite.com/checkout-external?eid=1894668557659

Also on every row: eventId, url, summary, isFree, isCancelled, organizerId, organizerName, priceMin, priceMax, currency, imageUrl, seriesId, query, location, page, rank, scrapedAt.

Use cases

• City guides and event aggregators: pull this weekend's events for a city with coordinates ready for a map, and refresh them on a schedule.
• Venue and competitor tracking: watch which events an organizer or a venue publishes, and get notified when a new one appears or a date changes.
• Marketing and sales calendars: build a list of conferences or meetups in a category and city window, with the ticket link on the row.

How it works

1. Each searches entry becomes an Eventbrite discovery URL (location slug plus keyword, category, date window and the free-only toggle); searchUrls are used as-is with their filters.
2. Result pages are read through a US residential proxy with a browser fingerprint — Eventbrite verifies non-residential visitors — and the embedded search payload is parsed, 20 events per page, up to maxPages.
3. Events are deduplicated on the Eventbrite event id, so overlapping searches are never charged twice.
4. In monitor mode the run compares against the previous run of the same task and returns only new or changed events, optionally posting a summary to a webhook or Telegram chat.

Input

Field	Meaning	Default
searches	[{"location": "ca--san-francisco", "keyword": "jazz", "category": "music", "dates": "this-weekend", "freeOnly": false}]	[{"location": "ca--san-francisco"}]
searchUrls	Any eventbrite.com/d/... search URL, filters preserved	empty
maxPages	Result pages per search (20 events per page)	3
maxItems	Stop after this many events	20
mode	scrape or monitor (only new/changed since the previous run)	scrape
monitorStateId	State key for monitor mode outside a saved task	empty
webhookUrl	HTTPS endpoint for the monitor-mode change summary	empty
telegramBotToken / telegramChatId	Send the monitor-mode summary to Telegram	empty

Pricing

Event	Price
result	$0.001 per event ($1 per 1,000)
monitor-check	$0.005 per monitor run
change	$0.001 per new/changed event

Charged only for events actually pushed. Eventbrite verifies non-residential visitors, so the actor runs through residential proxy; Apify bills that traffic on top (about 0.7 MB per page of 20).

Why this actor

• Venue address already split into city, region, postalCode, country plus lat / lon, so events land on a map without a geocoding step.
• Start and end are separate date, time and timezone fields instead of one localized string.
• Date windows Eventbrite itself understands (today, this-weekend, next-month) rather than client-side filtering after the fact.
• No login and no Eventbrite API key, so there is no OAuth app to maintain and no per-token quota.
• You pay per pushed row; an empty or blocked run costs nothing beyond platform usage, and RUN_SUMMARY records the reason (no_matches, blocked, rate_limited, invalid_input, upstream_error).
• Monitor mode with webhook and Telegram alerts on new and changed events.

Limits

• Event detail pages are not opened: full description and attendee counts are not included.
• Price range is present only when Eventbrite exposes ticket availability in search; on many rows priceMin, priceMax, currency and isFree are null.
• organizerName is frequently null in search results — organizerId is always there and identifies the organizer.
• location must be Eventbrite's own slug (ca--san-francisco, united-kingdom--london, online); a plain city name will not resolve.
• Search results are the discovery feed, not an archive: past events are not returned.

FAQ

Where do I find the location slug for my city? Open the city on Eventbrite and copy the segment from the URL: eventbrite.com/d/ca--san-francisco/... → ca--san-francisco. Use online for online-only events. You can also skip slugs entirely and paste the whole search URL into searchUrls.

Can I scrape Eventbrite events for this weekend only? Yes — set dates to this-weekend inside a searches entry (other accepted values: today, tomorrow, this-week, next-week, this-month, next-month).

Do I need the Eventbrite API? No. This actor reads public discovery pages through a residential proxy; you provide no API key and no account.

Changelog

• 0.1: initial release.

---

If this actor is useful, a review on its Apify Store page helps other people find it. For bugs or a field you need, open a ticket on the Issues tab of this actor.