# Events Scraper — Eventbrite, Meetup & Luma (`workstream/events-scraper`) Actor

One Actor for Eventbrite, Meetup and Luma. Search by keyword and city; get title, dates, venue, address, price, tickets URL and source in one normalized schema. Run all three platforms or pick what you need.

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

## Pricing

$1.00 / 1,000 events

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

## Events Scraper — Eventbrite, Meetup & Luma

One Actor for the three biggest public event platforms. Search by **keyword and city**; get a normalized feed of events with dates, venues, prices and ticket links.

### Who this is for

- Event aggregators and city guides
- Local lead generation (meetups, tech events)
- Community and campus tools
- Sales teams tracking industry events

### What you get (same shape for every source)

`source, id, title, url, summary, startDate, endDate, timezone, isOnline, venue, address, city, country, latitude, longitude, image, price, currency, ticketsUrl, group/hosts`

### Input example

```json
{
  "searches": [
    {"query": "tech", "city": "New York"},
    {"query": "startup", "city": "San Francisco", "sources": ["luma", "eventbrite"]}
  ],
  "maxEventsPerSource": 50
}
```

### Pricing

**$0.001 per event** ($1.00 / 1,000). No start fee. Replaces three separate Actors.

### FAQ

**Luma cities?** ~85 cities from Luma Discover (NYC, SF, London, Berlin, Dubai, Tokyo…). Unsupported cities return a clear error.
**Why one Actor?** Competitors are split one-site-per-Actor; this returns a single normalized schema across Eventbrite, Meetup and Luma.

# Actor input Schema

## `searches` (type: `array`):

List of {query, city, sources?}. Sources default to all three.

## `query` (type: `string`):

Used with city when searches is empty.

## `city` (type: `string`):

e.g. New York, London, San Francisco, Berlin.

## `sources` (type: `array`):

Which platforms to search: eventbrite, meetup, luma.

## `maxEventsPerSource` (type: `integer`):

Per platform, per search.

## `lumaKeywordFilter` (type: `boolean`):

Luma lists all events in a city; turn on to keep only events whose title contains a keyword word.

## Actor input object example

```json
{
  "searches": [
    {
      "query": "tech",
      "city": "New York"
    },
    {
      "query": "startup",
      "city": "San Francisco"
    }
  ],
  "query": "tech",
  "city": "New York",
  "sources": [
    "eventbrite",
    "meetup",
    "luma"
  ],
  "maxEventsPerSource": 30,
  "lumaKeywordFilter": false
}
```

# Actor output Schema

## `results` (type: `string`):

Scraped items

## `summary` (type: `string`):

Counts and errors per input

# 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 = {
    "searches": [
        {
            "query": "tech",
            "city": "New York"
        },
        {
            "query": "startup",
            "city": "San Francisco"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("workstream/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 = { "searches": [
        {
            "query": "tech",
            "city": "New York",
        },
        {
            "query": "startup",
            "city": "San Francisco",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("workstream/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 '{
  "searches": [
    {
      "query": "tech",
      "city": "New York"
    },
    {
      "query": "startup",
      "city": "San Francisco"
    }
  ]
}' |
apify call workstream/events-scraper --silent --output-dataset

```

## MCP server setup

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