Eventbrite Event Scraper

Extract structured public Eventbrite event listings for event discovery, local market research, competitor monitoring, calendar enrichment, and AI data pipelines.

The actor supports two input modes:

• Search queries plus a location, such as technology meetup in new-york.
• Direct Eventbrite event URLs or Eventbrite discovery URLs in startUrls.

Extracted fields

Each dataset item represents one unique event and includes its Eventbrite ID, title, canonical URL, image, start/end dates, timezone, online status, venue and address, city/region/postal code/country, organizer name and URL, category, lowest published price, currency, free-event flag, and scrape metadata. Descriptions and organizer fields can be disabled to reduce page work.

Example input

{
  "searchQueries": ["technology meetup", "startup networking"],
  "location": "new-york",
  "dateFilter": "this-month",
  "maxResults": 25,
  "includeDescription": true,
  "includeOrganizer": true
}

Direct URL example:

{
  "startUrls": [
    { "url": "https://www.eventbrite.com/e/example-event-tickets-123456789" }
  ],
  "maxResults": 1
}

How it works

The actor uses a headless Chromium session because Eventbrite discovery pages are JavaScript-rendered. It reads public JSON-LD structured data on event pages and uses conservative fallbacks for discovery cards. Results are deduplicated by Eventbrite event ID or canonical URL and are written as soon as they are extracted.

Pricing

Event	Price
Actor start	$0.00005 per run
Event returned	$0.001 per unique event

Example: a run returning 25 events costs $0.02505 in actor event charges, plus any platform usage passed through by the selected Apify pricing configuration.

Responsible use

This actor accesses public Eventbrite pages only. It does not log in, purchase tickets, bypass access controls, or collect attendee data. Respect Eventbrite’s terms, robots guidance, applicable privacy laws, and reasonable request rates. Use an Apify proxy configuration only when you are authorized to do so and direct access is blocked.

Limitations

Eventbrite can change page markup, regional availability, and the amount of structured data exposed on public pages. Missing optional values are returned as null; a warning is placed in the SUMMARY key-value record when a detail page cannot be fetched. A zero-result run is not proof that no matching event exists.

For AI agents

Use this actor when you need public Eventbrite event records by keyword/location or a known Eventbrite URL. Do not use it for ticket purchasing, attendee lists, private organizer data, or bypassing access restrictions. The result shape is one event per dataset item with stable semantic field names and a traceable url.