Luma Scraper — Events & Organizer Leads (lu.ma)

Extract complete Luma event data — exact date/time, venue geo, ticket price, capacity & spots remaining, categories, the full host list, and the community calendar behind every event — plus turn each community/organizer into a B2B lead with its description, Instagram / LinkedIn / TikTok handles and a lead score. Works on both lu.ma and luma.com.

No login, no cookies — fast JSON extraction straight from Luma's own internal API.

Why this Luma scraper?

Luma is where the AI, startup, crypto and tech scene runs its events — and most scrapers can't read it at all, or grab only the event title. This actor reads Luma's internal API directly and ships the richest dataset in the category: events plus the communities and hosts behind them.

Data	Typical scrapers	This actor
Event title, date/time, URL	partial	✅
In-person vs online + venue city/region/geo	❌	✅
Ticket price, free/paid, sold-out & spots remaining	❌	✅
Full description + event categories	❌	✅
Hosts with website & bio	❌	✅
Community calendar: name, description, IG/LinkedIn/TikTok	❌	✅
Organizer lead score	❌	✅
Search by city + keyword, or scrape a community/event URL	partial	✅
Monitor mode — only new events since last run	❌	✅

Use cases

• Lead generation — Luma communities (calendars) are run by founders, DevRel teams, VCs and agencies. Capture each one with its social handles and lead score, then reach out.
• Event discovery & aggregation — feed calendars, newsletters and apps with structured Luma data (date, venue, price, capacity) for any tech hub: San Francisco, New York, Austin, London, Singapore, and more.
• Sponsorship & partnership prospecting — find active communities by city and topic (AI, crypto, design, startups), then pitch the organizer directly.
• Market & trend research — track which topics and communities are drawing crowds across the startup ecosystem.
• Competitive intelligence — monitor specific communities for every new event they launch.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the Luma Scraper, fill in the inputs you need, and click Start.
3. Watch results stream into the dataset table as each record is parsed.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
    "cities": ["San Francisco", "New York"],
    "searchQueries": ["ai", "crypto"],
    "outputType": "all",
    "eventType": "any",
    "enrichEvents": true,
    "includeCalendarLeads": true,
    "maxResults": 200
}

• outputType (default events) — events, calendars (organizer leads with social handles), or all (events + their community calendars, each row tagged with a type).
• cities — city names or Luma slugs (San Francisco/sf, New York/nyc, Austin, London, Singapore). Common names are mapped automatically.
• searchQueries — optional keywords, combined with every city (ai, crypto, startup, design). Leave empty to get all of a city's events.
• eventType (default any) — offline (in-person) or online.
• dateFrom / dateTo — only events starting in this window (YYYY-MM-DD).
• onlyFreeEvents (default false) — only free-registration events.
• eventUrls / calendarUrls / startUrls — scrape specific events or communities directly (full URLs, slugs, or evt-/cal- api_ids; startUrls accepts a mixed list and auto-routes each).
• enrichEvents (default true) — open each event for description, categories, exact capacity/spots-left, price and the full host list. One fast API call per event; turn off for a faster run.
• includeCalendarLeads (default true) — in all mode, emit one community-lead record per unique organizer.
• includeCalendarEvents (default false) — when scraping a community, also pull its upcoming events.
• maxResults (default 200, 0 = no limit) — cap on primary records; keeps test runs cheap and predictable.
• maxConcurrency (default 6) — maximum parallel API calls.
• proxyConfiguration — Apify Proxy (datacenter, the default) works well; Luma's public API is light on anti-bot.

Output

By default you get one clean table of events. Set outputType to calendars for organizer leads, or all to combine both (each row tagged with a type of event or calendar).

An event record (type: "event"):

{
    "type": "event",
    "eventId": "evt-kTedGXXQYZLkTdB",
    "name": "AI Builders Hack Day",
    "eventUrl": "https://luma.com/aibuildershack",
    "startAt": "2026-06-18T16:30:00.000Z",
    "endAt": "2026-06-19T02:30:00.000Z",
    "timezone": "America/Los_Angeles",
    "durationMinutes": 600,
    "locationType": "in-person",
    "isOnline": false,
    "description": "A full day for SF builders to ship real AI projects…",
    "city": "San Francisco",
    "regionShort": "CA",
    "country": "United States",
    "countryCode": "US",
    "latitude": 37.78978,
    "longitude": -122.39649,
    "isFree": false,
    "price": null,
    "isSoldOut": false,
    "spotsRemaining": 835,
    "requireApproval": true,
    "categories": ["AI"],
    "coverUrl": "https://images.lumacdn.com/…",
    "hostNames": ["AWS Builder Loft", "tokens&"],
    "hostCount": 2,
    "hosts": [{ "name": "AWS Builder Loft", "website": "https://builder.aws.com/…", "bio": "…", "profileUrl": null }],
    "calendarId": "cal-EVJ0XV6EJegxAT7",
    "calendarName": "tokens&",
    "calendarSlug": "tokensand",
    "calendarUrl": "https://luma.com/tokensand",
    "calendarLinkedin": "/company/tokensand",
    "searchCity": "San Francisco",
    "searchQuery": "ai",
    "scrapedAt": "2026-06-12T19:35:55.262Z"
}

A community record (type: "calendar") carries name, description, calendarUrl, instagram / linkedin / tiktok handles, lumaPlusActive, upcomingEventCount and a leadScore.

Luma is organizer-entered data, so some fields appear only when the organizer published them (e.g. a free event has price: null, some communities list no socials). A blank field means the organizer didn't publish it — not that scraping failed; nothing is dropped. Attendee personal data is not published by Luma and is not included.

Monitoring — get only new events

Turn on onlyNewItems to make every run output only events you haven't received before. The actor remembers what it has delivered in a persistent store, so on a schedule each run hands you just the newly listed events — ideal for newsletters, lead pipelines and Slack alerts.

• Use monitorStateKey to name the monitor memory so different searches each track their own "already seen" list. Use a different key per search/schedule to keep them independent.
• Monitor mode is a per-run "new items only" filter that works alongside Apify Schedules — it does not replace or interfere with the scheduler.

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it on a cron to keep your data fresh.
• Webhooks — trigger downstream actions the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/luma-scraper').call({
    cities: ['San Francisco'],
    searchQueries: ['ai'],
    outputType: 'all',
    enrichEvents: true,
    maxResults: 200,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new records straight into your CRM or sheet.
• Slack — get notified when a run finds something new.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find AI events in San Francisco on Luma with their community organizers" and let it run this scraper for you.

More scrapers from scrapesage

Build a complete event intelligence & lead-gen stack across every major event platform:

• Eventbrite Scraper — events plus organizer leads with contacts.
• Sched Conference Scraper — conference speakers, sessions, sponsors & leads.
• Swapcard Exhibitor Scraper — event exhibitors, speakers & contacts.
• Whova Event Scraper — event sessions, speakers, sponsors & exhibitors.
• LinkedIn Jobs Scraper — filter-based LinkedIn job postings, no login.
• Bark Listing Scraper — service-provider directory listings & leads.
• Facebook Ad Library Scraper — competitor ad intelligence on Meta & Instagram.
• Telegram Scraper — channels, messages, media & search.

Tips

• Pick a single outputType (Events or Community calendars) for a clean, fully-populated table. Use all to get events plus the communities behind them in one dataset.
• Organizer leads: run outputType: "all" or calendars — every unique community becomes a contactable lead with social handles and a lead score.
• Scrape a whole community: put its URL in calendarUrls with includeCalendarEvents on to pull all of its upcoming events.
• Faster runs: turn off enrichEvents if you don't need description/categories/price — you still get date, geo, hosts, capacity and the community.
• Recurring monitoring: combine Schedules with onlyNewItems (and a distinct monitorStateKey per search) to capture only newly listed events each day.

FAQ

How do I scrape Luma events for a city? Put the city in cities (San Francisco, New York, Austin, London, Singapore, or Luma slugs like sf/nyc). Add keywords in searchQueries to narrow by topic.

Does it work on luma.com and lu.ma? Yes — Luma rebranded from lu.ma to luma.com; this actor reads the same internal API that powers both.

Does it need a Luma API key or login? No. This actor reads Luma's public internal API — no key or login needed.

Can I scrape a single community or event? Yes — paste its URL into calendarUrls or eventUrls (or a mixed list in startUrls). Communities can also yield all their upcoming events with includeCalendarEvents.

How do I get only new events on a schedule? Turn on monitor mode (onlyNewItems) and create a Schedule. Each run returns only events it hasn't delivered before, and works alongside the scheduler.

Where do the leads come from? From each event's public host list and its community calendar page on Luma (description, Instagram/LinkedIn/TikTok). Attendee personal data is not published by Luma and is not included.

Can I export to Google Sheets, CSV or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.