Lu.ma Event Scraper

Collect public events from Lu.ma at scale — by keyword, location, and date.

The Lu.ma Event Scraper extracts structured event data from Lu.ma: names, dates, locations, hosts, cover images, and full event details. It's built for event aggregators, researchers, marketers, and anyone tracking online and in-person events worldwide.

⚡ Quick start

{
  "query": "party",
  "maxItems": 5
}

Or search several keywords with a location filter:

{
  "queries": ["party", "meetup"],
  "location": "Paris, Île-de-France",
  "maxItems": 5
}

🧩 Input

Field	Type	Required	Default	Description
query	string	one of query/queries	—	Primary search keyword(s). Merged with queries; duplicates removed (case-insensitive).
queries	array	one of query/queries	[]	Additional search keywords. Merged with query; duplicates removed (case-insensitive).
location	string	no	—	Location string that must appear on the event page. The more specific, the better (e.g. Paris, Île-de-France).
indexedDateAfter	string	no	—	Only events indexed by Google after this date, YYYY-MM-DD (indexing date, not event date).
indexedDateBefore	string	no	—	Only events indexed by Google before this date, YYYY-MM-DD (indexing date, not event date).
maxItems	integer	no	5	Maximum results per search keyword.
proxyConfiguration	object	no	{ "useApifyProxy": false }	Apify proxy settings.

You must provide at least one keyword: use query, queries, or both. Values are merged in order (query first, then each entry in queries); duplicates are removed (case-insensitive), and each remaining keyword runs as its own search.

How to find a good value for location

1. Open an example event page you'd like to scrape.
2. Find the location section on the event page.
3. Copy the location string.
4. Paste it into the location field.

A more concrete string (full address, venue name) yields more relevant matches.

📤 Output

Each scraped event is pushed to the dataset as one flat record. Lu.ma's own page data carries about fifty keys, most of them page furniture — payment-processor and analytics IDs, tint colours, font names, wallet-address requirements. The dataset keeps the event and drops the rest. Fields an event does not provide are returned as null rather than omitted, so the columns stay stable.

Every item includes the query field so you can tell which keyword produced it when running multiple searches.

Fields

Field	Type	Description
apiId	string	Lu.ma event ID.
url	string	Public Lu.ma event URL.
name	string	Event name.
description	string | null	Event description as plain text.
mainImageUrl	string | null	Event cover image URL.
startAt	string	Event start time (ISO 8601, UTC).
endAt	string | null	Event end time (ISO 8601, UTC).
timezone	string | null	IANA timezone the organiser set, e.g. America/Los_Angeles.
locationType	string | null	offline or online.
venue	string | null	Street address, when the organiser publishes it.
city / region / country / countryCode	string | null	Where the event takes place.
latitude / longitude	number | null	Approximate coordinates.
addressIsHidden	boolean	true when Lu.ma withholds the exact address until you register — venue is then null while the city still resolves.
hosts	array	Organisers: name, avatarUrl, bio, twitterHandle, linkedinHandle, instagramHandle, website.
calendarName / calendarUrl	string | null	The Lu.ma calendar the event belongs to.
categories	array	Category names, e.g. ["AI"].
isFree	boolean | null	Whether attendance is free.
price / maxPrice	number | null	Ticket price range in the major unit of currency.
currency	string | null	Currency of price.
requiresApproval	boolean | null	Whether the organiser approves each registration.
isSoldOut	boolean	Whether registration is closed for capacity.
spotsRemaining	number | null	Places left, when the organiser publishes a capacity.
ticketTypes	array	Tiers: name, description, cents, currency, maxCapacity, isSoldOut.
guestCount / ticketCount	number | null	Registered guests, and tickets issued.
query	string	Search keyword that produced this event.
fetchedAt	string	When the event was scraped (ISO 8601).

💡 Use cases

• Aggregators keep an events directory fresh across cities and topics.
• Researchers analyze event volumes, themes, and locations.
• Marketers track niche meetups and community events.
• Developers power calendar and discovery apps with structured data.

❓ FAQ

• What is Lu.ma? A fast-growing platform for organizing and discovering online and in-person events.
• What can be scraped? Any public Lu.ma event surfaced by keyword search, with optional location and date filters.
• What if Lu.ma changes its site? We maintain the scraper and update it when major changes affect functionality.

🔗 More scrapers by Anyx

• Dice.fm Event Scraper
• TikTok Trending Hashtags Scraper

🤝 Anyx Solutions

We build custom scrapers and data-extraction pipelines.

• Email: tantosthor@gmail.com

🖼 Image credit

Image credit: lu.ma