Luma Events Scraper

Extract events from Luma (lu.ma / luma.com) city pages into clean JSON or CSV: event name, date, venue city and coordinates, guest count, ticket pricing, the hosting calendar, and every host's profile with Instagram, LinkedIn and X links. Point it at "sf" or "nyc", get back the full upcoming event feed for that city in under a minute.

What you get

One record per event:

{
    "eventId": "evt-71eqD0JrBrCBHRk",
    "name": "The California Peptide Club IV",
    "url": "https://luma.com/californiapeptideclub4",
    "startAt": "2026-07-25T01:00:00.000Z",
    "timezone": "America/Los_Angeles",
    "city": "San Francisco",
    "neighborhood": "Clarendon Heights",
    "latitude": 37.7559,
    "longitude": -122.4523,
    "guestCount": 118,
    "ticketInfo": { "is_free": false, "require_approval": true },
    "calendarName": "Personal",
    "calendarInstagram": null,
    "hosts": [
        {
            "name": "Julius Ritter",
            "verified": false,
            "instagram": "jlsritter",
            "linkedin": "/in/juliusritter",
            "twitter": "JuliusYRitter"
        }
    ]
}

Monitor new Luma events on a schedule

Turn on Monitor mode (onlyNewEvents) and the scraper remembers every event it has delivered. Each following run returns only events published since the last run. Put it on a daily Apify Schedule and you have a hands-off new-event feed for any city, ready to push into Slack, Google Sheets, a CRM or a webhook through Apify integrations.

You are only charged for events actually delivered. A monitor run that finds nothing new costs you nothing beyond the run start.

Who uses this

• Sales and sponsorship teams tracking AI, tech and startup events in their target cities, with host socials ready for outreach
• Community and event teams watching what competing organizers are running and how full their events get
• Newsletter and content curators auto-building "events this week" sections
• Market researchers measuring event volume and topics by city over time

Input

Field	Type	Description
sources	array	City slugs (sf, nyc, london), full city URLs, or single event URLs
maxEventsPerSource	integer	Events to scan per source (default 200)
onlyNewEvents	boolean	Monitor mode: deliver only events not seen in previous runs
proxy	object	Optional. Runs without a proxy by default

Pricing

Pay per event delivered. No subscription, no rental fee. A run that delivers nothing new costs nothing beyond the run start event.

FAQ

Which cities work? Any city with a Luma discover page: sf, nyc, la, london, singapore, tokyo, berlin, sydney and dozens more. Any luma.com/<city> URL works as input.

Does it scrape attendee lists? No. It extracts public event and host information only. Guest counts are included as numbers; personal attendee data is never touched.

Can I get results as CSV or Excel? Yes. Every Apify dataset exports as JSON, CSV, Excel or XML from the run page or via API.

How fresh is the data? Live. Every run reads Luma's current public pages at run time.

Can it feed my own app? Yes. Call the actor through the Apify API or an MCP client and read the dataset programmatically.