Luma Event Scraper 🎟️ — Scrape lu.ma Events, Hosts & Calendars

Extract Luma (lu.ma) events as clean, structured data — without writing any code. Discover events by city or category, scrape entire calendars/communities, or pull individual events, and get full details including date, location, GPS, tickets, guest counts and host/organizer social profiles.

Fast and reliable: this scraper is built on Luma's own data layer, so it returns complete, structured JSON — no missing fields, no flaky page-rendering.

💡 Two superpowers: (1) City/category discovery — list every event happening in a city like SF, NYC or London. (2) Host lead-gen — every event ships its organizers' Instagram, X/Twitter, LinkedIn, TikTok, YouTube and website.

---

📋 Table of contents

• What does it do?
• Use cases
• How to use it
• Input parameters
• Input examples
• Output — data fields
• Sample output record
• Host & organizer lead generation
• Pagination & scale
• Tips & best practices
• Frequently asked questions
• Related scrapers
• Changelog

---

What does it do?

Luma powers tens of thousands of tech meetups, conferences, parties, workshops and community events worldwide. This actor turns Luma into a structured dataset you can export to JSON, CSV, Excel, XML or HTML, or pull from the Apify API.

Four ways to scrape:

• 🌆 By city — discover all upcoming events in a city (e.g. sf, nyc, london).
• 🏷️ By category — filter to a topic like ai, tech, arts, crypto, wellness.
• 📅 By calendar/community — scrape every upcoming event from a Luma calendar (e.g. a company or community page).
• 🔗 By URL — paste any Luma event, calendar or city URL.

For every event you get the name, start/end time + timezone, venue and full address with GPS coordinates (or online link), cover image, ticket info (free/paid, price, sold-out, spots remaining), guest count, the calendar it belongs to, and full host/organizer profiles with social handles. Optionally fetch each event's description, ticket types/prices and categories.

---

Use cases

🎯 Event marketers & community builders

• Track every event in your city or niche and benchmark turnout (guest counts).
• Find the most active organizers and communities to partner with.
• Monitor competitor and ecosystem events in real time.

📇 Sales & lead generation

• Build lists of event organizers with their social profiles and websites.
• Target hosts running events in your category/city for sponsorship or outreach.
• Feed organizer leads straight into your CRM.

📊 Researchers & analysts

• Analyse event trends by city, category, time and price.
• Study the events ecosystem with clean, exportable data.

🤝 Sponsors & venues

• Discover upcoming events that fit your audience.
• Map events geographically by coordinates.

🤖 Data & AI teams

• Power event-discovery apps, newsletters and dashboards.
• Build datasets of events, hosts and venues.

---

How to use it (step by step)

No coding required.

1. Click Try for free / Start.
2. Pick how you want to scrape:
   • Cities — add city slugs like sf, nyc, london (from luma.com/<slug>).
   • Category — optionally narrow to ai, tech, arts, etc.
   • Calendars — add community/calendar handles (from luma.com/<handle>).
   • Luma URLs — paste event/calendar/city URLs directly.
3. Set Max items (start with 100).
4. Turn on Include full event details if you want descriptions, ticket prices and categories.
5. Click Save & Start, then export the results.

---

Input parameters

Field	Type	Description
cities	array	City slugs to discover events in (e.g. sf, nyc, london).
category	string	Optional category slug (e.g. ai, tech). Works with cities or on its own.
calendars	array	Calendar/community handles to scrape upcoming events from.
startUrls	array	Any Luma URLs — events, calendars, or cities (auto-detected).
includeDetails	boolean	Fetch each event's description, ticket types and categories. Default false.
maxItems	integer	Max events. 0 = no limit. Default 200.
proxyConfiguration	object	Proxy settings. Default: Apify Proxy on.
maxConcurrency	integer	Max parallel requests. Default 5.

---

Input examples

1) Discover all events in San Francisco

{
  "cities": ["sf"],
  "maxItems": 200
}

2) AI events across several cities

{
  "cities": ["sf", "nyc", "london"],
  "category": "ai",
  "maxItems": 500
}

3) Scrape a community calendar with full details

{
  "calendars": ["vizcom"],
  "includeDetails": true
}

4) Specific events / pages by URL

{
  "startUrls": [
    { "url": "https://luma.com/nqkyxczb" },
    { "url": "https://luma.com/sf" }
  ],
  "includeDetails": true
}

---

Output — data fields

Each event is one dataset row. Core fields:

Field	Description
eventId	Luma event ID
name	Event name
url / slug	Event URL and slug
eventType	Event type
visibility	public / private
startAt / endAt	Start and end datetime (ISO)
timezone	Event timezone
locationType	offline / online
isOnline	Boolean
address / fullAddress	Venue address
city / region / country	Location
latitude / longitude	GPS coordinates
virtualUrl	Link for online events
coverUrl / socialImageUrl	Images
isFree	Boolean
price / maxPrice	Ticket price(s)
isSoldOut	Boolean — event is sold out
isNearCapacity	Boolean — event is close to selling out (demand signal)
spotsRemaining	Remaining spots
requireApproval	Whether registration needs approval
registrationAvailability	Registration state
guestCount	Number of guests
ticketCount	Number of tickets
calendarName / calendarSlug / calendarUrl	Owning calendar
hosts	Array of host profiles (see below)
hostCount	Number of hosts
featuredGuestCount	Number of featured guests
scrapedAt	ISO timestamp

Each entry in hosts[]: name, username, website, bio, avatarUrl, isVerified, instagram, twitter, linkedin, tiktok, youtube.

With includeDetails: true you also get:

Field	Description
description	Full event description (plain text)
ticketTypes	Array of { name, price, currency, maxCapacity, isHidden }
categories	Array of { slug, name }

---

Sample output record

{
  "eventId": "evt-8DRVhINH9LTM7T4",
  "name": "Where Design Begins: An Open Exhibition",
  "url": "https://luma.com/nqkyxczb",
  "slug": "nqkyxczb",
  "startAt": "2026-06-04T18:00:00.000Z",
  "endAt": "2026-06-11T21:00:00.000Z",
  "timezone": "America/Los_Angeles",
  "locationType": "offline",
  "isOnline": false,
  "fullAddress": "488 Bryant St, San Francisco, CA 94107, USA",
  "city": "San Francisco",
  "region": "California",
  "country": "United States",
  "latitude": 37.7817006,
  "longitude": -122.3956533,
  "coverUrl": "https://images.lumacdn.com/...",
  "isFree": true,
  "isSoldOut": false,
  "isNearCapacity": false,
  "requireApproval": false,
  "guestCount": 142,
  "calendarName": "Vizcom",
  "calendarUrl": "https://luma.com/vizcom",
  "hosts": [
    {
      "name": "Vizcom",
      "username": "vizcom",
      "website": "https://vizcom.com/",
      "bio": "From Sketch to 3D in seconds.",
      "isVerified": true,
      "instagram": "vizcom",
      "twitter": "vizcomtech",
      "linkedin": "vizcom"
    }
  ],
  "hostCount": 1,
  "scrapedAt": "2026-06-04T12:00:00.000Z"
}

---

Host & organizer lead generation

Every event includes its organizers' contact and social footprint — name, username, website, bio, and handles for Instagram, X/Twitter, LinkedIn, TikTok and YouTube. Combine this with city/category discovery to build targeted lists like "every AI-event organizer in NYC, with their socials" — ideal for partnerships, sponsorships and outreach.

---

Pagination & scale

This Luma scraper is built directly on Luma's own JSON data layer (api.lu.ma), so there is no HTML parsing, no login and no browser — just fast, structured responses.

• Cursor pagination: city/category discovery and calendar pages are paged with a pagination_cursor. The actor automatically follows next_cursor page after page and stops when Luma reports has_more: false — so you collect every upcoming event, not just the first screen.
• Hundreds to thousands of events: add multiple cities, a category, or several calendars and the scraper keeps paginating across all of them, de-duplicating as it goes. A busy city or a large community calendar can return hundreds of events in a single run.
• Controlled by maxItems: set the exact number of events you want, or use 0 for no limit to pull the full set. The actor stops the moment it reaches your cap.
• Concurrency: maxConcurrency (default 5) controls how many requests run in parallel for faster large runs, with automatic retries (up to 5) on transient errors.

Because every record comes from the API, fields are complete and consistent — you won't see half-rendered rows or missing coordinates that plague browser-based Luma scrapers.

---

Tips & best practices

• 🌆 Use city slugs from the URL bar — open luma.com, go to a city, and copy the slug (e.g. sf, los-angeles).
• 🏷️ Combine city + category to focus on exactly the events you care about.
• 🧪 Start with maxItems: 50 to confirm your inputs.
• ⚡ Leave includeDetails off for fast, cheap discovery; turn it on when you need descriptions, ticket prices and categories.
• 💾 Use the Apify API / integrations to push results into Google Sheets, a database, or a webhook, and schedule runs to track new events.

---

Frequently asked questions

Can I get every event in a city? Yes — add the city slug to Cities and the actor paginates through all upcoming events.

Can I filter by topic? Yes — set Category (e.g. ai, tech, arts) alone or together with cities.

Do I get organizer contact info? Yes — each event includes its hosts with website, bio and social handles.

Can I scrape a single event or a community calendar? Yes — paste the URL into Luma URLs, or add a calendar handle to Calendars.

Do I get ticket prices and descriptions? Turn on Include full event details to add descriptions, ticket types/prices and categories.

What export formats are supported? JSON, CSV, Excel, XML, HTML table, RSS — plus the Apify API and integrations.

How many events can I scrape and how fast is it? There's no hard limit — the Luma scraper paginates through everything Luma returns. Discovery runs with includeDetails off are the fastest and cheapest; a single city typically finishes in well under a minute, and large multi-city runs scale to hundreds or thousands of events. Use maxItems to cap a run.

Do I need proxies or a login to scrape Luma? No login or API key is required. The actor uses Apify Proxy by default (datacenter is fine) and reads Luma's public data layer, so it works out of the box. You can plug in your own proxy via Proxy configuration if you prefer.

Is there a Luma API I can use instead? This actor is your Luma API: it wraps Luma's internal endpoints and returns clean JSON you can pull from the Apify API, a webhook, or a scheduled run — no need to reverse-engineer anything yourself.

How fresh is the data? Every run hits Luma live, so results reflect current upcoming events, guest counts, ticket availability and isNearCapacity/isSoldOut status at the moment of scraping. Schedule the actor to keep a dataset continuously up to date.

Can I scrape past events? The discovery and calendar endpoints return upcoming events. To capture a specific past event, paste its URL into Luma URLs — individual events are fetched directly by ID.

---

🔗 Related scrapers

Building event, venue or travel datasets? Pair this Luma scraper with other scrapers from the same author:

• 🎟️ Meetup Scraper — scrape Meetup groups and events with attendee counts and organizers.
• 🎫 Eventbrite Scraper — extract Eventbrite events, dates, venues and ticket prices.
• 🏨 Expedia Scraper — hotel listings, prices and availability from Expedia.
• 🛎️ HRS Scraper — business hotel rates and details from HRS.
• 🏡 Furnished Finder Scraper — mid-term furnished rentals for relocating event-goers and crews.
• ⛵ Yachtall Scraper — yacht and boat listings with prices and specs.

---

Changelog

Last updated: 2026-07-02 — Actor verified and maintained. Data pipeline tested for quality, structure and freshness; selectors/endpoints confirmed against the live site.

0.1.1

• Added isNearCapacity — a demand signal flagging events close to selling out, alongside isSoldOut and spotsRemaining.

0.1.0

• Initial release: discover events by city and category, scrape calendars/communities, and scrape individual events by URL.
• Cursor pagination, optional full-detail enrichment (description, ticket types, categories).
• Complete host/organizer profiles with social handles for lead generation.