# Unified Events Scraper: Eventbrite, Meetup & Luma (`informed_almandine_vzb/unified-events-feed`) Actor

Scrape Eventbrite, Meetup, and Luma events into one deduplicated JSON/CSV schema: dates, venue, geo coordinates, organizer, price, and RSVPs.

- **URL**: https://apify.com/informed_almandine_vzb/unified-events-feed.md
- **Developed by:** [Almandine Data](https://apify.com/informed_almandine_vzb) (community)
- **Categories:** Lead generation, Marketing, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 event scrapeds

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?

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

## Unified Events Scraper: Eventbrite, Meetup & Luma

Scrape Eventbrite, Meetup, and Luma events into one deduplicated JSON/CSV schema: dates, venue, geo coordinates, organizer, price, and RSVPs.

### What it does

One run pulls public event listings from Eventbrite, Meetup and Luma for your cities and keyword, normalizes them to one schema and removes cross-posted duplicates (same title + same day). Export clean, deduplicated data as **JSON, CSV, Excel, XML, or RSS**, or connect directly via the **Apify REST API, Python/JavaScript SDKs, CLI, MCP Server, n8n, Make, or Zapier** — with **no login, cookies, or browser overhead**.

### Use cases

- **City & Industry Event Aggregators:** Pull tech, startup, AI, or local events from Eventbrite, Meetup, and Luma in a single run with automatic cross-platform deduplication.
- **Event Sponsorship & Organizer Lead Gen:** Identify active event organizers, venues, ticket pricing, and RSVP traction across target cities.
- **Automated Community Newsletters:** Schedule weekly runs with `onlyNew: true` to feed curated local or niche event digests.
- **Sales & Conference Intelligence:** Track side events, meetups, and workshops happening around major industry conferences.

### Why use this scraper?

| Feature | This Actor | Generic Browser / HTML Scrapers |
|---|---|---|
| **Architecture** | Direct structured API / JSON / feed requests (`curl_cffi`) | Heavy headless browser automation |
| **Speed & reliability** | **2–25 seconds** for 50–200 items | Minutes of high compute burn |
| **Pricing model** | **Pay per result (`$0.00` actor-start fee)** | Monthly rental or high CU overhead |
| **Error handling** | Failed inputs logged in `ERRORS` key-value record and **never charged** | Bills compute time even on failures |

### Input parameters

- **Keyword** (`keyword`, `string`): Topic to search for, e.g. 'ai', 'yoga', 'startup'. Leave empty for all events. Luma pages are filtered by title.
- **Eventbrite locations** (`eventbriteLocations`, `array`): Eventbrite location slugs as they appear in eventbrite.com/d/<slug>/ URLs, e.g. 'ca--san-francisco', 'ny--new-york', 'united-kingdom--london'.
- **Eventbrite pages per location** (`eventbritePages`, `integer`): Each page has about 20 events.
- **Meetup locations** (`meetupLocations`, `array`): Meetup location codes as in meetup.com/find/?location=..., e.g. 'us--ca--San Francisco', 'gb--17--London'.
- **Luma cities** (`lumaCities`, `array`): Luma city page slugs (luma.com/<slug>), e.g. 'sf', 'nyc', 'london', 'berlin'.
- **Max events** (`maxItems`, `integer`): Stop after this many unique events (you are charged per event).
- **Only new events** (`onlyNew`, `boolean`): On scheduled runs, return only events not seen in earlier runs (state kept in a named key-value store).
- **Delay between requests** (`delaySeconds`, `number`): Polite pause between requests (default `0.7`).

#### Example input

```json
{
  "keyword": "ai",
  "eventbriteLocations": [
    "ca--san-francisco"
  ],
  "meetupLocations": [
    "us--ca--San Francisco"
  ],
  "lumaCities": [
    "sf"
  ]
}
```

### Output & example output

One dataset row per result. Default table view columns: `imageUrl, source, title, startAt, city, venueName, organizerName, isOnline, isFree, rsvpCount, url`. Full structured JSON is stored in the run's default dataset.

#### Example output item

```json
{
  "source": "eventbrite",
  "eventId": "2003316175609",
  "url": "https://www.eventbrite.com/e/ai-security-securing-the-age-of-autonomous-ai-tickets-2003316175609",
  "title": "AI & Security: Securing the Age of Autonomous AI",
  "description": "Join us in person to explore how to secure autonomous AI and stay ahead of emerging threats.",
  "startAt": "2026-10-28",
  "endAt": "2026-10-28",
  "timezone": null,
  "isOnline": false,
  "venueName": "Orrick",
  "address": "405 Howard Street, San Francisco, CA, 94105",
  "city": "San Francisco",
  "country": "US",
  "lat": 37.7884819,
  "lng": -122.3950928,
  "organizerName": null,
  "organizerUrl": null,
  "isFree": null,
  "price": null,
  "imageUrl": "https://img.evbuc.com/https%3A%2F%2Fcdn.evbuc.com%2Fimages%2F1195641029%2F68009401515%2F1%2Foriginal.20261012-211437?crop=focalpoint&fit=crop&w=355&auto=format%2Ccompress&q=75&s...",
  "rsvpCount": null,
  "dedupeKey": "7982f714cdd01ef45d59d3d9d4ac0000",
  "scrapedAt": "2026-10-25T04:27:01+00:00"
}
```

### Pricing (Pay-Per-Result)

This Actor uses transparent **Pay-Per-Event** pricing with a **`$0.00` actor-start fee**:

| Event | What is charged | Price |
|---|---|---|
| `event-result` | Event scraped (One unique event in the unified schema) | **$0.004 / result** (**$4.00 / 1,000 results**) |
| `apify-actor-start` | Actor start fee | **$0.00** |

#### Concrete pricing math

- **`event-result` (Event scraped):** `1,000 results = $4.00` (`50 results = $0.20`, `10,000 results = $40.00`). Apify's **$5.00/month Free Tier** covers up to **1,250 results/month** at **$0.00** out-of-pocket.
- **Empty runs (`0` results) & skipped duplicates (`onlyNew` / `onlyChanged`):** **$0.00**.

### Data and compliance

Public event pages only. No attendee or guest lists, no personal data about attendees. Requests are rate-limited and routed through Apify Proxy. Per-input errors are recorded in the run's `ERRORS` key-value record and are never charged.

### FAQ

**Do I need an account, login, or API key?**\
No. This Actor queries public endpoints directly and requires zero credentials.

**What happens if I start a run with empty `{}` input via API or CLI?**\
Every required input defines both `prefill` and `default` values in `.actor/input_schema.json`, so an empty `{}` run automatically returns **50+ live records** out of the box.

# Actor input Schema

## `keyword` (type: `string`):

Topic to search for, e.g. 'ai', 'yoga', 'startup'. Leave empty for all events. Luma pages are filtered by title.

## `eventbriteLocations` (type: `array`):

Eventbrite location slugs as they appear in eventbrite.com/d/<slug>/ URLs, e.g. 'ca--san-francisco', 'ny--new-york', 'united-kingdom--london'.

## `eventbritePages` (type: `integer`):

Each page has about 20 events.

## `meetupLocations` (type: `array`):

Meetup location codes as in meetup.com/find/?location=..., e.g. 'us--ca--San Francisco', 'gb--17--London'.

## `lumaCities` (type: `array`):

Luma city page slugs (luma.com/<slug>), e.g. 'sf', 'nyc', 'london', 'berlin'.

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

Stop after this many unique events (you are charged per event).

## `onlyNew` (type: `boolean`):

On scheduled runs, return only events not seen in earlier runs (state kept in a named key-value store).

## `delaySeconds` (type: `number`):

Polite pause between requests.

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

Apify Proxy settings.

## Actor input object example

```json
{
  "keyword": "ai",
  "eventbriteLocations": [
    "ca--san-francisco"
  ],
  "eventbritePages": 1,
  "meetupLocations": [
    "us--ca--San Francisco"
  ],
  "lumaCities": [
    "sf"
  ],
  "maxItems": 200,
  "onlyNew": false,
  "delaySeconds": 0.7,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

No description

## `results` (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 = {
    "keyword": "ai",
    "eventbriteLocations": [
        "ca--san-francisco"
    ],
    "meetupLocations": [
        "us--ca--San Francisco"
    ],
    "lumaCities": [
        "sf"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("informed_almandine_vzb/unified-events-feed").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 = {
    "keyword": "ai",
    "eventbriteLocations": ["ca--san-francisco"],
    "meetupLocations": ["us--ca--San Francisco"],
    "lumaCities": ["sf"],
}

# Run the Actor and wait for it to finish
run = client.actor("informed_almandine_vzb/unified-events-feed").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 '{
  "keyword": "ai",
  "eventbriteLocations": [
    "ca--san-francisco"
  ],
  "meetupLocations": [
    "us--ca--San Francisco"
  ],
  "lumaCities": [
    "sf"
  ]
}' |
apify call informed_almandine_vzb/unified-events-feed --silent --output-dataset

```

## MCP server setup

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

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/cPR0AKSITdDgOuG8y/builds/12CfIAa3Ao4okmYlw/openapi.json