Eventbrite Scraper: Events by City, Date & Category

Search Eventbrite by place, keyword and date and get one row per event: name, start and end time (with the venue's UTC offset), venue, city, category, and, when you switch on event pages, the ticket price range, free or paid, organiser and sold-out status. Switch on monitoring and the actor remembers every event it has seen, so a daily run tells you which events are new, repriced or sold out, optionally straight into Slack, Discord or Telegram.

No login, no cookies, no API key. A search that finds nothing costs nothing.

Who uses this

• Event-lead builders and sponsors who want every conference, meetup or expo in a city this month, with the organiser, to start outreach.
• Local-event aggregators and newsletters that list "what's on this weekend" for a city and need fresh rows every morning.
• n8n / Make / Clay workflows that need a clean event list from a place and a keyword, or an alert when a new event appears.

Try it in 30 seconds

Press Start with the pre-filled input: it searches New York, returns the first 20 events, and takes one page request.

{ "searches": ["ny--new-york"], "maxEvents": 20 }

Write your own lines, one search per line, place first and an optional keyword after a bar:

ny--new-york                          everything in New York
Austin, TX | startup                  keyword "startup" in Austin
London, United Kingdom | tech         keyword "tech" in London
online | python                       online events about python
https://www.eventbrite.com/d/ny--new-york/jazz/    a pasted search link

A place is "City, ST" for the US, "City, Country", an Eventbrite place slug (ny--new-york), or online. If Eventbrite does not know the place or the keyword, that line comes back as a free "not found" row.

What you get

One row per event:

Field	What it is
eventId, url, name, summary	The event, its public page and the organiser's short description
startAt, endAt, timezone	Start and end with the venue's UTC offset, e.g. 2026-11-01T17:00:00-05:00
venue, city, region, country, online	Where it happens (venue name and town only, no street addresses)
category	Eventbrite's category, e.g. Music, Business
isFree, minPrice, maxPrice, currency, ticketsAvailable, organizerName, organizerUrl	Filled when Fetch event pages is on (see Limits)
cancelled	Eventbrite marks the event as cancelled
changeType, previousMinPrice, previousMaxPrice, firstSeenAt	Monitoring: baseline, new-event, price-change, sold-out or unchanged
totalMatches, hasMore	How many events Eventbrite says match, and whether more exist than were returned

Filters that reach Eventbrite: place, keyword, date range (today, tomorrow, this weekend, next week, next 30 days, or exact start and end dates) and online only. Filters applied by the actor after the fetch: free only and paid only (they read each event page, so they take longer).

Example: new events this weekend, posted to Discord

Search New York for this weekend, remember what was seen, and post each new event to a Discord channel:

{
  "searches": ["ny--new-york | music"],
  "dateRange": "this_weekend",
  "maxEvents": 100,
  "deltaMode": true,
  "deltaName": "ny-music-weekend",
  "alertOn": "new-event",
  "alertOnChangeOnly": true,
  "notifyUrl": "https://discord.com/api/webhooks/<id>/<token>"
}

Run it daily on a schedule. The first run only sets the baseline (nothing is "new" yet, and nothing is posted); from the second run on, only events that were not on the search before are returned, billed and posted. The webhook link is stored encrypted and never appears in the results.

Monitoring: new, repriced, sold out

Turn on Track events across runs and each run compares every event with the previous run of the same search and watchlist name. Tell me about picks what counts: new events, price changes, sold-out events, or all three. Price changes and sold-out need the event pages, which are then fetched automatically. Only return rows that changed drops unchanged events from the output and the bill. Seed silently remembers the first run without returning it. State lives in a named store (eventbrite-events-lookup-delta) that keeps up to 20,000 events per watchlist.

Alerts go to a Discord or Slack webhook, a Telegram bot link or any URL (JSON for n8n, Make or Zapier), at most 20 messages per run by default. A message is only sent for an event row that was actually billed, and a failed message never fails the run.

Limits, stated plainly

• Search list vs event pages. Eventbrite's search results carry no price, organiser or ticket status. Those come from each event's own page: turn on Fetch event pages (one extra request per event). Without it, isFree, minPrice, maxPrice, currency, organizerName, organizerUrl and ticketsAvailable are empty. The free / paid filters and price-change / sold-out alerts switch it on by themselves.
• Speed. The actor makes at most one request per second. A search page holds 20 events, so 100 events without event pages take well under a minute. Each event page takes a few seconds more (measured 2 to 6 seconds on the residential proxy), so about 100 events with event pages fit in one run. A run stops fetching after about 9 minutes and returns what it has (hasMore: true).
• How many. Up to 500 events per search and 20 searches per run. Eventbrite lists at most 1,000 events per search (50 pages of 20); with event pages, expect to reach about 100 events per run (see Speed).
• Dates. A date window returns events that run during it, including multi-day events that started earlier. "Today" and "this weekend" are worked out from today's date in UTC.
• Places. Eventbrite place slugs are state--city in the US (ny--new-york) and country--city elsewhere (united-kingdom--london). Outside the US, Eventbrite sends event links on the country domain (eventbrite.co.uk, .nl, .ca ...); the rows keep the link as Eventbrite gave it.
• Not collected. No attendee lists, no comments, no emails or phone numbers, no street addresses. Category and date path pages (like business--events) are not read; use the keyword and date range instead.
• Proxy. Runs use a residential proxy by default: Apify's datacenter proxy was served a bot-check page instead of results.
• Terms. Eventbrite's terms restrict commercial use of site content. You are responsible for how you use the data.

How to use

1. In the Apify Console. Open the actor page and click Start — the searches field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["ny--new-york"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "searches": [
    "ny--new-york"
  ]
}

One search per line: a place, then an optional keyword after a bar. Places: "City, ST" (US), "City, Country", an Eventbrite place slug like ny--new-york, or "online". You can also paste an Eventbrite search link (https://www.eventbrite.com/d/ny--new-york/jazz/). Up to 20 searches per run. Accepted formats: ny--new-york, ny--new-york | jazz, London, United Kingdom | tech, Austin, TX | startup, online | python, https://www.eventbrite.com/d/ny--new-york/jazz/.

Sample output

query	found	status	searchQuery	totalMatches	hasMore	events	eventId	url	name	summary	startAt	endAt	timezone	venue	city	region	country	online	isFree	minPrice	maxPrice	currency	category	organizerName	organizerUrl	ticketsAvailable	cancelled	checkedAt	changeType	previousMinPrice	previousMaxPrice	firstSeenAt	notifyErrors	scrapedAt
ny--new-york	true	OK				<all events found (full list)>										<state / region>																		1970-01-01T00:00:00.000Z

A miss comes back as a row with "found": false and is never charged.

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["ny--new-york"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"searches":["ny--new-york"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~eventbrite-events-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"searches":["{{search}}"]}, mapping the row's search into the searches array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Eventbrite Scraper | Apify" — the agent will find and run this actor.

FAQ

Why are the price columns empty? Eventbrite's search list has no prices. Turn on Fetch event pages to open each event and read its ticket range.

Why does a place come back as not found? Eventbrite did not recognise the place slug. Use "City, ST" or "City, Country", or copy the slug from an Eventbrite search link (/d/<slug>/...).

Can I get only free events? Yes: Free events only. It reads event pages, so it scans up to five times the number of events you asked for.

Does it work from a schedule? Yes. Save it as a Task with monitoring on and a watchlist name, then schedule it daily.