# Eventbrite Scraper: Events from Eventbrite, Meetup and Luma (`oski/events-scraper`) Actor

Scrape events from Eventbrite, Meetup and Luma in one run. Type a city or keyword and get event name, date and time, venue, address, organiser, price, ticket link and online or in-person flag, deduplicated across the three sites. No login, no API key. Pay per event, $3 per 1,000.

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

## Pricing

from $2.91 / 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.
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 (plus Meetup and Luma)

Upcoming events for any city from Eventbrite, Meetup and Luma in one table: name, date and time, venue and address, organiser, price, free flag, online flag, image and link. Pay only for events delivered. No login, no browser, no API key.

Tired of event scrapers that fail one run in ten (the two busiest Eventbrite actors on the Store fail 9% and 12% of their runs), or that cover one platform and stop at the first page? This one reads the three platforms' own data feeds, merges them, keeps an event listed twice only once, and ends every run with a plain status line that says what came back from each source and why.

### What you get

One row per event:

| Field | Example |
|---|---|
| `source` | eventbrite, meetup or luma |
| `name`, `url` | Django London Meetup October, the event page |
| `start`, `end`, `timezone` | 2026-10-14T18:15:00+01:00, Europe/London |
| `is_online` | false |
| `venue_name`, `address`, `city`, `country`, `lat`, `lon` | Kraken, 182 Oxford Street, London, GB |
| `organizer`, `organizer_url`, `organizer_followers` | Django London, meetup.com/djangolondon, 3095 (Eventbrite) |
| `price_min`, `price_max`, `currency`, `is_free` | 85.0, 85.0, GBP, false |
| `sold_out`, `spots_remaining` | false, 7 (Luma shows spots where the host does) |
| `category_tags` | \["Health & Wellness", "Beauty"] (Eventbrite) |
| `image`, `description` | cover image, short summary |
| `attendees` | 70 (Meetup RSVPs, Luma guest count) |
| `search_city`, `search_keywords`, `scraped_at` | what you asked for and when |

Plus one free `SUMMARY` row per city: events delivered, requested, available, count per source, and a reason whenever a source returned nothing.

### Use cases

- **Event discovery apps and newsletters:** every upcoming event in a city, refreshed daily.
- **Venue and sponsor prospecting:** organisers who run paid events, with follower counts.
- **Market research:** how many tech, music or fitness events a city hosts each month, and what they charge.
- **Competitor tracking:** keyword searches such as "startup" or "yoga" across three platforms at once.
- **Travel content:** "what's on this weekend in Lisbon" tables built from the `this_weekend` range.

### How to use it

1. Type your cities, one per line ("London", or "London, CA" to pick the country per city), or paste an Eventbrite search link (eventbrite.com/d/<country--city>/<category>/), a Meetup find link or a Luma city link. Links to a single event page are declined with a note; search by city instead.
2. Optional: add keywords, pick a date range, turn off online events or keep only free ones. Keywords run each platform's own relevance search, so results relate to the keyword but do not all contain it; Luma has no keyword search and is filtered on the event name.
3. Set how many events you want per city.
4. Start the run. Download the dataset as JSON, CSV or Excel, or read it through the API.

### What each source gives

| Source | Per request | How far it goes | Filters honoured |
|---|---|---|---|
| Eventbrite | 50 events | up to 1,000 per search (20 pages), paged | date range, keywords, free only |
| Meetup | 20 to 50 events | one page per keyword (add keywords for more; the status line says when more exist) | keywords, date range (filtered by start date) |
| Luma | 25 events | paged to the end of the city's list | keywords (matched on the name), date range (filtered by start date) |

Cities without a Luma city page (smaller towns) show "Luma has no city page for it" in the summary. Online events are included unless you turn them off; the `is_online` column tells them apart.

### Cost

| Events delivered | Cost |
|---|---|
| 100 | about $0.30 |
| 1,000 | about $3.00 |
| 10,000 | about $30 |

A small fee per run plus a fee per event delivered (the table assumes $0.003 per event). An event listed on two platforms is counted once. A city or source that returns nothing adds nothing but the run fee.

### Scheduling and API

Schedule it in the Apify console (Schedules > Create) or call it:

```bash
curl -X POST "https://api.apify.com/v2/acts/oski~events-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"cities": ["London"], "keywords": ["jazz"], "dateRange": "this_month", "maxEventsPerCity": 200}'
```

### If something looks wrong

| Status line says | What it means | What to do |
|---|---|---|
| Input problem: Add at least one city | The cities field was empty | Add a city or paste a link |
| Input problem: "Date range" must be one of ... | A typed value is not one of the presets | Pick one from the list |
| Eventbrite refused the request | Eventbrite would not hand out a session from that exit | Run again; if it repeats, choose the RESIDENTIAL proxy group |
| Luma has no city page for it | Luma only has pages for about 90 cities | Nothing to do; Eventbrite and Meetup still cover the city |
| Meetup listed no events for it | Meetup found no events for that city or keyword | Check the country setting; try the city name Meetup uses |
| Fewer events than asked for: London (120 of 500, 179 found) | The sources ran out for that search | Add keywords to split a big city (Eventbrite answers 1,000 per search), or widen the date range |
| Eventbrite links of that kind cannot be fetched yet | A single-event or browse link was pasted | Paste a search link (eventbrite.com/d/...) or type the city |
| Luma listed events, but none matched your keywords | Luma is filtered on the event name | Drop the keyword for Luma, or run Luma without keywords in a second run |

### Frequently asked questions

**Why is the same event in two rows?** It is not, unless the names or start times differ between platforms. Exact name-and-start matches are kept once.

**Can I filter by exact dates?** The presets (today, tomorrow, this weekend, this week, next week, this month, next month) apply to all three sources: Eventbrite natively, Meetup and Luma by start date. For a custom window, run "All upcoming" and filter the `start` column.

**Does it read ticket availability?** Eventbrite rows carry min and max ticket price, the free flag and `sold_out`; Luma rows carry `sold_out` and `spots_remaining` where the host shows them.

**Is it legal?** It reads publicly listed events without logging in and stores no personal data about attendees.

### Related actors by the same developer

- Google Hotels Prices Scraper
- Google Jobs Scraper
- Website Contact Finder

# Actor input Schema

## `cities` (type: `array`):

One city per line, as people write it. Add the country after a comma to pick it per city (London, CA). A pasted Eventbrite search link (eventbrite.com/d/<country--city>/<category>/), Meetup find link or Luma city link is read as that one source; links to a single event are declined with a note.

## `keywords` (type: `array`):

Narrow each city to events related to these words. Each keyword is a separate Eventbrite and Meetup relevance search (results relate to the keyword, not all contain it); Luma is filtered on the event name. Keywords are also the way to get more than one page of Meetup results.

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

Which platforms to read. All three by default; results are merged and the same event listed twice is kept once.

## `dateRange` (type: `string`):

Eventbrite applies the preset itself; Meetup and Luma results are filtered to the same calendar window by start date.

## `includeOnline` (type: `boolean`):

Turn off to keep only in-person events.

## `freeOnly` (type: `boolean`):

Keep only events marked free.

## `maxEventsPerCity` (type: `integer`):

Stop a city after this many unique events across the chosen sources, balanced between them. 500 events cost about $1.50. Eventbrite answers at most 1,000 per search; add keywords to split a big city.

## `country` (type: `string`):

The country the cities are in; Meetup needs it to find the right city.

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

Apify datacenter proxy is enough for all three sources (tested clean). Choose RESIDENTIAL only if a source starts refusing.

## `maxPagesPerSource` (type: `integer`):

Safety cap on result pages fetched per source (Eventbrite 50 events a page, Luma 25).

## `concurrency` (type: `integer`):

How many cities run in parallel.

## Actor input object example

```json
{
  "cities": [
    "Berlin",
    "New York",
    "https://lu.ma/london",
    "https://www.eventbrite.com/d/ny--new-york/music/"
  ],
  "keywords": [
    "jazz",
    "python",
    "startup"
  ],
  "sources": [
    "eventbrite",
    "meetup",
    "luma"
  ],
  "dateRange": "current_future",
  "includeOnline": true,
  "freeOnly": false,
  "maxEventsPerCity": 200,
  "country": "GB",
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "maxPagesPerSource": 40,
  "concurrency": 3
}
```

# Actor output Schema

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

One row per event: name, source, date and time, venue, city, organiser, price, online flag and ticket link; plus one free SUMMARY row per city.

## `allFields` (type: `string`):

Every field for each event, including description, address, coordinates, categories and ticket details.

# 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 = {
    "cities": [
        "London",
        "Manchester"
    ],
    "maxEventsPerCity": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("oski/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 = {
    "cities": [
        "London",
        "Manchester",
    ],
    "maxEventsPerCity": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("oski/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 '{
  "cities": [
    "London",
    "Manchester"
  ],
  "maxEventsPerCity": 200
}' |
apify call oski/events-scraper --silent --output-dataset

```

## MCP server setup

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