Luma Events Scraper - by City, Calendar or URL (lu.ma)
Pricing
from $1.50 / 1,000 results
Luma (lu.ma) event scraper: public events by city, organiser calendar or pasted URL with start/end and time zone, city, online/in-person, price range, registration status and guest count. Filters: keyword, dates, category. Event facts only, no host/guest data. Unofficial; not affiliated with Luma.
Luma city pages to read, one per line: a city slug or name, e.g. "sf", "San Francisco", "nyc", "london", "tokyo", "berlin". Each city page carries the first 20 events Luma shows for that city. Also accepted: "all" (every Luma city, 87 pages) or a continent: europe, na (North America), apac (Asia & Pacific), sa (South America), africa. A city page URL (https://luma.com/tokyo) works too. If both Cities and URLs are empty, the Quick start cities are used; if URLs are given while this still holds the pre-filled list, only the URLs are read.
[ "sf", "nyc"]Optional. Public Luma pages pasted from your browser, one per line: an event (https://luma.com/abc123de or https://lu.ma/abc123de), an organisation or community calendar (https://luma.com/) or a city page. A calendar returns its listed upcoming events. Personal calendars and user profiles (luma.com/user/...) are not read.
[]Optional filter on Luma's own event categories: ai, tech, crypto, arts, climate, fitness, wellness, running, food, books, games, family (names such as "Food & Drink" also work). Keeps only events Luma tagged with at least one of them. Needs each event's page (one extra request per event, slower); Luma tags only some events, so this filter can remove many.
[]Optional. Keeps events whose title, organiser calendar or venue contains every word (not case- or accent-sensitive), e.g. "hackathon" or "AI founders". Applied to the events listed on the pages you choose; it does not search all of Luma.
Optional. Keep events starting on or after this LOCAL date: YYYY-MM-DD (e.g. 2026-10-20), "today", "tomorrow" or "+7d". Leave empty for no lower bound.
Optional. Keep events starting on or before this LOCAL date (inclusive): YYYY-MM-DD, "today", "tomorrow" or "+30d". Leave empty for no upper bound.
Also read every event's own page: adds Luma's categories, and for calendar events the price range, registration status, guest count, city and organiser. One extra request per event (about 1.5 s each). Turned on automatically when the categories filter is used.
Calendars can list events hosted on other websites. When on (default), they are returned with platform "external", their own URL, dates and city (no price or guest data).
Maximum number of event records for the whole run (1..10000; values outside are clamped). The run stops reading pages once this many events are stored.
Hard budget of page requests to luma.com for the whole run (1..2000; clamped): one per city / URL page plus one per event page when event pages are opened. Requests are strictly serial, at least 1.5 s apart. If the budget runs out, the run still SUCCEEDS with what it has and complete=false in the RUN_SUMMARY record.
Apify proxy settings. Default: Apify RESIDENTIAL proxies, country US — luma.com sometimes rate-limits Apify datacenter IPs (HTTP 429 "Rate Limit Hit" on 1 of 6 datacenter test runs, 2026-10-13), while the same requests through a residential IP were answered. One sticky session (one IP) is kept for the whole run, never rotation; only if the very first request is refused is it retried once on a fresh session. Set {"useApifyProxy": false} to run without a proxy.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "US"}