Luma Events Scraper – lu.ma Events & Organizer Leads avatar

Luma Events Scraper – lu.ma Events & Organizer Leads

Pricing

from $1.50 / 1,000 events

Go to Apify Store
Luma Events Scraper – lu.ma Events & Organizer Leads

Luma Events Scraper – lu.ma Events & Organizer Leads

Get public Luma (lu.ma) events by city and topic, calendar or URL. Returns name, dates, venue, coordinates, price, sold-out status and guest count, plus each organizer's public profile, website and social links. Built for event discovery and organizer lead lists. No login needed.

Pricing

from $1.50 / 1,000 events

Rating

5.0

(1)

Developer

Spase Nikolov

Spase Nikolov

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 hours ago

Last modified

Features

Limited permissions

Share

This Actor returns public events from Luma (lu.ma) for the cities (optionally narrowed to a topic), calendars or event links you give it. Each row has the event name, start and end time, venue, address and coordinates when Luma shows them publicly, price, sold-out status and guest count. With organizer details switched on, each row also carries the organizer's name, Luma page, website, public X, LinkedIn and Instagram links, and the host names. No Luma login is needed.

Use this to

  • Discover events in a city, optionally on one topic, such as AI events in London next month.
  • Build a lead list of event organizers with their websites and social links.
  • Monitor a calendar for new events by scheduling a run with onlyNew turned on.
  • Research sponsorship and partnership targets by seeing who runs events in your field and how large they are.

Sample output

recordTypenamestartAtcitypriceMinguestCountorganizerNameorganizerWebsite
eventFounders and Builders Meetup2026-12-04T18:30:00.000ZSan Francisco0142Bay Buildershttps://example.com

Every event row has the same 26 fields, including eventId, url, timezone, venueName, address, latitude, longitude, isOnline, category, isFree, priceCurrency, soldOut, organizerUrl, organizerTwitter, organizerLinkedin, organizerInstagram and hostNames. A value Luma does not publish is returned as null. The organizer fields are null when organizer details are off or Luma publishes none. hostNames is an empty list (never null) when there are no hosts or organizer details are off.

Pricing

You pay per event:

  • event: $0.0015 for each event returned.
  • organizer-details: $0.003 for each event that has organizer data, only when organizer details are on.

Examples: 20 events with organizer details cost at most $0.09. 100 events without organizer details cost $0.15.

Explanatory rows (see below) are never charged. The run stops when it reaches your spending limit.

Input

  • cities: accepts city names or Luma city slugs, such as san-francisco or london. Returns upcoming events in and around each city.
  • categories: optional topics that narrow the cities, so you get topic events in and around each city: family, books, games, tech, food, ai, running, arts, climate, fitness, wellness, crypto. It needs cities; without them the run returns an invalid_input row.
  • calendarUrls: links to Luma calendar or community pages, such as https://lu.ma/ls. Their events are returned as they are, whatever categories says.
  • eventUrls: links to single Luma events, such as https://lu.ma/abc123xy. Returned as they are, whatever categories says.
  • dateFrom / dateTo: the first and last day to include, written YYYY-MM-DD, inclusive. A dateFrom after dateTo, or a date not in YYYY-MM-DD form, returns an invalid_input row.
  • maxEvents: the most events to return in total, 1 to 500 (default 20). Each returned event is charged.
  • includeOrganizerDetails: adds organizer name, Luma page, website, social links and host names (default on).
  • onlyNew: returns only events not returned by earlier runs with the same sources (default off).

Send at least one of cities, calendarUrls or eventUrls. categories only works together with cities.

What you get when nothing matches

When nothing matches or the input needs correcting, the run succeeds and returns a short explanatory row instead of an empty result. If Luma cannot be reached and nothing could be returned, the run fails with a clear message. If only some sources could be reached, you get their events plus a partial row for each source that could not. The explanatory row has recordType: "status", a message in plain language and a subject naming what it refers to. The status is one of:

  • no_results: nothing matched the input, or nothing new appeared since the last run.
  • invalid_input: the input could not be used, for example no source or a malformed date.
  • not_found: a city, category or link was not found on Luma.
  • partial: a source could not be reached or was only partly scanned.
  • limit_reached: the run stopped at your spending limit.

What it never returns

Guest lists, attendee data, email addresses, phone numbers, and addresses that Luma shows only to registered guests.

FAQ

How are dates compared? By UTC day. An event late in the evening local time can fall on the next UTC day.

Do I need a Luma account? No. The Actor reads only public information.

How does onlyNew remember events? The Actor stores the IDs of events it has returned in a key-value store named luma-events-scraper-seen in your own Apify account, separately for each combination of sources. A later run with the same sources skips them. Changing the sources starts a fresh list.

This Actor reports usage statistics to its developer to keep it reliable: the Actor's name and build number, the time of the run, the run's outcome, row counts, events charged, an estimate of the revenue from those events, an estimate of what paid data sources cost for the run (always zero for this Actor), duration, a short error category when a run fails, partly fails or meets upstream data in an unexpected shape, how the run was started, whether the account is on a paid plan, and a one-way hash of the Apify user ID. It never reports your inputs or the data returned.