# Eventbrite Event Scraper (`midnight_static/eventbrite-events-scraper`) Actor

Scrape upcoming Eventbrite events by city and category: title, dates, venue, price range and organizer name. No personal data collected, robots.txt respected, rate-limited crawling.

- **URL**: https://apify.com/midnight\_static/eventbrite-events-scraper.md
- **Developed by:** [Ferit Töngemen](https://apify.com/midnight_static) (community)
- **Categories:** Open source
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Eventbrite Event Scraper

Scrape upcoming Eventbrite events by city and category — title, dates, venue, price range and organizer name — with no personal data, robots.txt respected and rate-limited crawling.

### What it does

Give it a city (and optionally a category), get back upcoming Eventbrite events as clean, flat rows:
title, start/end date, timezone, venue name, city, country, online flag, price range, category,
organizer name and URL, the event URL, and the browse page the event was found on (`sourceListUrl`).

Discovery works through Eventbrite's own sitemap and category browse pages (`/b/<city>/<category>/`),
which are stable and reachable from the Apify platform. City names are resolved against the sitemap,
so "San Francisco", "Istanbul" or the exact slug `ca--san-francisco` all work. If a name is ambiguous
(`springfield`, or `new york` as city vs. state) the run stops and lists the candidates instead of guessing.

```json
{
  "city": "San Francisco",
  "category": "music",
  "maxItems": 20,
  "futureOnly": true
}
```

### Output

One row per event. Every field is present in every row; missing values are `null`, never omitted.

```json
{
  "id": "1983682844788",
  "url": "https://www.eventbrite.com/e/prime-the-san-francisco-meat-2026-tickets-1983682844788",
  "title": "PRIME - The San Francisco MEAT 2026",
  "description": "PRIME - The San Francisco MEAT!",
  "startDate": "2026-09-26T05:00:00.000Z",
  "endDate": "2026-09-26T11:00:00.000Z",
  "timezone": "-07:00",
  "venueName": "Club Six - Both Floors!",
  "city": "San Francisco",
  "country": "US",
  "isOnline": false,
  "price": { "min": 75.38, "max": 75.38, "currency": "USD" },
  "category": "San Francisco Music Events",
  "organizerName": "TrophyDad",
  "organizerUrl": "https://www.eventbrite.com/o/trophydad-11423585232",
  "attendeeCount": null,
  "sourceListUrl": "https://www.eventbrite.com/b/ca--san-francisco/music/",
  "scrapedAt": "2026-09-14T19:05:25.010Z"
}
```

Notes on fields:

- `attendeeCount` is always `null` today: Eventbrite does not expose it in the page's structured data.
- `timezone` is the UTC offset of the event's local time (`-07:00`), not an IANA name.
- `description` is truncated to 2,000 characters; emails, phone numbers and URLs inside it are masked.
- `sourceListUrl` tells you which browse page the event was found on — useful for auditing and for
  understanding why an event from another city can appear (Eventbrite occasionally lists it there).

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `city` | string | — | City name ("San Francisco", "Istanbul") or Eventbrite slug (`ca--san-francisco`). Use `online` for online events. Ambiguous names stop the run and list candidates. |
| `category` | string | — | Eventbrite category slug: `music`, `business`, `arts`, `sports-and-fitness`, `food-and-drink`, `technology`… Leave empty for all categories in the city. If the slug does not exist for that city, the run stops and lists the valid ones. |
| `subcategory` | string | — | e.g. `rock`, `jazz`, `classical` for `music`. Only meaningful with `category`. |
| `maxItems` | integer | 50 | Upper bound on records written. You are charged per record. If the city/category has fewer events, you get what exists plus a warning saying how many pages were scanned and why there is no more. |
| `futureOnly` | boolean | true | Skip events that have already ended. |
| `dateFrom` / `dateTo` | string | — | `YYYY-MM-DD`, inclusive. Filters the fetched results only. |
| `startUrls` | array | — | Advanced. Skips discovery. Event (`/e/`) and browse (`/b/`) URLs are reliable. |
| `onlineOnly` | boolean | false | Shortcut for `city: online`. |

Request budget for the example input above: 32 requests (1 sitemap index + 5 sitemap shards + 6 browse pages + 20 event pages).
The run log prints the planned and actual request counts.

#### Category slugs

Categories are Eventbrite's own browse slugs and differ slightly per city. If you pass one that does not
exist for the city, the run stops and lists the valid ones. For San Francisco (measured 14 Sep 2026) they are:

`arts, auto-boat-and-air, business, charity-and-causes, community, family-and-education, fashion,
film-and-media, food-and-drink, government, health, hobbies, holiday, home-and-lifestyle, music, nightlife,
other, school-activities, science-and-tech, seasonal, spirituality, sports-and-fitness, tech, travel-and-outdoor`

### What it does NOT do

- **No organizer discovery.** Organizer pages (`/o/…`) render their event lists client-side; the static
  HTML carries no events, so this Actor does not crawl them. `organizerName` and `organizerUrl` come from
  the event page itself.
- **No personal data.** Attendee names, emails, phone numbers, social handles and profile pictures are
  never collected. Free-text fields are scanned and masked before export. Organizer name is taken only
  when Eventbrite marks it as an organization, not a person.
- **Date filters are post-filters.** `dateFrom` / `dateTo` narrow the output, not the crawl: they do not
  reduce the number of requests and do not widen the search.
- **No `/d/` list pages.** Eventbrite's `/d/` search listings answer datacenter traffic with a
  human-verification challenge about three times out of four, and the outcome changes between attempts.
  This Actor does not retry those pages. If you pass a `/d/` URL in `startUrls` it is tried once and skipped.
- **No ticket purchase, no login, no API endpoints.** Only public pages that Eventbrite's robots.txt allows.

### Limits and compliance

- **Personal data:** none collected. Output is a fixed whitelist of 18 fields; anything else on the page
  is dropped. Free text is masked for emails, phones and URLs.
- **robots.txt:** fetched once per run and obeyed. Paths it disallows are never requested.
  If robots.txt cannot be fetched after three attempts, the run stops rather than guessing.
- **Rate limiting:** 2 concurrent requests, at most 60 requests per minute, 0.5–1.5 s random delay
  before every request. Human-verification responses are never retried; five in a row stop the run.
- **Coverage:** browse pages list at most 8 events each. A single city + category typically exposes
  a few hundred upcoming events; ask for more than exist and you get a warning with the exact numbers.
- **Freshness:** data is read live at run time. Eventbrite's sitemap does not carry per-event
  modification dates, so there is no "changed since" mode.
- **Failures are loud.** If discovery cannot start, if a record fails schema validation, or if the
  internal counters do not reconcile, the run fails with a diagnostic message. It never finishes
  green with an empty dataset and no explanation.

### FAQ

**Why not use the Eventbrite API?**

The public search endpoint was retired in 2020. What remains requires an API key, OAuth, and in practice
a partnership for anything beyond your own events. This Actor reads public pages instead — no credentials,
no application process.

**Why did an event from another city appear in my results?**

Browse pages are Eventbrite's own listings, and they occasionally surface events from nearby or unrelated
places. The `city` field comes from the event's own structured data, not from your input. Use
`sourceListUrl` to see which browse page produced the row.

**Can I get organizer emails or attendee lists?**

No, by design. This Actor collects no personal data. If you need contact details, this is not the right tool.

**What happens if I ask for more events than exist?**

You get the ones that exist, plus a warning stating how many were requested, how many were found, how many
browse pages were scanned, and why there are no more.

### Pricing

Pay per result: **$3.50 per 1,000 results** ($0.0035 per event row). You pay only for rows written
to the dataset. A run that finds nothing costs only platform usage (roughly $0.007 for a 20-event run
at 1 GB memory on the reference runs).

# Actor input Schema

## `city` (type: `string`):

Sehir adi ("San Francisco", "Istanbul") ya da Eventbrite slug'i ("ca--san-francisco"). Ad birden fazla yere uyarsa kosu durur ve adaylari listeler; o zaman tam slug verin. Cevrim ici etkinlikler icin "online" yazin. startUrls verilmisse yok sayilir.

## `category` (type: `string`):

Eventbrite kategori slug'i: music, business, arts, sports-and-fitness, food-and-drink, technology... Bos birakilirsa sehirdeki tum kategoriler.

## `subcategory` (type: `string`):

Eventbrite alt kategori slug'i (ornek: music icin rock, jazz, classical). Yalniz category ile birlikte anlamli.

## `startUrls` (type: `array`):

Verilirse sehir/kategori kesfi ATLANIR. Etkinlik (/e/) ve gezinme (/b/) URL'leri guvenilir. Liste (/d/) yollari guvenilir degil: tek deneme yapilir, engellenirse yeniden denenmez; sehir/kategori girdisini ya da /b/ kullanin. Organizator (/o/) sayfalari statik HTML'de etkinlik tasimiyor.

## `maxItems` (type: `integer`):

Kaydedilecek etkinlik sayisi ust siniri. Her kayit icin ucretlendirilirsiniz. Sehir/kategori icin yeterli sayfa yoksa bulunan kadari yazilir ve uyari loglanir.

## `futureOnly` (type: `boolean`):

Gecmis etkinlikleri atar.

## `dateFrom` (type: `string`):

YYYY-MM-DD. Bu filtre cekilen sonuclari suzer; arama kapsamini genisletmez veya daraltmaz. Istek sayisini azaltmaz; yalniz araliga girmeyen kayitlar yazilmaz.

## `dateTo` (type: `string`):

YYYY-MM-DD. Bu filtre cekilen sonuclari suzer; arama kapsamini genisletmez veya daraltmaz. Istek sayisini azaltmaz; yalniz araliga girmeyen kayitlar yazilmaz.

## `onlineOnly` (type: `boolean`):

city yerine "online" kullanir (city ile birlikte verilirse bu kazanir).

## Actor input object example

```json
{
  "city": "San Francisco",
  "maxItems": 50,
  "futureOnly": true,
  "onlineOnly": false
}
```

# Actor output Schema

## `results` (type: `string`):

One row per event, 18 fields (see dataset schema). Missing values are null, never omitted.

## `runStats` (type: `string`):

Counters, request budget (plan vs actual), proxy and charging verdicts, discovery summary.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "city": "San Francisco"
};

// Run the Actor and wait for it to finish
const run = await client.actor("midnight_static/eventbrite-events-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "city": "San Francisco" }

# Run the Actor and wait for it to finish
run = client.actor("midnight_static/eventbrite-events-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "city": "San Francisco"
}' |
apify call midnight_static/eventbrite-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,midnight_static/eventbrite-events-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ZobgosBi3RelDf6Vi/builds/SkV43f5Q4xLdE3UTZ/openapi.json