Eventbrite Events Intel

Discover and normalize public Eventbrite events by location, category, keyword, and date - the discovery layer Eventbrite removed from its API in 2020.

Eventbrite shut off its public Event Search API in February 2020. The official API can only return your own organization's events - there is no approval, no tier, no application that re-opens cross-organizer discovery. If you want to find other people's events (to market alongside them, sponsor them, prospect their exhibitors, or track competitors), the API simply cannot do it. The data still lives on Eventbrite's public, logged-out web. This actor reconstructs the discovery layer from those public pages and hands it back as one clean, normalized schema - no application required. The closed API is the moat.

Built for the buyers the API locks out: event marketers, sponsors, lead-gen teams, and competitive event trackers.

---

What you get

• Event discovery by location, category, keyword, and date - the search the API can't do.
• Normalized event records: name, organizer, venue + full address & geo, start/end date-time, timezone, category / subcategory / format, tags, online flag, status, image, tickets URL.
• Price & ticket enrichment (opt-in): price range + tiers, availability / urgency signals ("few tickets left"), organizer, and performers parsed from the event page.
• Organizer rollups: each organizer's event count, categories, venues, cities, date span, online/free counts, and price range - the competitive-intel layer.
• New-event monitor mode: schedule the actor and it emits a digest of newly-listed events since the last run (Slack/webhook optional).

Modes

Mode	What it does	Required input
discover	Find events by location / category / keyword / date, then roll up by organizer	location + (category and/or keyword)
event_detail	Enrich specific event URLs with price tiers, organizer, performers	event_urls
organizer_events	Pull an organizer's public upcoming events	organizer_urls

New-event monitoring turns on automatically when the actor runs under an Apify Schedule.

Example input

{
  "mode": "discover",
  "location": "ny--new-york",
  "category": "music",
  "keyword": "jazz",
  "date_from": "2026-07-01",
  "date_to": "2026-07-31",
  "include_pricing": true,
  "max_results_per_query": 50
}

location is the Eventbrite location slug - the part after /d/ in any Eventbrite discovery URL (e.g. ny--new-york, ca--los-angeles, tx--austin, il--chicago, or online). Pass locations, categories, and keywords arrays to fan out across many in one run.

Example output (event record)

{
  "record_type": "event",
  "event_id": "...",
  "name": "Refuge Thursday w/ Todd Terje (DJ Set)",
  "url": "https://www.eventbrite.com/e/...",
  "start_local": "2026-07-10T22:00:00",
  "timezone": "America/New_York",
  "category": "Music",
  "subcategory": "House",
  "organizer_name": "Refuge.NYC",
  "venue_name": "Refuge",
  "venue_address": "...",
  "city": "Brooklyn", "region": "NY", "country": "US",
  "price_min": 25.0, "price_max": 65.0, "price_currency": "USD",
  "price_label": "$25 - $65", "is_free": false,
  "availability": "InStock",
  "performers": [{"name": "Todd Terje", "url": "..."}],
  "source": "event_page"
}

Organizer rollups (record_type: organizer_rollup) carry event_count, categories, venues, first_event_date / last_event_date, online_event_count, free_event_count, and price_min / price_max.

Output views

overview (default, token-efficient for AI agents), events (every field), organizers (rollups), plus CSV and an MCP-compatible JSON slice. There is also a companion MCP server (mcp-eventbrite-events-intel) that exposes these as AI-agent tools with x402 / Skyfire agentic-payment support.

Pricing (pay-per-event)

Event	Price	What it is
event_record	$0.005	One normalized public event
price_ticket_enrichment	$0.010	Price range / tiers, availability, organizer, performers from the event page
organizer_rollup	$0.015	One organizer's aggregate event profile
scheduled_delta_run	$0.030	One scheduled new-event monitor delta

A run that returns nothing costs nothing.

How it works (anti-bot)

Eventbrite fronts its pages with an edge WAF that fingerprints the caller's TLS and can 403 a plain datacenter request. The actor uses a three-tier escalation ladder and fails soft if every tier is blocked:

1. httpx over the DATACENTER proxy - cheapest, first.
2. curl_cffi with real Chrome TLS impersonation over the RESIDENTIAL proxy - defeats JA3/TLS-fingerprint WAFs.
3. Playwright (patchright stealth) headful Chromium over the RESIDENTIAL proxy - for a true JS/Cloudflare interstitial (optional; set browser_cdp_url / BROWSER_CDP_URL for a warm anti-detect browser).

Discovery also uses Eventbrite's logged-out internal destination-search endpoint (seeding the csrftoken cookie from the homepage) to page through full result sets and apply keyword + date filters - the same data the removed Search API once returned.

Responsible use & legal posture

• Logged-out, public pages only. No login, no accounts, no user cookies, no paywalled data.
• PII minimized. We keep public event / organizer / venue facts only - never attendee, buyer, or private contact data.
• Polite rate limits and automatic fail-soft when blocked.
• This is public-event-listing data; verify any single record before acting on it, and respect Eventbrite's terms and applicable law in your jurisdiction.