# Luma Events Scraper (`zucchini_gopher_m2v/luma-scraper`) Actor

Extract event details, an organizer's full event calendar, or the platform-wide discover/trending feed from lu.ma / luma.com -- no account or API key needed.

- **URL**: https://apify.com/zucchini\_gopher\_m2v/luma-scraper.md
- **Developed by:** [Faisal Ahdan naufal](https://apify.com/zucchini_gopher_m2v) (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 $2.70 / 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.
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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Luma Events Scraper

Extract event details, an organizer's full event calendar, or the
platform-wide discover/trending feed from lu.ma / luma.com — no account
or API key needed.

### Why use this actor

- One actor covers Luma's whole public surface: a single event's full
  detail, an organizer's complete upcoming/past event list, or the
  general discover/trending feed
- No account, login, or API key required — this actor talks to the same
  internal API (`api.lu.ma`) that powers the luma.com website itself for
  every logged-out visitor
- Accepts a full URL, a bare path, or just the short slug — paste
  whatever you copied from the address bar
- Automatic retries on temporary network hiccups
- Robust pagination — automatically follows Luma's cursor links up to
  the limit you set, instead of returning just one page
- Honest about limits: guest lists and Luma's own search are gated
  behind a login wall upstream and are out of scope, stated plainly
  rather than faked (see Known limits)

### How it works

Pick a `mode`:

1. **`event`** — full detail for one or more specific event URLs.
2. **`calendar`** — an organizer's own profile plus their full event
   list (upcoming or past).
3. **`discover`** — the platform-wide discover/trending feed, optionally
   filtered by latitude/longitude (no URL needed).

### Input

**Event detail:**

```json
{
  "mode": "event",
  "urls": ["https://lu.ma/sggq2oi9", "lu.ma/some-other-event"]
}
```

**Organizer calendar:**

```json
{
  "mode": "calendar",
  "url": "https://lu.ma/drupal-indonesia",
  "period": "future",
  "maxItems": 100
}
```

**Discover feed:**

```json
{ "mode": "discover", "maxItems": 50 }
```

```json
{ "mode": "discover", "latitude": "40.7128", "longitude": "-74.0060", "maxItems": 50 }
```

| Field | Type | Description |
|---|---|---|
| `mode` | string | `"event"` (default), `"calendar"`, or `"discover"`. |
| `url` | string | `event`/`calendar` mode — a single lu.ma URL, path, or bare slug. |
| `urls` | array | `event`/`calendar` mode — multiple URLs/slugs in one run. |
| `period` | string | `calendar` mode — `"future"` (default) or `"past"`. |
| `latitude` / `longitude` | string | `discover` mode — filter the feed around this coordinate. Leave blank to use the request's own IP-based location (Apify proxy country then steers results). |
| `maxItems` | integer | `calendar`/`discover` mode — max events to return. Pagination is followed automatically up to this cap. Default 100, max 10,000. |
| `maxConcurrency` | integer | `event`/`calendar` mode — how many URLs to fetch in parallel. Default 4. |
| `proxyConfiguration` | object | Apify Proxy settings. Residential is on by default (not required for this endpoint — no WAF was found, see `CRAWLING_METHOD.md` — kept for production robustness and to steer `discover` mode's geo-personalized results). |

### Output

**`event` mode** — one record per event, full upstream shape (truncated
here for readability):

```json
{
  "_input": "https://lu.ma/sggq2oi9",
  "_source": "S1-api",
  "_scrapedAt": "2026-08-29T18:52:22Z",
  "api_id": "evt-KrtX1E0X7IdEFch",
  "event": {
    "name": "bRUNch - Run & Brunch Vol. 1",
    "start_at": "2026-08-28T23:00:00.000Z",
    "end_at": "2026-08-29T05:00:00.000Z",
    "timezone": "Asia/Jakarta",
    "location_type": "offline",
    "geo_address_info": { "city": "Kota Jakarta Pusat", "country": "Indonesia" }
  },
  "calendar": { "name": "LeadSphere" },
  "hosts": [{ "name": "...", "username": "..." }],
  "ticket_info": { "is_free": true, "spots_remaining": 71, "require_approval": true },
  "guest_count": 0
}
```

**`calendar` mode** — one `CALENDAR_PROFILE` record, then one
`CALENDAR_EVENT` record per event:

```json
{
  "_input": "drupal-indonesia",
  "_source": "S1-api",
  "recordType": "CALENDAR_PROFILE",
  "calendar": { "name": "Drupal Indonesia", "slug": "drupal-indonesia", "location": { "city": "Jakarta" } },
  "featured_items": [ "..." ]
}
```

```json
{
  "_input": "drupal-indonesia",
  "_source": "S1-api",
  "recordType": "CALENDAR_EVENT",
  "api_id": "calev-ADxrEdCdFjJVuZb",
  "event": { "name": "Drupal Drag and Drop Page Builder", "start_at": "..." }
}
```

**`discover` mode** — one record per trending event, same per-event
shape as a `CALENDAR_EVENT` record above.

A record with `_error` instead of the fields above means that input
could not be processed (for example, `"_error": "not_found"` for a URL
that doesn't resolve to any event or calendar, or `"_error":
"kind_mismatch"` if you pass a calendar URL in `event` mode).

### Known limits

- **Guest lists and Luma's own search are not available.** Both
  `event/get-guest-list` and `search/get-results` require a logged-in
  session upstream (`401 "You are not signed in."`) even for fully
  public events — this is Luma's own access-control choice, not a bug,
  and is out of scope per this project's no-login policy.
- **The discover feed's ranking is Luma's own algorithm.** This actor
  exposes the geo-filter parameters Luma's own frontend uses, but the
  ranking/selection logic behind which events surface is not documented
  publicly.

# Actor input Schema

## `mode` (type: `string`):

"event" fetches full detail for specific event URL(s). "calendar" fetches an organizer's profile plus their full event list (upcoming or past). "discover" fetches the platform-wide discover/trending feed (no URL needed, optionally geo-filtered).

## `url` (type: `string`):

"event" or "calendar" mode: a single lu.ma URL, path, or bare slug (e.g. "https://lu.ma/sggq2oi9", "lu.ma/a16z", or just "sggq2oi9").

## `urls` (type: `array`):

"event" or "calendar" mode: multiple lu.ma URLs/slugs to process in one run.

## `period` (type: `string`):

"calendar" mode only -- list this organizer's upcoming (future) or past events.

## `latitude` (type: `string`):

"discover" mode only -- filter the trending feed around this latitude. Leave blank to use the request's own IP-based location (so Apify proxy country also steers results).

## `longitude` (type: `string`):

"discover" mode only -- filter the trending feed around this longitude. Leave blank to use the request's own IP-based location.

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

"calendar" mode: max events to list per organizer. "discover" mode: max events to list. Pagination is followed automatically until this cap or the end of the result set, whichever comes first.

## `maxConcurrency` (type: `integer`):

"event"/"calendar" mode only -- how many URLs to fetch in parallel.

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

Apify Proxy configuration. Residential is on by default. Not required for this endpoint (no WAF was found -- see CRAWLING\_METHOD.md), but kept on for production robustness and to steer "discover" mode's geo-personalized results by proxy country.

## Actor input object example

```json
{
  "mode": "event",
  "url": "https://lu.ma/sggq2oi9",
  "period": "future",
  "maxItems": 100,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

All scraped event / calendar records produced by this run.

# 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 = {
    "mode": "event",
    "url": "https://lu.ma/sggq2oi9",
    "period": "future",
    "maxItems": 100,
    "maxConcurrency": 4,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("zucchini_gopher_m2v/luma-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 = {
    "mode": "event",
    "url": "https://lu.ma/sggq2oi9",
    "period": "future",
    "maxItems": 100,
    "maxConcurrency": 4,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("zucchini_gopher_m2v/luma-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 '{
  "mode": "event",
  "url": "https://lu.ma/sggq2oi9",
  "period": "future",
  "maxItems": 100,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call zucchini_gopher_m2v/luma-scraper --silent --output-dataset

```

## MCP server setup

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