Luma Events Scraper - lu.ma Events, Hosts, Tickets & Organizers avatar

Luma Events Scraper - lu.ma Events, Hosts, Tickets & Organizers

Pricing

from $0.03 / 1,000 events

Go to Apify Store
Luma Events Scraper - lu.ma Events, Hosts, Tickets & Organizers

Luma Events Scraper - lu.ma Events, Hosts, Tickets & Organizers

Scrape Luma (luma.com, lu.ma) events by city, category, keyword, calendar, host or link: every event near a city, hosts and organizers with socials, ticket prices, guest counts, full description, ticket types. Monitor mode, alerts. $0.027 per 1,000 events, details $0.69 per 1,000.

Pricing

from $0.03 / 1,000 events

Rating

0.0

(0)

Developer

Top Api

Top Api

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Features

Limited permissions

Share

What does Luma Events Scraper do?

Luma Events Scraper reads public events from Luma (luma.com, formerly lu.ma) - the RSVP platform behind AI and tech meetups, hackathons, founder dinners, crypto and community events - and returns one row per event: name, link, start and end time with timezone, venue and address with coordinates, the organizer (calendar) with website and social links, every host and Luma's featured guests with their LinkedIn / Instagram / X / YouTube / TikTok links, ticket price, sold-out and waitlist state, spots left and the guest count. By default every row also carries the event's full Luma record: the description (text, Markdown and HTML), every ticket type with its price and spots, the registration questions, Luma categories, and the emails, phone numbers, Telegram / Discord / WhatsApp links and sponsor lines written in the description.

Luma scraper · lu.ma scraper · Luma events API · Luma calendar scraper · luma.com events data

  • Every event near a city, not only the city page: Luma's own nearby feed. On 2026-11-06 it listed 1,065 events around San Francisco and 1,200 around London, against 77 and 62 on Luma's featured city pages (the featured page is one option away).
  • Every way into Luma: cities (Luma's 87 cities or any other place name), Luma's 12 categories (in a city or worldwide), keyword search, calendars and communities (upcoming and past), hosts, event links, a point with a radius, a map rectangle, luma.com/discover - mixed in one run.
  • Past Luma's 50-match search cap: a search near a city is read further by map area, a worldwide one region by region.
  • A date window that skips what you did not ask for: the feed is opened at your start date instead of being paged through from today.
  • Organizer and host rows too: one row per organizer calendar (website, socials, upcoming / past / last-90-day event counts) or per host profile (events hosted and attended, joined date) - and an optional email read from each organizer's own website.
  • Monitor mode with changes: a schedule delivers only events earlier runs did not deliver, and (option) events whose date, price, sold-out or waitlist state, venue or format changed, with the old values. Alerts to a webhook, Slack, Discord, Teams, Telegram or ntfy; an .ics calendar file of the run.
  • No login, cookies or API key: Luma's public JSON - the same data luma.com shows a visitor who is not signed in.
  • Pay only for delivered rows: no start fee; filtered-out events, duplicates and events delivered by earlier monitor runs are never charged.

What data can you get from Luma?

🎟️ Event name, id, link, slug🗓️ Start, end, timezone, duration🏷️ Luma categories, calendar tags
📍 Venue, full address, city, region, country🗺️ Latitude / longitude, Google place id💻 In person or online (Zoom, Google Meet ...)
🏢 Organizer: name, website, verified, Luma Plus🔗 Organizer LinkedIn, Instagram, X, YouTube, TikTok👤 Hosts with bio, website and social links
⭐ Featured guests (up to 10)💳 Free / paid, price, currency, price range🎫 Every ticket type: price, capacity, registered, spots
👥 Guest count, tickets, spots left🚦 Open / waitlist / sold out, approval required📝 Description: text, Markdown, HTML
❓ Registration questions✉️ Emails, phones, Telegram / Discord links in the text🤝 Sponsor and partner lines

Measured fill on a real 1,000-event London run (2026-11-06, details on): name, link, dates, city, country, coordinates, organizer, guest count, cover image and ticket types 100%; description 99.1%; hosts 98.3% (LinkedIn on 64.8% of hosts, website 33.8%, Instagram 30.2%, X 26.8%); Luma categories 75.8%; organizer social links 73.6%; spots remaining 67.8%; venue and full address 65.3% (the rest are events whose host shows the address to registered guests only - Luma then gives the city and an approximate point); registration questions 62.4%; featured guests 52.9%; organizer website 50.0%; links in the description 44.8%; sponsor lines 35.2%; paid events 23.4% (price and currency on those); Telegram / Discord / other social links in the description 17.3%; emails in the description 6.3%.

How to scrape Luma with Luma Events Scraper

  1. Type one or more cities (or pick categories, type search keywords, paste calendars, hosts or any Luma links).
  2. Optional: a date window, in person / online, free / paid, a minimum guest count, words the event must or must not contain.
  3. Leave Full event details on for descriptions and ticket types, or turn it off for listing rows only.
  4. Click Start. Rows arrive in the dataset as each page is read; download them as JSON, CSV, Excel or XML.

⬇️ Input

FieldWhat it does
citiesCity names or Luma slugs (San Francisco, sf, New York, London, Berlin, Tokyo). Luma's 87 cities, or any other place name (found by a geocoder).
categoriestech, ai, crypto, arts, food, climate, fitness, wellness, running, books, games, family. With cities: that category in each city; without: worldwide, region by region.
searchQueriesLuma's own event search. Near each city when cities are given, otherwise worldwide.
startUrlsAny luma.com / lu.ma link: event, calendar, city page, category page, luma.com/discover, luma.com/user/...
calendarsCalendar slugs, links or cal- ids (genai-sf, https://luma.com/ycombinator-official).
hostsLuma usernames, profile links or usr- ids.
eventUrlsEvent links, slugs or evt- ids.
urlsFromFileMany links or slugs, one per line.
periodCalendars and hosts: upcoming (default), past, all.
cityScopenearby (default, every event near the city) or featured (Luma's curated city page).
radiusKmKeep events within this distance of the city centre or the point.
latitude, longitudeEvery event near a point.
boundingBoxEvery event inside {"north", "south", "east", "west"}.
dateFrom, dateTo, daysAheadStart-date window.
eventTypeany, in_person, online.
pricingany, free, paid.
minGuestsMinimum registered guests.
keywordFilter, excludeKeywordsWords the name (or, with details, the description) must / must not contain.
hideSoldOutDrop sold-out events.
includeDetailsThe full event record on every row (default on, charged per row that gets it).
descriptionFormat, descriptionMaxLengthall / text / markdown / html; cut length.
includeHostProfilesHosted / attended counts and join date on every host (no extra charge).
organizerContactsEmail, phones and social links from each organizer's own website (charged once per organizer per run, only when an email is found).
outputTypeevents (default), calendars (one row per organizer), hosts (one row per host), all.
maxItemsRows in the run (default 100; 0 = no limit).
maxItemsPerSource, maxPagesCaps per city / category / search / calendar / host.
splitSearchesRead past Luma's 50-match search cap (default on).
searchMatchstrict (default): a search row must have a search word in its name, organizer or hosts. luma: Luma's own ranking as it is.
monitorMode, emitChanges, monitorStoreName, firstRunMode, resetMonitorScheduled runs: only new (and changed) events.
generateIcsSave the delivered events as events.ics.
webhookUrl (+ webhookHeaders), slackWebhookUrl, discordWebhookUrl, teamsWebhookUrl, telegramToken + telegramChatId, ntfyTopicAlerts after a run that delivered rows.
maxConcurrency, proxyConfigurationEvent records read at once; your own proxy (empty = direct, then Apify datacenter, then residential).

Input names other Luma scrapers use are accepted too (lumaUrls, discoverCity, slugs, scrapeEventDetails, maxResults, maxEvents, maxEventsPerCity, startDate / endDate, lat / lng, onlyNewItems, includePastEvents ...).

Input JSON

{
"cities": ["San Francisco", "London"],
"categories": ["ai"],
"dateFrom": "2026-12-01",
"dateTo": "2026-12-31",
"pricing": "free",
"minGuests": 50,
"maxItems": 500
}

Tips

  • A whole city: leave categories and keywords empty - the nearby feed is every public in-person event around it.
  • Online events: Luma's city and map feeds list in-person events; online ones come from calendars, hosts, searches and links.
  • Big lists without descriptions: turn Full event details off - listing rows still carry hosts, organizer, tickets and guest counts.
  • A worldwide search ranks events near Luma's guess of the caller's location first; add cities for one area.

⬆️ Output

One row per event. A real row from the London run (trimmed: one host, one featured guest, one ticket type, descriptions cut):

{
"type": "event",
"id": "evt-mXuRZDludSZQetj",
"name": "Assay-A-Thon | Building an Experimental Validation Toolkit for AI-Enabled Discovery",
"url": "https://luma.com/1a6mdyp6",
"category": "ai",
"categories": ["AI"],
"startAt": "2026-11-06T17:00:00.000Z",
"endAt": "2026-11-08T18:00:00.000Z",
"timezone": "Europe/London",
"durationMinutes": 2940,
"locationType": "offline",
"isOnline": false,
"city": "London",
"region": "England",
"country": "United Kingdom",
"countryCode": "GB",
"latitude": 51.53056945427067,
"longitude": -0.12524249328488116,
"distanceKm": 2.4,
"organizerName": "nile verleur",
"organizerUrl": "https://luma.com/user/usr-o515DoAA4t7FrGS",
"hosts": [
{
"id": "usr-o515DoAA4t7FrGS",
"name": "nile verleur",
"profileUrl": "https://luma.com/user/usr-o515DoAA4t7FrGS",
"socialHandles": { "linkedin": "https://www.linkedin.com/in/nile-verleur", "instagram": null, "twitter": null, "youtube": null, "tiktok": null }
}
],
"hostCount": 4,
"hostNames": "nile verleur, Inga Van den Bossche, Alex Ainscough, Anjali Chadha",
"featuredGuestCount": 10,
"ticketing": { "isFree": true, "isSoldOut": true, "spotsRemaining": 0, "requiresApproval": true, "registrationAvailability": "sold-out" },
"guestCount": 46,
"description": "Join us to develop prototypes and assays that meet the demands of AI-enabled discovery, then compete for a fellowship to experimentally validate your work using…",
"ticketTypes": [{ "id": "ttype-kVlaaVAkvcJQTMm", "name": "Standard", "type": "free", "registered": 46, "requiresApproval": true }],
"registrationQuestionCount": 10,
"registrationQuestions": [{ "id": "tmsp7g5k", "label": "What is your LinkedIn profile?", "type": "linkedin", "required": true }],
"detailsFetched": true,
"source": "London",
"sourceType": "city",
"scrapedAt": "2026-11-06T20:38:21.034Z"
}

The full row also carries location (venue, full address, address, sublocality, place id, address visibility, meeting platform), organizer (id, slug, description, verified, Luma Plus, avatar, cover, website, social links), featuredGuests, attendance (tickets, waitlist, guest-list visibility), descriptionMarkdown, descriptionHtml, descriptionLinks, extractedEmails, extractedPhones, socialLinks, sponsorMentions, nameRequirement, phoneRequirement, featuredIn, refundPolicy, coverImageUrl, socialImageUrl, dominantColors, featuredCity, tags and platform (external for an event a calendar lists from another site). Monitor runs add changeType, previousValues, firstSeenAt, lastSeenAt, contentHash. The dataset has views for events, details, organizer leads, monitor changes, organizer calendars and hosts.

Organizer rows (outputType: calendars): id, name, slug, url, description, website, social links, city, country, coordinates, verified, Luma Plus, personal or community, total / upcoming / past / last-90-day events, next and last event, tags, membership tiers, Luma plan, and with organizer contacts the email, phones and website social links. Host rows (outputType: hosts): id, name, username, profile link, bio, website, social links, events hosted, events attended, joined date.

Not available: the guest / attendee list (Luma shows it only to signed-in users), and the exact address of events whose host keeps it for registered guests.

How can I use Luma data?

  • Sales and partnerships: organizers and hosts of AI, tech and founder events in a city, with their websites and LinkedIn - and the paid, near-capacity events worth sponsoring.
  • Event and community teams: what competing communities run, when, at what price and how many people register.
  • Newsletters and event sites: a daily feed of new events in a city or category, with descriptions and cover images.
  • Research: event volume, pricing and attendance by city, category and month.

How much does it cost to scrape Luma?

Pay per event, no start fee:

WhatPrice
Event row$0.027 per 1,000
Full event details on a row (default on)$0.69 per 1,000
Organizer calendar row$6.30 per 1,000
Host profile row$5.40 per 1,000
Organizer email from their website$0.90 per 1,000 organizers with an email

A detailed event row is $0.717 per 1,000; a listing row alone $0.027 per 1,000. Measured on real runs: 20 events with details $0.014; 150 events across three cities $0.11; 1,000 London events with details $0.72 (130 s); 3,000 listing rows from three cities $0.081 (46 s). Set Maximum cost per run in the run options and the run stops cleanly at it (a $0.02 limit delivered 27 detailed events and charged $0.0194).

Run it on a schedule (only new events)

Turn on Only new events (monitor) and schedule the actor (Apify Console > Schedules, or the API). The first run delivers what it finds (or, with First monitor run: remember only, nothing); every later run with the same input delivers only events it has not delivered before. With Also changed events, a remembered event whose name, date, price, sold-out or waitlist state, venue or format changed comes back as changeType: "updated" with previousValues. Turn on event details, host profiles or organizer contacts later and the events delivered without them come back once with them (changeType: "details"), charged like any delivered event. A poll that finds nothing costs about $0.0001 of platform time and is not charged.

{
"cities": ["Toronto"],
"maxItems": 0,
"monitorMode": true,
"emitChanges": true,
"slackWebhookUrl": "https://hooks.slack.com/services/..."
}

Measured: first run 430 events; an immediate second poll 0 rows ($0.000096); a poll 20 minutes later 1 new event and 2 changed ones (one sold out, one renamed).

Integrations, API, scheduling & MCP

Run it from the Apify API (POST https://api.apify.com/v2/acts/TopApi~luma-events-scraper/runs), the Apify CLI, Make, Zapier, n8n, Google Sheets, or an AI agent through the Apify MCP server. Results stay in the run's dataset (JSON, CSV, Excel, XML, RSS); events.ics imports into Google, Outlook and Apple Calendar.

Limits & empty runs

  • Luma answers about 50 feed pages from one IP in a burst, then asks for "additional verification". The actor reads up to 40 pages at once per egress, then one every 3 seconds, and moves one rung up (direct, then Apify datacenter, then residential) when Luma asks - so very large runs slow down rather than stop: 3,671 tech events worldwide took 204-224 s.
  • A search shows Luma's 50 best matches. Luma answers even a word no event uses with 50 unrelated events; in strict mode those rows are dropped, the run ends with a status that says so, and nothing is charged.
  • City, map and category feeds list upcoming in-person events; past events come from calendars and hosts (period).
  • An event whose full record cannot be read is delivered with its listing fields (detailsFetched: false) and is not charged for details.
  • Every 0-row run ends with a status that says why (nothing matched the filters, a link that is not on Luma, a search word no event has); nothing is charged.

FAQ

How many events can I get in one run?

As many as Luma lists: a whole city's nearby feed (London 1,200, San Francisco 1,065, Toronto 430 on 2026-11-06), every city in a list, a category worldwide (tech: 3,671), or a calendar's full history.

Do I need a Luma account, cookies or an API key?

No. Everything comes from Luma's public pages and JSON, as a signed-out visitor sees them.

Can I get the attendee list?

No. Luma shows the guest list only to signed-in users; the actor delivers the public guest count and Luma's featured guests.

Can I get the organizer's email?

Turn on Organizer email from their website: the actor reads the organizer's own website (the link on their Luma calendar) and its contact / about pages. Emails written in the event description are in extractedEmails on every detailed row.

How do I get only events I have not seen?

Monitor mode (above).

Why did my run return no results?

The status message says why: the filters removed every event, the city is not found, the link is not a Luma page, or Luma's search has no event with the word. Nothing is charged for an empty run.

Your feedback

Found a Luma page the actor does not read, or need a field? Open an issue on the actor's Issues tab.