# Luma (lu.ma) Events Scraper (`soogrow_berries/luma-events-scraper`) Actor

Upcoming events from Luma city and category pages: name, time, place, price, open or sold out, guest count, organizer and hosts.

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

## Pricing

$2.16 / 1,000 event saveds

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 (lu.ma) Events Scraper

Get events from Luma's city and category discovery pages, one row per event.

**Verified 16 October 2026:** private cloud tests passed for the 20-event preset, result charging, spending limits and output links. These are bounded checks.

### New York: see the output

Start with the New York preset to build an event shortlist, then export JSON/CSV or use the API recipe below.

Three real records from a 20-event verification run on 16 October 2026. This is captured sample output; event details and availability can change.

| Event | Starts (UTC) | City | Ticket | Availability |
| --- | --- | --- | --- | --- |
| [Aleph x Corgi Run Club NYC](https://luma.com/au1yymwo) | 2026-10-17 13:00 | New York | Free | open |
| [Fall Book Crawl](https://luma.com/iycz744t) | 2026-10-17 16:00 | New York | 15 USD | open |
| [new interfaces 007](https://luma.com/72ze84s3) | 2026-10-18 17:00 | New York | Free | waitlist |

The tested preset saved 20 schema-valid, unique events in about eight seconds. At the configured rate, 20 saved events cost $0.0432. This bounded test is not a response-time or coverage guarantee.

### What does this Actor do?

- **You give:** a city name in "City" (New York, London, San Francisco), or Luma city pages ([luma.com/nyc](https://luma.com/nyc), /london, /sf) or category pages (/ai, /tech, /crypto).
- **You get:** event name and link, start and end time (UTC) with the event's time zone, location type (`offline` = in person, or online), city, region, country and neighborhood, approximate coordinates, free or ticket price and currency, registration status (open, waitlist, sold-out), guest count, the organizer calendar (empty when the host uses a personal calendar) and the host names.
- **How many:** up to your result limit from the pages read; the Actor reads 25 at a time until the list ends or a run limit is reached. Category pages end after about 30 events.
- **Price:** $2.16 per 1,000 saved events. No start fee: a run that saves nothing costs nothing. Platform usage is included. No proxy needed.
- **Not included:** exact address (Luma shows it only to registered guests), event description text, guest lists and attendee details, and host contact details. Turn on "Leave out names of people" to drop the host names too.

### Input

| Field | What it does | Default |
|---|---|---|
| City or category pages | Luma discovery pages to read | `https://luma.com/nyc` |
| City | City names or luma.com addresses, separated by commas (New York, nyc, London, sf); each adds its city page | None |
| Maximum results | Stop after this many events | 20 |
| Only new results | Skip results that an earlier run with the same input already saved; they are not saved or charged | Off |
| Leave out names of people | Empty the host names (`hosts`) | Off |
| Proxy configuration | Optional; the Actor runs without one | No proxy |

Example:

```json
{
    "startUrls": [
        { "url": "https://luma.com/nyc" },
        { "url": "https://luma.com/london" },
        { "url": "https://luma.com/ai" }
    ],
    "maxItems": 200
}
```

### API quick start: New York event export

For tool integrations, use the [machine-readable OpenAPI definition](https://api.apify.com/v2/actors/soogrow_berries~luma-events-scraper/builds/default/openapi.json). It describes the Actor API and input schema; the New York preset below supplies the use-case configuration.

Use this preset when you need public events from Luma's New York discovery page as structured data. An Apify account and API token are required; a Luma account is not.

Set `APIFY_TOKEN` to your own Apify API token in your local environment. Keep the token private; pass it in the authorization header, not the URL. This request has a $0.05 spending ceiling and a 120-second Actor timeout:

```bash
curl --fail-with-body --silent --show-error \
  --request POST \
  --url 'https://api.apify.com/v2/acts/soogrow_berries~luma-events-scraper/run-sync-get-dataset-items?timeout=120&maxTotalChargeUsd=0.05&format=json&clean=true' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"startUrls":[{"url":"https://luma.com/nyc"}],"maxItems":20,"proxyConfiguration":{"useApifyProxy":false}}'
```

| Contract | Behavior |
| --- | --- |
| Input | New York discovery URL, maximum 20 events, no proxy |
| Successful response | JSON array; one unique saved event per row; up to 20 rows |
| Key fields | `eventId`, `name`, `url`, `startAt`, `timezone`, `city`, `price`, `currency`, `availability`, `scrapedAt` |
| Times and unknown values | Raw timestamps are UTC. `timezone` is the event's local zone. Unknown values in nullable fields remain `null`; an unknown price is not zero. |
| Cost | $0.00216 per saved event, no start fee; 20 events = $0.0432. The $0.05 ceiling is a limit, not a minimum charge. |
| Scope | The discovery feed can include events already underway. It is not a complete archive. No attendee lists, host contact details or private addresses. |

For CSV, change `format=json` to `format=csv`. Inspect HTTP errors before retrying; repeating a run can incur another charge. For longer workflows or run-status/OUTCOME inspection, use the asynchronous [Run Actor API](https://docs.apify.com/api/v2/actors-runs-post). See the [synchronous endpoint reference](https://docs.apify.com/api/v2/actor-run-sync-get-dataset-items-post).

### Output

One record per event. Download it as JSON, CSV, Excel or HTML from the Output tab, or read it through the Apify API.

```json
{
    "eventId": "evt-eJqGZCbxARjYO7K",
    "name": "Fall Book Crawl",
    "url": "https://luma.com/iycz744t",
    "startAt": "2026-10-17T16:00:00.000Z",
    "timezone": "America/New_York",
    "city": "New York",
    "price": 15,
    "currency": "USD",
    "availability": "open",
    "scrapedAt": "2026-10-16T23:54:04.745Z"
}
```

A real record from the 16 October verification run, shortened to 10 of its 23 fields. The full JSON response includes all declared fields.
Coordinates are approximate: Luma shows the exact address only to registered guests. Times are in UTC; `timezone` is the event's local time zone. `guestCount` is `null` when Luma shows no count.

The run also saves an `OUTCOME` record in its key-value store, and the same sentence as the run's status message: `COMPLETE` (your pages have no more results), `MAX_RESULTS` (stopped at Maximum results), `SPENDING_LIMIT`, `PARTIAL` (some pages failed to load), `PAGE_LIMIT`, `NO_NEW_RESULTS` (Only new results is on and nothing is new), `NO_MATCHING_RESULTS`, `NO_RESULTS` or `FAILED`. Only `FAILED` ends the run as failed.

### Pricing

You pay $0.00216 for each event saved. There is no start fee. Platform usage is included, with no additional usage charge. Check the Store Pricing tab for the current rates.
Example: 100 saved events in one run cost $0.21605 (about $0.22).

- A record found on two of your pages is saved and charged once per run.
- A run that saves no events costs nothing, including when pages cannot be read.
- A record seen again in a later run is saved and charged again, unless "Only new results" is on.
- Set "Maximum results" or a spending limit to cap the cost.

### Notes

- This Actor is an independent tool. It is not affiliated with, endorsed by or sponsored by the website it reads.
- It reads public event listings only and needs no login. It does not collect guest lists or attendee details.
- Found a problem? Open an issue on the Issues tab and include the run link.

# Actor input Schema

## `startUrls` (type: `array`):

Luma discovery pages: cities such as https://luma.com/nyc, https://luma.com/london or https://luma.com/sf, or categories such as https://luma.com/ai, https://luma.com/tech or https://luma.com/crypto. The scraper reads every upcoming event listed there.

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

A Luma city by name or by its luma.com address, such as New York, nyc, London or sf. Separate several cities with commas. Each one adds the city page to the start URLs. In the Console, clear the pages above if you want these cities only.

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

Stop after saving this many events. You pay per result, so this also caps the cost.

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

Skip results that an earlier run with the same start URLs and filters already saved. Skipped results are not saved and not charged. The list of saved IDs is kept in a key-value store named "luma-events-scraper-seen" in your Apify account; delete it to start over.

## `leaveOutPersonFields` (type: `boolean`):

Empty the fields that name people: host names (hosts). The fields stay in each record as null or an empty list.

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

Optional. The Actor runs without a proxy.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://luma.com/nyc"
    }
  ],
  "maxItems": 20,
  "onlyNew": false,
  "leaveOutPersonFields": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Scraped Luma events in the default dataset.

## `runSummary` (type: `string`):

Run outcome record in the default key-value store.

# 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 = {
    "startUrls": [
        {
            "url": "https://luma.com/nyc"
        }
    ],
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("soogrow_berries/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 = {
    "startUrls": [{ "url": "https://luma.com/nyc" }],
    "maxItems": 20,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("soogrow_berries/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 '{
  "startUrls": [
    {
      "url": "https://luma.com/nyc"
    }
  ],
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call soogrow_berries/luma-events-scraper --silent --output-dataset

```

## MCP server setup

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