# Eventbrite Events Scraper (`neuro-scraper/eventbrite-events-scraper`) Actor

Eventbrite Scraper SD - Eventbrite Scraper is an events data tool that extracts public Eventbrite events by place, category, keyword and date: name, dates, venue, address, organizer, ticket prices, sales status, plus optional full description, performers and policies.

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

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Eventbrite Scraper - public events by city, category, keyword and date

The Eventbrite Scraper extracts public Eventbrite events: name, start and end time, venue and address with
coordinates, category, organizer (with follower count), ticket price range, currency, free / sold-out flags,
sales status and image. Turn on details for the full description, performers, age limit, duration, refund
policy and FAQ. No Eventbrite account or login is used.

#### Input

| Field | Type | Default | Meaning |
|---|---|---|---|
| `locations` | list | `New York` (prefill) | City, "City, Country", an Eventbrite place slug (ny--new-york) or `online` |
| `category` | select | `all` | One of Eventbrite's 21 categories (music, business, food-and-drink, ...) |
| `searchTerms` | list | empty | Keywords searched in every place (replaces the category) |
| `dateFilter` | select | any upcoming | today, tomorrow, this_weekend, this_week, next_week, this_month, next_month |
| `startUrls` | list | empty | Eventbrite discovery URLs (`/d/...`, `/b/...`) or event URLs (`/e/...`) |
| `maxItems` | integer | `50` | Total events to return |
| `includeDetails` | boolean | `false` | Open each event page (one extra request per event) |
| `proxyConfiguration` | proxy | Apify RESIDENTIAL | Proxy used for Eventbrite |

#### Output (one row per event)

| Field | Meaning |
|---|---|
| `id`, `name`, `url`, `summary` | Event id, title, page, short summary |
| `startDate`, `endDate`, `timezone`, `isOnline`, `language` | When, where in time, online flag |
| `category`, `subcategory`, `format`, `tags` | Eventbrite taxonomy and organizer tags |
| `venueName`, `address`, `city`, `region`, `country`, `postalCode`, `latitude`, `longitude` | Venue |
| `organizerName`, `organizerUrl`, `organizerId`, `organizerFollowers` | Organizer profile |
| `minPrice`, `maxPrice`, `currency`, `isFree`, `isSoldOut`, `hasAvailableTickets`, `salesStatus`, `salesEnd`, `ticketsUrl` | Tickets |
| `imageUrl`, `urgencySignals` | Image; "goingFast", "fewTickets", "salesEndSoon" |
| details: `description`, `performers`, `ageRestriction`, `durationMinutes`, `doorTime`, `refundPolicy`, `eventStatus`, `attendanceMode`, `faq` | Only with `includeDetails` or event URLs |
| `searchTotal`, `page`, `source`, `scrapedAt` | Event count of the search, page, input that produced the row, time |

#### Measured limits (2026-10-03, local runs)

- 20 events per page and at most 49 pages: about 980 events per search (big cities report "10,000").
  Combine categories, date filters and keywords to cover more.
- Keyword searches stop at the number of events the Eventbrite page shows (e.g. 61 for "yoga" in Berlin);
  Eventbrite's API would return thousands of looser matches after that.
- 50 events in 16 s, 70 in 18 s; with details about 1.5 s more per event.
- Tested without proxy from one residential IP; no bot challenge was met. A challenge is never solved: the
  Actor retries on a new IP, then skips the target with an error in the log.

#### Example

```json
{"locations": ["London", "Austin, TX"], "category": "music", "dateFilter": "this_weekend", "maxItems": 200}
```

# Actor input Schema

## `locations` (type: `array`):

One per line: a city (London), city and state/country (Austin, TX / Berlin, Germany), an Eventbrite place slug (ny--new-york) or 'online'.

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

Eventbrite category for the places above (ignored when keywords are given).

## `searchTerms` (type: `array`):

Search events by keyword in each place, e.g. jazz, yoga, startup. One search per place and keyword.

## `dateFilter` (type: `string`):

Eventbrite's date filter.

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

Discovery pages copied from Eventbrite (https://www.eventbrite.com/d/ny--new-york/music--events/) or event pages (https://www.eventbrite.com/e/...-tickets-123456789).

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

Stops after this many events in total. Eventbrite serves 20 per page and at most 49 pages (~980) per search.

## `includeDetails` (type: `boolean`):

Opens every event page for the full description, performers, age limit, duration, refund policy and FAQ. One extra request per event.

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

Residential proxies (the default) are recommended.

## Actor input object example

```json
{
  "locations": [
    "New York"
  ],
  "category": "all",
  "searchTerms": [],
  "dateFilter": "current_future",
  "startUrls": [],
  "maxItems": 50,
  "includeDetails": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# 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 = {
    "locations": [
        "New York"
    ],
    "searchTerms": [],
    "startUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-scraper/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 = {
    "locations": ["New York"],
    "searchTerms": [],
    "startUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-scraper/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 '{
  "locations": [
    "New York"
  ],
  "searchTerms": [],
  "startUrls": [],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call neuro-scraper/eventbrite-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-scraper/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/0RoSYQpz3AzrxD0DZ/builds/JSIhvhpoddO9Rwa7R/openapi.json