Eventbrite Scraper - Events, Tickets & Organizers

Pricing

Rating

Developer

Actor stats

Categories

Share

Pull structured event data from Eventbrite by city, keyword, category, or by pasting URLs. For every event you get the name, exact start/end times, the venue with full address and coordinates, whether it is online or in person, the organizer, the Eventbrite category, the ticket price range with a free/paid flag, availability, the cover image, and the description.

No headless browser. Eventbrite's search and browse pages embed their full result set as inline JSON, and each event page exposes structured schema.org data, so the actor reads those directly. Requests use a real Chrome TLS fingerprint (via curl_cffi), which keeps it fast and cheap, and datacenter proxies are enough.

What you can scrape

• All upcoming events in any city Eventbrite covers, or online-only events.
• Keyword searches (e.g. jazz, startup, yoga) scoped to a location.
• A whole Eventbrite category (Music, Business, Food & Drink, and 18 more).
• Any Eventbrite search, browse, or individual event URL you paste in.

Input

Provide at least one of location, query, category, or startUrls. Pagination is automatic - the actor walks the result pages until the location runs out of events or maxItems is reached.

Example input:

{
"location":"New York",
"query":"live music",
"dateFilter":"this-weekend",
"maxItems":200,
"scrapeEventDetails":true
}

Output

One dataset item per event:

{
"id":"1989784917251",
"name":"PrideFest 2026: FREE RSVP",
"url":"https://www.eventbrite.com/e/pridefest-2026-free-rsvp-registration-1989784917251",
"summary":"RSVP here for our free street festival on 4th Avenue from Astor Place to 14th Street!",
"description":"RSVP here for our free street festival, taking place Sunday, June 28th...",
"start_datetime":"2026-06-28T11:00:00-04:00",
"end_datetime":"2026-06-28T18:00:00-04:00",
"timezone":"America/New_York",
"is_online":false,
"venue_name":"PrideFest",
"venue_address":"4th Avenue between Union Square and Astor Place, Manhattan, NY 10003",
"venue_city":"Manhattan",
"venue_region":"NY",
"venue_postal_code":"10003",
"venue_country":"US",
"latitude":40.7333524,
"longitude":-73.9902571,
"organizer_id":"7937981614",
"organizer_name":"NYC Pride",
"organizer_url":"https://www.eventbrite.com/o/nyc-pride-7937981614",
"category":"Community & Culture",
"subcategory":"LGBT",
"format":"Festival or Fair",
"price_min":0.0,
"price_max":0.0,
"currency":"USD",
"is_free":true,
"availability":"InStock",
"status":"EventScheduled",
"is_cancelled":null,
"image_url":"https://img.evbuc.com/...original.20260517-173925?...",
"tickets_url":"https://www.eventbrite.com/checkout-external?eid=1989784917251",
"is_series":false,
"series_id":null
}

Field notes:

• start_datetime/end_datetime carry the venue's UTC offset when scrapeEventDetails is on. With detail scraping off they fall back to the local date and time without an offset, alongside the timezone name.
• price_min/price_max/currency/is_free/availability, organizer_name/organizer_url, and status come from the event page and are populated only when scrapeEventDetails is on.
• category/subcategory/format are Eventbrite's own labels. latitude/longitude come from the venue when Eventbrite publishes them.
• is_series is true when the event is one occurrence of a recurring series (series_id is set).
• Events are deduplicated by id across every source.

Unresolvable inputs and fetch/parse failures are written as typed error items ({ "error": ..., "source_url": ..., "detail": ... }) so one bad URL or a markup change never silently empties your run. The error field is one of unsupported_url, not_found (dead URL), blocked (anti-bot challenge), fetch_failed (transient network or HTTP error), or parse_failed (an event did not match the expected shape). If every source fails and zero events are scraped, the run is marked FAILED with a status message instead of reporting a green, empty success, so schedulers and monitors are not deceived.

Billing

Pay-per-result: one event charge event per stored event. Error records are never charged.

Notes

• Event lists live in the page's window.__SERVER_DATA__ blob; ticket and organizer details come from each event page's schema.org JSON-LD. If Eventbrite changes either structure, the actor emits an explicit error rather than empty results.
• Network calls have a 30s timeout and bounded retries with exponential backoff and jitter; 403/429 are treated as blocks and retried. Concurrency is bounded.