# Eventbrite Scraper (`coder_zoro/eventbrite-scraper`) Actor

Scrapes Eventbrite URLs to fetch event details, images, and ticket info. Pushes AWS API response directly to dataset without modification.

- **URL**: https://apify.com/coder_zoro/eventbrite-scraper.md
- **Developed by:** [Zoro](https://apify.com/coder_zoro) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 110 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.99 / 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.
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 – Apify Actor

This Apify Actor is designed to **scrape Eventbrite data** efficiently. It supports both **individual event pages** and **event listings** with automatic URL-type detection.

***

### Overview

| Feature             | Description                                                          |
| ------------------- | -------------------------------------------------------------------- |
| **Platform**        | Eventbrite                                                           |
| **Purpose**         | Extract event details or event listings data                         |
| **Output Format**   | JSON, CSV, or Excel (via Apify Dataset)                              |
| **Automation Type** | Apify Actor                                                          |
| **Use Case**        | Market research, event monitoring, data analysis, or lead generation |

***

### How It Works

The scraper automatically determines whether the input URL is an **event detail page** or a **search results page** and extracts data accordingly.

#### 1. Event Detail URL

When you provide a direct event URL such as:

```
https://www.eventbrite.com/e/haunt-massive-tickets-1736141428749
```

The scraper collects and returns all available details for that specific event, including title, date, location, and link.

***

#### 2. Search Results URL

If you input a search page URL such as:

```
https://www.eventbrite.com/d/ny--new-york/events--today/business/?page=1
```

The scraper navigates through multiple pages to collect multiple event listings. You can control pagination using the `max_page_number` field.

**Example Input:**

```json
{
  "input_url": "https://www.eventbrite.com/d/ny--new-york/events--today/business/?page=1",
  "max_page_number": 5
}
```

If `max_page_number` is not provided, it defaults to **3** pages.

***

### Input Configuration

| Field             | Type    | Required | Description                                                   |
| ----------------- | ------- | -------- | ------------------------------------------------------------- |
| `input_url`       | string  | Yes      | The Eventbrite URL (event or search page)                     |
| `max_page_number` | integer | No       | Number of pages to scrape (only for search pages, default: 3) |

***

### Example Output

Below is an example of the structured JSON output stored in the Apify Dataset:

```json
[
  {
    "title": "NYC Tech Mixer",
    "date": "2025-10-25",
    "url": "https://www.eventbrite.com/e/nyc-tech-mixer-tickets-123456789"
  },
  {
    "title": "Startup Summit 2025",
    "date": "2025-11-01",
    "url": "https://www.eventbrite.com/e/startup-summit-2025-tickets-987654321"
  }
]
```

***

### Output Format Options

| Format           | Description                              |
| ---------------- | ---------------------------------------- |
| **JSON**         | Structured data for APIs or integrations |
| **CSV**          | Ideal for Excel or spreadsheet analysis  |
| **Excel (XLSX)** | Easy for reporting and manual review     |

All outputs are accessible through the **Apify Dataset** section.

***

### Key Features

| Feature                     | Benefit                                                       |
| --------------------------- | ------------------------------------------------------------- |
| **Automatic URL Detection** | Identifies whether the URL is an event or search results page |
| **Pagination Handling**     | Scrapes multiple pages when applicable                        |
| **Asynchronous Execution**  | Ensures faster data extraction                                |
| **Clean Data Output**       | Provides well-structured JSON or CSV data                     |
| **Flexible Input**          | Works with any valid Eventbrite URL                           |

***

### Example Use Cases

| Use Case                | Description                                          |
| ----------------------- | ---------------------------------------------------- |
| **Market Research**     | Analyze trends in events across cities or categories |
| **Lead Generation**     | Collect event organizers and attendee data           |
| **Competitor Tracking** | Monitor events hosted by competitors                 |
| **Data Analysis**       | Export and visualize event data in reports           |

***

### Notes

- The scraper runs fully within the Apify platform.
- Automatically detects event type and adapts extraction logic.
- Default pagination limit is 3 pages (configurable).
- Produces structured, ready-to-use JSON or CSV output.

# Actor input Schema

## `input_url` (type: `string`):

A search/discovery URL (contains '/d/') to collect event links, or a single event URL (contains '/e/') to scrape full details.

## `max_page_number` (type: `integer`):

How many result pages to paginate through when the input is a '/d/' search URL. Ignored for single '/e/' event URLs.

## `scrape_details` (type: `boolean`):

When the input is a search URL, also visit each discovered event and scrape its full details (organizer, tickets, description, map). Slower but richer output.

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

Hard cap on the number of events pushed to the dataset per run. Protects against runaway cost.

## `requestTimeoutSecs` (type: `integer`):

Per-request HTTP timeout in seconds.

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

Select proxies to use for requests. Helps avoid IP blocking and rate limits. Residential proxies are recommended for Eventbrite as it blocks datacenter IPs aggressively.

## Actor input object example

```json
{
  "input_url": "https://www.eventbrite.com/e/some-event-tickets-1977106150719",
  "max_page_number": 3,
  "scrape_details": false,
  "maxItems": 100,
  "requestTimeoutSecs": 30,
  "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 = {
    "input_url": "https://www.eventbrite.com/e/haunt-massive-tickets-1736141428749",
    "max_page_number": 3,
    "maxItems": 100,
    "requestTimeoutSecs": 30,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("coder_zoro/eventbrite-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 = {
    "input_url": "https://www.eventbrite.com/e/haunt-massive-tickets-1736141428749",
    "max_page_number": 3,
    "maxItems": 100,
    "requestTimeoutSecs": 30,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("coder_zoro/eventbrite-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 '{
  "input_url": "https://www.eventbrite.com/e/haunt-massive-tickets-1736141428749",
  "max_page_number": 3,
  "maxItems": 100,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call coder_zoro/eventbrite-scraper --silent --output-dataset

```

## MCP server setup

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