# Luma Events Scraper — lu.ma Events by City, Topic or Organizer (`northbell/luma-events-scraper`) Actor

Scrape Luma (lu.ma) events in 87 cities, by topic (AI, tech, crypto, climate and more) or from any organizer calendar: date, venue, full address, coordinates, organizer, guest count, price, sold-out and approval status, optional description. Only new events since your last run.

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

## Pricing

from $1.20 / 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

## Luma Events Scraper — lu.ma Events by City, Topic or Organizer

Get the events listed on **Luma (lu.ma)** — the platform most tech, AI, startup and crypto communities use for meetups, demo nights and conferences — as clean JSON: **name, start and end time, venue, full address, coordinates, organizer, guest count, price, sold-out and approval status**, and optionally the **description**.

Pick events three ways: by **city** (87 Luma cities, from San Francisco and New York to London, Tokyo and Singapore), by **topic** around a city (AI, tech, crypto, climate, arts, food, fitness, wellness, books, games, family, running), or from any **organizer calendar** (`lu.ma/<name>`). Schedule it with *Only new events* and each run returns just the events added since the last one.

### What you get

| Field | What it is |
|---|---|
| `name`, `url`, `startAt`, `endAt`, `timezone` | the event |
| `locationType`, `venue`, `address`, `city`, `region`, `country`, `countryCode`, `latitude`, `longitude` | where (online events have no venue; some organizers show the address to guests only) |
| `organizer`, `organizerUrl` | the community or company calendar that runs it |
| `hosts` | the host names shown on the event |
| `guestCount` | how many people registered |
| `isFree`, `price`, `currency`, `soldOut`, `spotsRemaining`, `requiresApproval`, `waitlist` | tickets |
| `description` | with *Include the event description* |
| `source`, `isNewSinceLastRun` | which city / topic / calendar it came from, and whether it is new since your last run |

`hosts` lists the host names shown on the event. Hosts' social handles and guest lists are **not** collected.

### Use it for

- **Event discovery** — every AI or crypto event in your city for the next two weeks, in one sheet
- **Sponsorship and sales** — which communities run the biggest events, where, and how often
- **Community and market research** — event counts, guest counts and paid vs free across 87 cities
- **Alerts** — schedule daily with *Only new events* and send new listings to Slack or email

### Input

```json
{ "cities": ["sf", "nyc"], "categories": ["ai"], "startsWithinDays": 14 }
```

Measured on October 7, 2026: San Francisco, Tokyo and São Paulo city pages returned 127 events in 2.4 seconds; San Francisco AI and crypto with descriptions, 67 events in 26 seconds. Data comes from Luma's public event listings — no login.

### Pricing

**$1.50 per 1,000 events**, plus $0.01 per run. Error rows and events left out by your filters are free. The $0.01 run-start fee is the one charge every run pays, even one that returns nothing.

### For AI agents

`{"cities": ["london"], "categories": ["tech"], "startsWithinDays": 7}` returns next week's London tech events. Rows have `type`: `event` or `error`.

# Actor input Schema

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

Luma city pages by name or short name: "sf", "nyc", "London", "Tokyo", "Berlin", "Singapore" … (87 cities; an unknown name returns the full list).

## `categories` (type: `array`):

With topics, each city returns that topic's events around it instead of the whole city page.

## `calendars` (type: `array`):

lu.ma/<name> links of organizers or communities. Returns their upcoming events.

## `startsWithinDays` (type: `integer`):

Keep only events that start within this many days from now. Leave empty for every upcoming event.

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

Keep events whose name or organizer contains any of these.

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

Skip paid events.

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

How many events to return for each city, topic or calendar you enter.

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

One extra request per event.

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

From the second run on, return only events this Actor has not returned before for the same city, topic or calendar.

## Actor input object example

```json
{
  "cities": [
    "sf"
  ],
  "freeOnly": false,
  "maxEventsPerSource": 100,
  "includeDescription": false,
  "onlyNew": false
}
```

# Actor output Schema

## `events` (type: `string`):

Events with date, venue, organizer, guest count and price.

# 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": [
        "sf"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/luma-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": ["sf"] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/luma-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": [
    "sf"
  ]
}' |
apify call northbell/luma-events-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/luma-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/8zOr7kudKDpy42Hv2/builds/2vuOEhOpfDvxOhkX9/openapi.json