# Luma Attendee Scraper - Event Guest Lists & Social Handles (`forkoff/luma-get-attendees`) Actor

Scrape any Luma (lu.ma) event's attendee list: names, bios, and social handles (Twitter, LinkedIn, Instagram, TikTok, YouTube). Export to CSV, JSON, Excel or Google Sheets.

- **URL**: https://apify.com/forkoff/luma-get-attendees.md
- **Developed by:** [FORKOFF](https://apify.com/forkoff) (community)
- **Categories:** Lead generation, Automation, Social media
- **Stats:** 17 total users, 6 monthly users, 15.2% runs succeeded, 1 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

$12.00 / 1,000 attendees

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/platform/actors/running/actors-in-store#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 Get Attendees - Profiles & Social Handles

Export **every attendee of a Luma (lu.ma) event you can see** - names, bios, avatars, websites and **social handles** (Twitter, LinkedIn, Instagram, TikTok, YouTube) - straight to a clean dataset you can download as **JSON, CSV, Excel** or push to **Google Sheets**.

Perfect for **event networking and lead-gen**: pull the attendee list of a conference or meetup you're attending and instantly get everyone's socials.

You bring your own lu.ma session cookie, and the Actor reads the guest list through Luma's official API - the same list a logged-in attendee sees on the event page.

### What you get per attendee

`name`, `first_name`, `last_name`, `username`, `bio_short`, `avatar_url`, `website`, `timezone`, `is_verified`, `last_online_at`, `num_tickets_registered`, plus social handles: `twitter_handle`, `linkedin_handle`, `instagram_handle`, `tiktok_handle`, `youtube_handle`.

> Note: email, phone and ticket details are **host-only** on Luma and are not shown to attendees, so they are not part of this export.

### Input

| Field | Required | Description |
|---|---|---|
| `lumaCookie` | yes | Your lu.ma `luma.auth-session-key` cookie value (see below). |
| `eventUrl` | yes | The lu.ma event URL (e.g. `https://lu.ma/abc123?tk=...`) or its `evt-XXXXXXXX` id. Resolved automatically; an invite `tk` token is used if present. |
| `limit` | no | Guests per request (1-100, default 50). |
| `maxResults` | no | Stop after N attendees (default: fetch all). |

### How to get your Luma cookie

1. Log in to lu.ma in your browser.
2. Open DevTools (F12) > **Application** > **Cookies** > `https://lu.ma`.
3. Copy the value of **`luma.auth-session-key`** and paste it into `lumaCookie`.

### Which event?

Paste the **event URL** whose attendees you can see (e.g. `https://lu.ma/abc123`) - the Actor resolves it to the event id for you, and uses the invite `tk` token if the URL has one.

### Output

One dataset item per attendee (the full Luma guest record). Download as JSON / CSV / Excel, or connect to Google Sheets, your CRM, or a webhook.

### Notes

- You can export any event whose **attendee list is visible to you** as a logged-in guest. Private / host-only lists return 403.
- Pagination is automatic - the Actor walks every page until the list is complete.

***

Built by [FORKOFF](https://forkoff.xyz) - the culture studio for AI & Web3 events (ETHCC, Token2049, Devcon).

# Actor input Schema

## `lumaCookie` (type: `string`):

The value of your lu.ma 'luma.auth-session-key' cookie. Log in to lu.ma, open DevTools > Application > Cookies > lu.ma, and copy the luma.auth-session-key value. You can paste just the value, or the whole 'luma.auth-session-key=...' pair.

## `eventUrl` (type: `string`):

The lu.ma event URL you host - e.g. https://lu.ma/abc123 - or the event api\_id (evt-XXXXXXXX). The Actor resolves the URL to the event id automatically.

## `limit` (type: `integer`):

Guests fetched per request (1-100). Default 50.

## `maxResults` (type: `integer`):

Optional. Stop after this many attendees. Leave empty to fetch all.

## Actor input object example

```json
{
  "eventUrl": "https://lu.ma/",
  "limit": 50
}
```

# 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 = {
    "eventUrl": "https://lu.ma/"
};

// Run the Actor and wait for it to finish
const run = await client.actor("forkoff/luma-get-attendees").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 = { "eventUrl": "https://lu.ma/" }

# Run the Actor and wait for it to finish
run = client.actor("forkoff/luma-get-attendees").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "eventUrl": "https://lu.ma/"
}' |
apify call forkoff/luma-get-attendees --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=forkoff/luma-get-attendees",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tgCQL64PoMIHnonv9/builds/BerPVkmED3dWVMChS/openapi.json