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

Extract structured public Eventbrite events from search pages or direct event URLs for research, discovery, and event intelligence workflows.

- **URL**: https://apify.com/muhammadafzal/eventbrite-event-scraper.md
- **Developed by:** [Muhammad Afzal](https://apify.com/muhammadafzal) (community)
- **Categories:** Other, Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 event returneds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Event Scraper

Extract structured public Eventbrite event listings for event discovery, local market research, competitor monitoring, calendar enrichment, and AI data pipelines.

The actor supports two input modes:

- Search queries plus a location, such as `technology meetup` in `new-york`.
- Direct Eventbrite event URLs or Eventbrite discovery URLs in `startUrls`.

### Extracted fields

Each dataset item represents one unique event and includes its Eventbrite ID, title, canonical URL, image, start/end dates, timezone, online status, venue and address, city/region/postal code/country, organizer name and URL, category, lowest published price, currency, free-event flag, and scrape metadata. Descriptions and organizer fields can be disabled to reduce page work.

### Example input

```json
{
  "searchQueries": ["technology meetup", "startup networking"],
  "location": "new-york",
  "dateFilter": "this-month",
  "maxResults": 25,
  "includeDescription": true,
  "includeOrganizer": true
}
```

Direct URL example:

```json
{
  "startUrls": [
    { "url": "https://www.eventbrite.com/e/example-event-tickets-123456789" }
  ],
  "maxResults": 1
}
```

### How it works

The actor uses a headless Chromium session because Eventbrite discovery pages are JavaScript-rendered. It reads public JSON-LD structured data on event pages and uses conservative fallbacks for discovery cards. Results are deduplicated by Eventbrite event ID or canonical URL and are written as soon as they are extracted.

### Pricing

| Event | Price |
|---|---:|
| Actor start | $0.00005 per run |
| Event returned | $0.001 per unique event |

Example: a run returning 25 events costs $0.02505 in actor event charges, plus any platform usage passed through by the selected Apify pricing configuration.

### Responsible use

This actor accesses public Eventbrite pages only. It does not log in, purchase tickets, bypass access controls, or collect attendee data. Respect Eventbrite’s terms, robots guidance, applicable privacy laws, and reasonable request rates. Use an Apify proxy configuration only when you are authorized to do so and direct access is blocked.

### Limitations

Eventbrite can change page markup, regional availability, and the amount of structured data exposed on public pages. Missing optional values are returned as `null`; a warning is placed in the `SUMMARY` key-value record when a detail page cannot be fetched. A zero-result run is not proof that no matching event exists.

### For AI agents

Use this actor when you need public Eventbrite event records by keyword/location or a known Eventbrite URL. Do not use it for ticket purchasing, attendee lists, private organizer data, or bypassing access restrictions. The result shape is one event per dataset item with stable semantic field names and a traceable `url`.

# Actor input Schema

## `searchQueries` (type: `array`):

Event keywords, one per line. Example: 'jazz concert' or 'startup networking'.

## `location` (type: `string`):

City, region, or country slug used for Eventbrite discovery. Example: 'new-york' or 'london'.

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

Optional direct Eventbrite event URLs or Eventbrite discovery URLs. Example: https://www.eventbrite.com/e/example-tickets-123456789.

## `maxResults` (type: `integer`):

Maximum unique events to return across all inputs. Defaults to 25; maximum 200.

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

Optional Eventbrite time filter for discovery searches.

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

Optional category or refinement passed to the Eventbrite discovery page.

## `includeDescription` (type: `boolean`):

Include the public event description when available. Defaults to true.

## `includeOrganizer` (type: `boolean`):

Include public organizer name and URL when available. Defaults to true.

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

Optional Apify proxy configuration. Use a residential proxy only when Eventbrite blocks direct access.

## Actor input object example

```json
{
  "searchQueries": [],
  "location": "new-york",
  "startUrls": [
    {
      "url": "https://www.eventbrite.com/e/tech-connect-networking-for-tech-startups-investors-professionals-nyc-tickets-1993825320205"
    }
  ],
  "maxResults": 25,
  "dateFilter": "all",
  "category": "",
  "includeDescription": true,
  "includeOrganizer": true,
  "proxyConfiguration": {}
}
```

# Actor output Schema

## `datasetId` (type: `string`):

Dataset containing event records.

## `summaryKey` (type: `string`):

Key-value store key containing run summary diagnostics.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("muhammadafzal/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 = {}

# Run the Actor and wait for it to finish
run = client.actor("muhammadafzal/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 '{}' |
apify call muhammadafzal/eventbrite-event-scraper --silent --output-dataset

```

## MCP server setup

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