Eventbrite Scraper — Events, Organizers & Demand Signals

Scrape Eventbrite events from any city, country or category and get a flat, spreadsheet-ready table of event data: venue with coordinates, ticket prices, the organizer with follower count and social links — plus Eventbrite's own demand signals showing which events are actually selling.

Built for event lead generation, market research, competitive analysis and event aggregation. No Eventbrite account, no API key, no browser — one request returns 50 events.

Table of contents

• Why this Eventbrite scraper
• Demand signals — the field nobody else exposes
• Use cases
• Cost
• Input
• Output
• How to use it
• Working with the data
• Run it from AI agents
• Honest limits
• FAQ
• Related Actors

---

Why this Eventbrite scraper

Most Eventbrite scrapers hand you an event list. This one answers the question you actually had when you started scraping: who is behind this event, how big are they, and is it selling?

	Typical Eventbrite scraper	This Actor
Organizer name	✅	✅
Organizer follower count	❌	✅
Organizer social handles	billed as a separate enrichment step	✅ included, no extra charge
Demand signals ("few tickets left")	❌	✅
isSellingFast flag	❌	✅
Venue coordinates	sometimes	✅ lat/lng on every venue
Price range	min only	✅ min and max
Output shape	nested JSON (crop_mask, edge_color…)	✅ flat row, opens straight in Excel
Failed pages	silently missing	✅ reported with the reason

The organizer block is the part people usually pay twice for — competing Actors charge per enriched organizer and load an extra page for each one. Here it arrives in the same response as the event, so it costs nothing extra and adds no time.

---

Demand signals — the field nobody else exposes

Eventbrite shows badges like "Few tickets left" and "Sales end soon" on its own site. They come down in the API response, and this Actor keeps them:

"urgencySignals": ["fewTickets"],
"isSellingFast": true

isSellingFast is deliberately narrow: only scarcity counts. salesEndSoon is a deadline, not proof of demand, so it does not raise the flag. In a Berlin run of 60 events, 33 carried a signal and 14 were genuinely selling fast.

This is the closest public proxy for how well an event is selling — useful for picking venues, pricing your own event, or ranking leads by how much money they actually move.

---

Use cases

1. Event lead generation

Build a targeted event organizer list for any city: organizer name, follower count, Facebook and Twitter handles, and profile URL on every row. Ideal if you sell to event hosts — catering, ticketing, venues, AV, sponsorship, marketing.

2. Sponsorship prospecting

Sort by organizerFollowers to find the organizers with real audiences instead of the ones with the loudest event titles.

3. Event market research

What does a workshop actually cost in Berlin versus Austin? Every row carries min and max ticket price with currency, so you can price your own event off real numbers.

4. Competitive analysis

Schedule a daily run on your category and city, and watch who launches what, at which price, and whether it sells out.

5. Event aggregation

Feed a city or category into your own site or app. Rows are flat and stable, with image URLs, tags, timezone and ticket links included.

6. Venue and demand analysis

Coordinates on every venue plus demand signals show which rooms in a city actually fill up — and which nights they fill on.

7. Demand-based content

Build "Top events this weekend" roundups that rank by real scarcity signals rather than by guesswork.

8. Automated alerts

Run on a schedule and diff the dataset to catch new events in your niche the day they are published.

---

Cost

Pay per event returned. maxResultsPerLocation is a hard ceiling, so the bill is knowable before the run starts — 200 events per location means at most 200 billable rows per location.

Organizer data is included in that price. Actors that bill organizer enrichment separately charge for it per unique organizer, on top of the per-event price.

Turning on Include full description costs one extra request per event (Eventbrite does not return descriptions in search results), which makes the run slower but does not change the per-event price.

---

Input

Field	Description
Locations	Berlin, Germany, a slug like germany--berlin, or a full /d/ URL. Mix freely — each is searched separately.
Category	One of Eventbrite's 21 categories, or all of them.
Keyword	Free-text search inside the location — a topic, brand or artist.
Time frame	Upcoming, today, this weekend, next month… or a custom startDate/endDate range.
Price	Free only, paid only, or any.
Online events only	Online events instead of physical venues. Still needs a location — Eventbrite scopes online events by country.
Max events per location	Your cost ceiling. Up to 10,000 per search.
Include full description	Off by default. Adds the full description text at the cost of one extra request per event.

{
  "locations": ["New York, United States", "Berlin, Germany"],
  "category": "103",
  "dates": "this_weekend",
  "priceFilter": "paid",
  "maxResultsPerLocation": 200
}

---

Output

49 fields per event, all flat. A trimmed sample:

{
  "name": "Out & Abt",
  "startDateTime": "2026-07-25T16:00",
  "venueName": "Elsewhere - The Rooftop",
  "venueCity": "Brooklyn",
  "venueCountry": "US",
  "latitude": 40.709411,
  "longitude": -73.958,
  "minPrice": 18.46,
  "maxPrice": 25.0,
  "currency": "USD",
  "isFree": false,
  "isSoldOut": false,
  "isSellingFast": true,
  "urgencySignals": ["salesEndSoon", "fewTickets"],
  "organizerName": "Elsewhere",
  "organizerFollowers": 12480,
  "organizerTwitter": "elsewherespace",
  "organizerUrl": "https://www.eventbrite.com/o/elsewhere-105655500371",
  "tags": ["Music", "Concert", "Dj"],
  "url": "https://www.eventbrite.com/e/out-abt-tickets-198354591421"
}

Fields are grouped into identity · when (date, time, timezone) · where (venue, full address, coordinates) · money (min/max price, free, sold out, availability) · demand · organizer (followers, summary, Facebook, Twitter, profile URL) · misc (tags, language, cancelled, series) · provenance (which search produced the row).

---

How to use it

1. Enter one or more locations — a city and country is enough.
2. Optionally narrow by category, keyword, date range or price.
3. Set Max events per location to cap your cost.
4. Click Start — a 60-event run finishes in about 10 seconds.
5. Export from the Storage tab as CSV, Excel, JSON or XML, or pull it via API.

---

Working with the data

• Excel / Google Sheets — the dataset has a ready Overview view with the 26 columns that matter, in a readable order. Export as CSV, or use IMPORTDATA() with the dataset CSV link.
• API — GET https://api.apify.com/v2/datasets/<datasetId>/items?format=csv&view=overview
• Integrations — the dataset connects to Make, Zapier, Google Drive, Slack and webhooks from the Apify integrations tab.
• Scheduling — run daily or weekly; each run is a fresh dataset, so diffing them gives you new events only.

---

Run it from AI agents

The Actor exposes a standard input schema, so it works as a tool for LLM agents through Apify's MCP server — an agent can search events, filter by demand signals, and hand back an organizer shortlist without any glue code.

---

Honest limits

• Page size is 50. Eventbrite caps it; asking for 100 silently returns 50.
• Descriptions are not free. Eventbrite returns full_description as null in search results, so the Actor fetches each description separately when you ask for it. That is why the option is off by default — the alternative would be shipping an always-empty column.
• organizerUpcomingEvents is usually null. Eventbrite returns the key but rarely fills it. Kept visible rather than hidden, so you can see it is genuinely empty rather than silently dropped.
• A failed page is reported, never skipped quietly. If a request fails after every retry, the reason lands in RUN_SUMMARY — an empty result is never disguised as "no more events".
• Proxy: datacenter proxies are enough. Residential ones only add cost. Eventbrite rejects some datacenter IPs on some paths, so the Actor retries with a fresh session, a different path and HTTP/1.1 before giving up.

---

FAQ

Do I need an Eventbrite account or API key? No. This uses Eventbrite's public search — no login, no key, no quota.

Is this an Eventbrite API alternative? For discovery, yes. Eventbrite's official API no longer exposes public event search to third parties; this Actor reads the same search the website uses.

Can I scrape one organizer's events? Search their city with a keyword matching their name, then filter rows by organizerId.

Can I get events near a specific point rather than a whole city? Search the city and filter by latitude/longitude — every venue row carries coordinates.

How do I find only events that are selling well? Filter on isSellingFast. It is set only by scarcity signals, not by countdown timers.

Does it work outside the US? Yes — any Eventbrite location. Berlin, London, Barcelona and Paris are all verified in testing.

Can I run it on a schedule? Yes, like any Apify Actor. Daily runs on a category make a clean feed of newly published events.

Is scraping Eventbrite legal? This Actor collects only publicly visible event listings — no login, no personal data behind authentication. As with any scraping, how you use the data is your responsibility.

---

Related Actors

• Airbnb Scraper — size up the same local market from the accommodation side.
• Google Trends Scraper — check whether the topic behind an event is growing before you invest in it.
• Facebook Ads Library Scraper — see how event organizers in your niche advertise, and which creatives they keep running.
• Telegram Channel Scraper — track how events get promoted in public communities.
• Indeed Jobs Scraper — find companies hiring in a city, another angle on local business activity.