Luma Events Scraper: lu.ma events to JSON avatar

Luma Events Scraper: lu.ma events to JSON

Pricing

from $1.00 / 1,000 event scrapeds

Go to Apify Store
Luma Events Scraper: lu.ma events to JSON

Luma Events Scraper: lu.ma events to JSON

Luma (lu.ma) events as JSON from keywords, city pages, calendars or event URLs: start/end, timezone, venue, coordinates, hosts, ticket price range, guest count and full description. From $1.50 per 1,000 events, no start fee.

Pricing

from $1.00 / 1,000 event scrapeds

Rating

0.0

(0)

Developer

subimpact

subimpact

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Public Luma (lu.ma / luma.com) events as clean JSON, one row per event. Give it search keywords, city pages, calendar pages or single event URLs — it mixes all four, removes duplicates and stops at your cap.

No browser, no login, no cookies, no API key: the actor calls the same public JSON endpoints the Luma website itself uses (api.lu.ma), so 50 events arrive in seconds using 256 MB of memory.

  • Search — "ai startup", "run club", "founders dinner"… anything Luma's own search finds.
  • Cities — walk a city's discover page: Singapore, Kuala Lumpur, New York, Berlin, Zurich and the rest.
  • Calendars — every upcoming event of one organizer calendar.
  • Single events — one URL, full row (always with the description).

What one row looks like

FieldMeaning
eventIdLuma's own event id (evt-XXXX), stable — use it to de-duplicate across runs
nameEvent title
urlPublic event URL (https://lu.ma/<slug>)
startAt, endAtStart and end time in UTC, ISO 8601 (timezone gives the organizer's local zone)
timezoneIANA timezone of the event, e.g. Asia/Singapore
cityCity of the venue
venueNameVenue / place name Luma resolved for the event
addressFull street address
lat, lngVenue coordinates
isOnlinetrue for online events
hostsArray of host / organizer names
organizerCalendarName of the Luma calendar the event belongs to (null for personal one-offs)
organizerCalendarUrlhttps://lu.ma/<calendar-slug> when the calendar has a public page
ticketPriceMin, ticketPriceMaxCheapest and most expensive visible ticket tier in major units (65 = CHF 65); across all tiers of the event
currencyISO code of the ticket prices (CHF, USD, SGD…), null when free
isFreetrue when Luma reports the event as free
guestCountPublic guest count, null when the organizer hides the guest list
coverImageUrlEvent cover image
descriptionPlain-text description (paragraphs, headings, list items), up to 8,000 characters — with includeDetails: true
source, sourceTypeWhich input produced the row (search, city, calendar, event-url)
statusok, partial (detail call failed, core fields still real) or error (not charged)
errorReason for an error row, or why a row is partial
scrapedAtISO timestamp of the run

Example input

Cheapest useful run — 20 events from Singapore, no detail calls:

{
"cities": ["singapore"],
"maxEvents": 20,
"includeDetails": false
}

Everything at once:

{
"searchQueries": ["ai startup", "run club"],
"cities": ["singapore", "kuala-lumpur", "nyc"],
"calendarUrls": ["https://lu.ma/readingrhythms-global"],
"eventUrls": ["https://lu.ma/ciul4l43"],
"maxEvents": 200,
"includeDetails": true
}
  • cities takes Luma's own discover slugs — the last part of a city page: singapore, frankfurt, zurich, berlin, kuala-lumpur, nyc (New York), sf (San Francisco). A full https://lu.ma/singapore also works. An unknown slug produces one status: "error" row that costs nothing, naming the slug format.
  • calendarUrls takes https://lu.ma/<calendar-slug>, a bare slug, or a cal-XXXX id.
  • eventUrls takes https://lu.ma/<event-slug>, a bare slug or an evt-XXXX id.
  • maxEvents (default 50, max 2000) is a hard cap for the whole run.
  • includeDetails (default on) fetches each event once more to fill description and the real ticket tiers. Turn it off to spend one request per page instead of one per event.

Example output

A real row from a live run ({"cities": ["singapore"], "maxEvents": 12}, description shortened here):

{
"eventId": "evt-7FyBURpr9MgBbn4",
"name": "Unconference: Community Day! | 2026",
"url": "https://lu.ma/4ibqnsto",
"startAt": "2026-11-15T04:00:00.000Z",
"endAt": "2026-11-15T13:00:00.000Z",
"timezone": "Asia/Singapore",
"city": "Singapore",
"venueName": null,
"address": null,
"lat": 1.2988922845254298,
"lng": 103.83483256641982,
"isOnline": false,
"hosts": ["3 of Us"],
"organizerCalendar": null,
"organizerCalendarUrl": null,
"ticketPriceMin": null,
"ticketPriceMax": null,
"currency": null,
"isFree": true,
"guestCount": 85,
"coverImageUrl": "https://images.lumacdn.com/uploads/eo/bcd18291-eee6-4ec7-8481-7c52e821e11a.png",
"description": "3 of Us is hosting our THIRD Unconference! And we're inviting you! :D\n\nWhat is an Unconference?\n\nAn Unconference is the opposite of a conference…",
"source": "singapore",
"sourceType": "city",
"status": "ok",
"error": null,
"scrapedAt": "2026-11-14T19:30:09.573Z"
}

Pricing

$1.50 per 1,000 events — one charge per event row delivered, no start fee. You pay only for events that actually land in your dataset: status: "error" rows (an unknown city slug, a deleted event URL) are free.

Good to know

  • Only public events. Private events, unlisted events and invite links that need a session are not returned — the actor never logs in and sends no cookies.
  • Hidden details stay hidden. Luma lets organizers hide the guest list and the exact address (the address is often revealed only after RSVP). Those rows have guestCount: null and venueName/address: null; the coordinates are still filled when Luma exposes them.
  • Online events are flagged by the organizer's own setting (isOnline). Many organizers describe an online webinar in the text without setting the flag, so treat isOnline: false as "not marked online", not as proof of a physical venue.
  • Recurring events come back as separate rows, one per occurrence (each with its own eventId and dates).
  • Past events are not walked: city and calendar sources return upcoming events only. A past event URL given explicitly still returns its row.
  • No proxy by default. Luma's public API answers plain requests at full speed. If your runs ever start seeing 403/429 answers, switch proxyConfiguration on — the actor retries 429/5xx twice either way.

Notes on sources

  • search = Luma discover search, paginated 50 per page.
  • city = the city's discover page, resolved through Luma's place lookup first, then paginated.
  • calendar = the calendar's upcoming events (period=future).
  • event-url = the single event, read from the page's own bootstrap data (no second call needed).
  • The same event found by two sources is delivered once; duplicates inside a run are skipped.