# Luma Events Scraper - All Events by City & Date (`nohanml/luma-events-scraper`) Actor

- **URL**: https://apify.com/nohanml/luma-events-scraper.md
- **Developed by:** [Nohan Marie-Louise](https://apify.com/nohanml) (community)
- **Stats:** 3 total users, 2 monthly users, 94.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 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.

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 — All Events by City, Category & Date

Search [Luma](https://luma.com) for **every** event around a city, not just the handful Luma
features on its own city pages. Filter by category and date range, and get clean, structured
results: dates and timezone, geolocated venue, organizer, hosts, and ticket prices — no HTML to
parse, no Luma event ID to guess.

Turn on **Include details** to also get each event's categories, ticket types, and a short
summary.

### Input example

```json
{
    "city": "New York",
    "category": "tech",
    "dateRange": "this_week",
    "maxItems": 100,
    "includeDetails": true
}
```

Searching somewhere outside Luma's own cities? Use **Latitude / Longitude (advanced)** instead of
`city` — it replaces it.

### Output example

A real result (captured on 2026-10-03), with **Include details** turned off:

```json
{
    "id": "evt-OJTU4NRIFfK7Be0",
    "url": "https://luma.com/t29u1kdw",
    "name": "Make It in Brooklyn Grid Futures Panel",
    "startDate": "2026-10-06",
    "startTime": "18:00",
    "endDate": "2026-10-06",
    "endTime": "20:00",
    "timezone": "America/New_York",
    "isOnline": false,
    "venue": {
        "name": "Hana House",
        "address": "Hana House, 345 Adams St, Brooklyn, NY 11201, USA",
        "city": "Brooklyn",
        "region": "New York",
        "country": "United States",
        "countryCode": "US",
        "latitude": 40.692398999999995,
        "longitude": -73.98844160000002,
        "isAddressPublic": true
    },
    "organizer": {
        "name": "Downtown Brooklyn Partnership",
        "url": "https://luma.com/calendar/cal-PStLt0TLTfw9IoW"
    },
    "hosts": [
        {
            "name": "Downtown Brooklyn Partnership",
            "url": "https://luma.com/user/usr-FHe3wOWVLssJBaf"
        }
    ],
    "tickets": {
        "isFree": true,
        "minPrice": 0.0,
        "maxPrice": 0.0,
        "currency": null,
        "isSoldOut": false,
        "spotsRemaining": null,
        "requiresApproval": false
    },
    "registrationStatus": "open",
    "guestCount": 0,
    "imageUrl": "https://images.lumacdn.com/uploads/j6/13751efe-b2b4-431a-9f5b-3ffc4ee10c35.png",
    "searchCenter": {
        "latitude": 40.73061,
        "longitude": -73.935242,
        "city": "New York"
    },
    "scrapedAt": "2026-10-03T16:46:17+00:00"
}
```

The same event, with **Include details** turned on, also gets:

```json
{
    "categories": [
        "Climate",
        "Tech"
    ],
    "ticketTypes": [
        {
            "name": "Standard",
            "price": 0.0,
            "currency": null,
            "isSoldOut": false
        }
    ],
    "summary": "New York’s energy transition depends on a more flexible, resilient electric grid. As more buildings become fully electric and electricity demand grows, the network that delivers power across the city must evolve to integrate clean energy, support new technologies, and remain reliable during periods…"
}
```

`categories`, `ticketTypes` and `summary` are only present with **Include details** turned on, and
only for the events whose page was read successfully.

### Pricing

Pay-per-event, no subscription:

| Event | Price |
| --- | --- |
| Event | $0.003 |
| Event, with details (`includeDetails`) | +$0.005 |

Example: 100 events with details cost $0.80 (100 × ($0.003 + $0.005)).

### FAQ

**Why a full search instead of Luma's own city pages?**
Luma's city pages only show a curated selection — a dozen events for a typical city, sometimes
just a handful. This Actor searches everything Luma's own map knows about around your point:
often ten times more events for a big city like New York.

**How big is the search area?**
Luma's search returns events up to roughly 70 km around the point (measured around New York). The
radius is Luma's own: this Actor can't widen or narrow it.

**Why is a venue's address sometimes missing?**
Some hosts restrict the exact address to registered guests. This Actor never reconstructs it: you
get exactly what Luma makes public (`venue.isAddressPublic: false`, with `name`, `address`,
`latitude` and `longitude` left empty), plus the city, region and country Luma still shows.

**Does this include the guest list?**
No, never — only the host(s) who run the event, reduced to their name and public profile URL. No
avatar, bio or social links either, for hosts or anyone else. `guestCount` is a plain number of
registered guests, nothing more.

**What's in `summary`?**
Luma's own event description, truncated to 300 characters. Never the full description.

**What data does this Actor collect?**
Only what Luma already shows on its public discovery page and event pages — no login, no account,
no private data.

**`registrationStatus` says "sold-out" but `tickets.spotsRemaining` isn't 0 — is that a bug?**
No, that's how Luma reports some events: a closed registration (`sold-out`) while a few spots
still show as remaining. This Actor passes `registrationStatus` and `tickets` through exactly as
Luma reports them.

**How do I get new events automatically, every week?**
Save your input as a task, then add that task to a schedule in Apify Console (**Schedules**). For
example, run your city with `dateRange` set to "Next week" every Friday. Each run is billed like
any other, per event returned.

**Can I get more than the default 100 events?**
Yes, raise `maxItems`. The run stops at `maxItems`, at your Actor budget, or when Luma's search
runs out of results — whichever comes first.

**Known limitations**

- Only Luma's own short description is returned, truncated to 300 characters.
- Only one location per run: to cover several cities, run the Actor once per city.

### Disclaimer

This Actor is not affiliated with, endorsed by, or sponsored by Luma. It only reads Luma's public
pages. You are responsible for how you use the data it returns, and for complying with the laws
and terms that apply to you.

# Actor input Schema

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

Name or slug of a Luma city (e.g. "New York", "zurich"), matched without case or accents. Ignored if latitude/longitude are set.

## `category` (type: `string`):

Restricts results to a Luma category.

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

Restricts results to a period, computed in each event's own timezone.

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

Stops the search after this many events (deduplicated). The run also stops on your Actor budget, if lower.

## `includeDetails` (type: `boolean`):

Opens each event's page for its categories, ticket types, and a short summary. Adds $0.005 per detailed event.

## `latitude` (type: `number`):

Search around these coordinates instead of city. Must be given together with longitude; replaces city when set. Use this for a place outside Luma's own 87 cities.

## `longitude` (type: `number`):

Search around these coordinates instead of city. Must be given together with latitude; replaces city when set.

## Actor input object example

```json
{
  "city": "New York",
  "category": "",
  "dateRange": "anytime",
  "maxItems": 100,
  "includeDetails": false
}
```

# Actor output Schema

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

One item per event, deduplicated. Opens the overview table (name, date, city, organizer, free or not, link).

# 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 = {
    "city": "New York"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nohanml/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 = { "city": "New York" }

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

```

## MCP server setup

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