# Eventbrite Event Scraper (`mrdoe/eventbrite-event-scraper`) Actor

Scrape Eventbrite events with event names, dates, venues, tickets, prices, organizers, categories, locations, images, and URLs. Ideal for event discovery, market research, ticket monitoring, lead generation, and event data analysis.

- **URL**: https://apify.com/mrdoe/eventbrite-event-scraper.md
- **Developed by:** [MrDoe](https://apify.com/mrdoe) (community)
- **Categories:** Travel, News, Lead generation
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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/platform/actors/running/actors-in-store#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 Events Scraper - Extract Events, Pricing & Organizer Data Worldwide

Scrape structured event data from **any Eventbrite country site** - name, date/time, venue, organizer, category, pricing, and ticket availability - by simply pointing it at an Eventbrite listing page.

### What does Eventbrite Events Scraper do?

Give this Actor one or more Eventbrite **listing URLs** (a city page, a category page, a search results page - on any country domain: `eventbrite.com`, `eventbrite.ie`, `eventbrite.co.uk`, `eventbrite.de`, `eventbrite.com.au`, `eventbrite.ca`, etc.) and it returns one structured record per event, including:

- **Core details** - name, description, date range, venue, address, geo-coordinates, cover image, ticket URL
- **Precise date/time** - local start/end time, IANA timezone, and UTC-normalized timestamps
- **Classification** - category, subcategory, and format (e.g. Music / Nightlife / Party)
- **Organizer info** - name, profile URL, and description/logo when publicly shown
- **Pricing** - currency, minimum/maximum ticket price, whether the event is free, and current sales status
- **Metadata** - Eventbrite's own event ID (for deduplication), source URL, and scrape timestamp

Not affiliated with or endorsed by Eventbrite. Only publicly visible listing and event-page data is collected - no login, CAPTCHA bypass, or access-control circumvention is used.

#### How it works

For each start URL, the Actor first reads the listing page to find the events on it, then visits **each event's own detail page** to pull the richer fields above (organizer, pricing, category, etc.), which aren't present on the listing page itself. This means a run typically makes one request per listing page plus one request per event - factor that into `maxItems` if you're scraping at scale.

Because not every organizer fills in every field on Eventbrite, some fields (organizer description/logo, refund policy, venue capacity, per-ticket-type pricing, taxonomy IDs) will be `null` or `[]` on events where Eventbrite itself doesn't publicly expose that data. Nothing is guessed or fabricated - see the [Output](#output) section for exactly which fields this applies to.

### Why scrape Eventbrite?

- Build a local events calendar or aggregator for any city or country
- Track competitor or industry events, organizers, and pricing
- Monitor event trends and ticket availability by category, city, or date
- Feed structured event data into a marketing, research, or community platform

### How to use Eventbrite Events Scraper

1. [Sign up](https://apify.com/sign-up) for a free Apify account.
2. Open this Actor and click **Try for free** (or **Start**).
3. Enter one or more **Start URLs** - any Eventbrite city or category listing page, on any country site, for example:
   - `https://www.eventbrite.ie/d/ireland--dublin/events/`
   - `https://www.eventbrite.com/d/united-states--new-york/events/`
   - `https://www.eventbrite.co.uk/d/united-kingdom--london/events/`
4. Set **Max events per start URL** (default `5`) and leave **Proxy configuration** on (Apify Proxy is required).
5. Click **Start** and export results as JSON, CSV, Excel, or via API.

### Input

| Field | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `startUrls` | array | Yes | `https://www.eventbrite.ie/d/ireland--dublin/events/` | Eventbrite city/category event listing pages, on any country site. This is also how you control location and category - there's no separate country/city/category input. |
| `maxItems` | integer | No | `5` | Maximum events to scrape per start URL. Set `0` for unlimited. |
| `proxyConfiguration` | object | Yes | `{ "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }` | Apify Proxy is mandatory - Residential is used by default since Eventbrite blocks datacenter IPs with a human-verification challenge. |
| `useCache` | boolean | No | `false` | When enabled, event IDs scraped in previous runs are remembered in a persistent store, so re-running against the same start URLs only fetches events not seen before. Off by default - each run scrapes fresh. |

### Output

Each dataset item is one event. Fields fall into two groups: a core set always populated from the event's own page, and enrichment fields whose presence depends on what the organizer/Eventbrite publish for that specific event.

| Field | Description |
| --- | --- |
| `name` | Event name |
| `startDate`, `endDate` | Event date range |
| `description` | Full event description |
| `venue`, `address`, `locality`, `postalCode` | Venue name and address |
| `latitude`, `longitude` | Venue geo-coordinates |
| `image` | Event cover image URL |
| `url` | Direct link to the Eventbrite ticket page |
| `eventId` | Eventbrite's own event ID - stable and safe to use as a deduplication key |
| `summary` | Short one-line event summary |
| `status` | Event status as reported by Eventbrite (e.g. `live`) |
| `listed` | Whether the event is publicly listed/searchable on Eventbrite |
| `startTime`, `endTime` | Local start/end time of day (`HH:mm:ss`) |
| `timezone` | IANA timezone of the event (e.g. `Europe/Dublin`) |
| `startUtc`, `endUtc` | Start/end date-time normalized to UTC |
| `country`, `region` | Venue's country and region/state, ISO where Eventbrite provides it |
| `onlineEvent` | `true` if the event is hosted online rather than at a physical venue |
| `category`, `subcategory`, `format` | Eventbrite's classification taxonomy for the event |
| `categoryId`, `subcategoryId`, `formatId` | Numeric taxonomy IDs where Eventbrite exposes them publicly; `categoryId`/`subcategoryId` are currently `null` since Eventbrite doesn't surface those IDs on the event page |
| `organizerId`, `organizerName`, `organizerUrl` | Organizer identity and public profile link |
| `organizerDescription`, `organizerLogo` | Organizer bio and logo, only when the organizer has filled these in |
| `organizerPastEvents`, `organizerFutureEvents` | Reserved for organizer event counts; currently `null` - Eventbrite's event page doesn't publish a past/future split |
| `isFree` | `true` if the event has no paid tickets |
| `currency` | ISO currency code for ticket prices |
| `priceMin`, `priceMax` | Lowest/highest ticket price found; `null` for free events or when pricing isn't published |
| `ticketAvailability` | Current sales status (e.g. `on_sale`, `sold_out`, `not_yet_on_sale`) |
| `venueId` | Eventbrite's internal venue ID |
| `venueCapacity` | Venue capacity, when publicly shown (currently rarely available - `null` otherwise) |
| `ticketTypes` | Structured per-ticket-type pricing (`name`/`price`/`currency`/`status`) when reliably available; `[]` otherwise - use `priceMin`/`priceMax` for the aggregate price range instead |
| `refundPolicy` | Publicly stated refund policy (`policyType`, `isRefundAllowed`, `validDays`), or `null` when not shown |
| `source` | Always `"Eventbrite"` |
| `sourceUrl` | The event URL that was scraped |
| `scrapedAt` | ISO timestamp of when the item was scraped |

> `ticketTypes` and `venueCapacity` reflect what Eventbrite's static event page publishes; if an organizer only shows an aggregate price range (the common case), you'll get `priceMin`/`priceMax` with an empty `ticketTypes` array rather than a fabricated breakdown.

#### Example item

```json
{
    "name": "LC Results Night @ Soho Nightclub, Dublin",
    "startDate": "2026-08-21",
    "endDate": "2026-08-22",
    "description": "Dublin's Biggest Leaving Cert Results Party",
    "venue": "Soho Dublin",
    "address": "21 D'Olier Street",
    "locality": "Dublin",
    "postalCode": "D02 A370",
    "latitude": "53.3464476",
    "longitude": "-6.257863899999999",
    "image": "https://img.evbuc.com/...",
    "url": "https://www.eventbrite.ie/e/lc-results-night-soho-nightclub-dublin-tickets-1992291629896",
    "eventId": "1992291629896",
    "summary": "Dublin's Biggest Leaving Cert Results Party",
    "status": "live",
    "listed": true,
    "startTime": "22:30:00",
    "endTime": "02:30:00",
    "timezone": "Europe/Dublin",
    "startUtc": "2026-08-21T21:30:00Z",
    "endUtc": "2026-08-22T01:30:00Z",
    "country": "IE",
    "region": "Dublin",
    "onlineEvent": false,
    "category": "Music",
    "categoryId": null,
    "subcategory": "Other",
    "subcategoryId": null,
    "format": "Party",
    "formatId": "11",
    "organizerId": "78506806553",
    "organizerName": "Touch Events",
    "organizerUrl": "https://www.eventbrite.ie/o/touch-events-78506806553",
    "organizerDescription": null,
    "organizerLogo": null,
    "organizerPastEvents": null,
    "organizerFutureEvents": null,
    "isFree": false,
    "currency": "EUR",
    "priceMin": 13.85,
    "priceMax": 15.99,
    "ticketAvailability": "on_sale",
    "source": "Eventbrite",
    "sourceUrl": "https://www.eventbrite.ie/e/lc-results-night-soho-nightclub-dublin-tickets-1992291629896",
    "scrapedAt": "2026-08-21T09:00:00.000Z",
    "venueId": "298248637",
    "venueCapacity": null,
    "ticketTypes": [],
    "refundPolicy": { "policyType": "no_refunds", "isRefundAllowed": false, "validDays": 0 }
}
```

Export results as JSON, CSV, Excel, XML, or via the [Apify API](https://docs.apify.com/api/v2) once a run finishes.

### Pricing

This Actor is billed on a **pay-per-result** basis (~$1 per 1,000 dataset items). A default cap of 5 events per start URL keeps trial runs inexpensive; raise `maxItems` for larger runs. Note that each event costs one extra page request (the detail-page visit used to enrich the output), so overall run time scales with the number of events, not just the number of start URLs.

### FAQ

**Is this legal?** This Actor only collects publicly available event listing and event-page data. It is not affiliated with or endorsed by Eventbrite. Please respect the site's Terms of Service and applicable data protection laws (GDPR).

**Why does it need a residential proxy?** Eventbrite blocks Apify's shared datacenter proxy pool with a human-verification challenge - a residential proxy is required and enabled by default for reliable results.

**Will every event have every field filled in?** No. Fields like `organizerDescription`, `organizerLogo`, `refundPolicy`, `venueCapacity`, and `ticketTypes` depend entirely on what the organizer has published for that specific event. When Eventbrite doesn't expose a field, this Actor returns `null` (or `[]` for list fields) rather than guessing.

**Does it work on any Eventbrite country site?** Yes - location and currency are entirely determined by the start URLs you provide, so `eventbrite.ie`, `eventbrite.com`, `eventbrite.co.uk`, `eventbrite.de`, `eventbrite.com.au`, etc. are all supported the same way.

Found a bug or have a feature request? Use the Issues tab on this Actor's Apify Store page.

# Actor input Schema

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

Eventbrite city/category event listing pages to scrape from, on any country site, e.g. https://www.eventbrite.ie/d/ireland--dublin/events/, https://www.eventbrite.com/d/united-states--new-york/events/, https://www.eventbrite.co.uk/d/united-kingdom--london/events/

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

Maximum number of events to scrape per start URL. Set to 0 for unlimited.

## `proxyConfiguration` (type: `object`):

Proxy settings for the run. Eventbrite blocks Apify's shared datacenter proxy pool with a human-verification challenge, so a Residential proxy is used by default for reliable results.

## `useCache` (type: `boolean`):

When enabled, event IDs scraped in previous runs are remembered in a persistent store, so re-running the Actor against the same start URLs only fetches events it hasn't scraped before.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.eventbrite.ie/d/ireland--dublin/events/"
    }
  ],
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "useCache": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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 = {
    "startUrls": [
        {
            "url": "https://www.eventbrite.ie/d/ireland--dublin/events/"
        }
    ],
    "maxItems": 5,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("mrdoe/eventbrite-event-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 = {
    "startUrls": [{ "url": "https://www.eventbrite.ie/d/ireland--dublin/events/" }],
    "maxItems": 5,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("mrdoe/eventbrite-event-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 '{
  "startUrls": [
    {
      "url": "https://www.eventbrite.ie/d/ireland--dublin/events/"
    }
  ],
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call mrdoe/eventbrite-event-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mrdoe/eventbrite-event-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/EDYwMUa5dAChOzDKG/builds/imS7zx8CD5QehQh4J/openapi.json