Pricing

Rating

Developer

Actor stats

Categories

Share

Eventbrite + Lu.ma + Meetup Events Scraper

Three event platforms, one scraper. Pull structured events from any Eventbrite, Lu.ma, or Meetup URL — name, description, start/end dates, venue + address + real lat/long, price, attendance mode, and the organizer/host/group behind each event (incl. website, social links, and best-effort contact email on Eventbrite & Lu.ma). Each row carries a source field (eventbrite, luma, or meetup) so you can keep all three in one dataset or split them. One row per event, JSON or CSV out, billed per result.

How it works

👁 How the Events Scraper works

✨ Why use this scraper?

Building an events feed across platforms? Prospecting organizers for sponsorship, venues, or services? Mapping active communities by topic and size? This actor pulls the full event and the organizer/host behind it — from all three platforms — into one consistent dataset.

• 🎯 Three platforms, auto-routed. Mix Eventbrite, Lu.ma, and Meetup URLs in one run. Each URL is classified by host and sent to the right parser — no separate actors, no separate runs.
• 🧩 One unified schema + a source tag. Every row uses the same core columns (name, dates, venue, geo, price, organizer) regardless of platform, with a source field so you can filter or split.
• 📧 Organizer/host lead-gen (Eventbrite & Lu.ma). Adds organizerWebsite, organizerDomain, organizerSocials, and a best-effort organizerEmail harvested from the organizer's own website. Turn an events list into an outreach list.
• 👥 Community data (Meetup). Each Meetup row carries its host group's member count, topics, and the event's RSVP/going count — ideal for finding active communities by size and subject.
• 📍 Venue + real coordinates. Venue, address, and latitude/longitude for in-person events; online events are flagged isOnline: true.
• 💰 Price + tickets. priceMin/priceMax/isFree across sources, plus on-sale window (Eventbrite) and approval/spots (Lu.ma).
• 🔁 Monitoring mode. Run on a schedule and get only NEW events each time — a private per-user record tracks what was already delivered.
• 🧰 No anti-bot, no auth. Reliable, fast parallel fetching. JSON + CSV exports.

🎯 Use cases

📥 Supported inputs

Pass any mix of URLs in startUrls — each is classified automatically by host. Leave startUrls empty to build an Eventbrite search from the convenience fields.

URLs are routed by host — each source uses its own purpose-built parser. All three share the core event + organizer columns; each adds a few source-specific fields:

• Eventbrite: saleStart/saleEnd, organizerFollowers, organizerEmail (harvested).
• Lu.ma: guestCount, requiresApproval, spotsRemaining, hostName, timezone, organizerEmail (harvested).
• Meetup: going, waitlist, maxTickets, groupMembers, groupUrlname, hostNames, topics. (No email lead-gen — Meetup groups are a closed community.)

Easiest workflow: run a search on eventbrite.com / luma.com / meetup.com in your browser, copy the URL from the address bar, and paste it (or several) into startUrls.

Not supported: authenticated/attendee data, and hosts other than eventbrite.*, luma.com/lu.ma, and meetup.com.

Note on the maxItems cap across sources: start URLs are processed in order, and maxItems is a single shared cap — so when you mix sources in one run, earlier URLs fill the budget first. For an even split across platforms, raise maxItems or run sources separately.

🔄 How it works

1. Classify each startUrl by host → Eventbrite, Lu.ma, or Meetup (or build an Eventbrite search from location + category + keyword).
2. Collect event links from listing/search/city/group pages, then fetch each event in parallel via a global sliding window.
3. Parse each source with its purpose-built extractor and map everything onto one unified schema with a source tag.
4. Enrich the organizer/host (Eventbrite & Lu.ma) — website, socials, and a best-effort contact email harvested from the organizer's own site. (Meetup adds the host group + member count inline — no extra fetch.)
5. Push one row per event to the dataset.

⚙️ Input parameters

📊 Output overview

Each scraped event is one single dataset row with a source field (eventbrite / luma / meetup). All three sources share the core event + organizer columns (so the dataset lines up); each adds its own extras. The organizer/host is merged inline — no separate rows, so the row count equals the event count exactly.

📦 Output samples

Eventbrite (source: "eventbrite") — organizer website + harvested email:

{
"source":"eventbrite",
"type":"event",
"eventId":"1984643225312",
"name":"The 2026 Gracies Luncheon",
"startDate":"2026-06-16T11:00:00-04:00",
"isOnline":false,
"venueName":"Cipriani 42nd Street",
"addressLocality":"New York",
"latitude":40.7515845,
"longitude":-73.9771076,
"priceMin":215.26,
"priceMax":482.02,
"currency":"USD",
"isFree":false,
"category":"Business",
"organizerName":"Alliance for Women in Media",
"organizerWebsite":"https://allwomeninmedia.org/",
"organizerEmail":"info@allwomeninmedia.org",
"organizerFollowers":75,
"scrapedAt":"2026-06-10T14:48:58.354Z"
}

Lu.ma (source: "luma") — host calendar + socials + harvested email + Lu.ma extras:

{
"source":"luma",
"type":"event",
"eventId":"evt-kTedGXXQYZLkTdB",
"eventUrl":"https://luma.com/harnesshack",
"name":"Harness Engineering Hack",
"startDate":"2026-06-12T16:30:00.000Z",
"timezone":"America/Los_Angeles",
"isOnline":false,
"addressLocality":"San Francisco",
"country":"United States",
"latitude":37.789,
"longitude":-122.396,
"isFree":false,
"requiresApproval":true,
"spotsRemaining":805,
"guestCount":0,
"hostName":"AWS Builder Loft",
"organizerName":"tokens&",
"organizerWebsite":"https://tokensand.ai/",
"organizerSocials":["https://twitter.com/tokensandai","https://www.linkedin.com/company/tokensand"],
"organizerEmail":null
}

Meetup (source: "meetup") — host group + member count + RSVP/going + topics:

{
"source":"meetup",
"type":"event",
"eventId":"315135716",
"eventUrl":"https://www.meetup.com/joinmytrip-dublin-travel-club/events/315135716/",
"name":"Novalja Summer Getaway",
"startDate":"2026-06-22T19:00:00+01:00",
"eventType":"PHYSICAL",
"isOnline":false,
"venueName":"Novalja",
"addressLocality":"Novalja",
"country":"hr",
"latitude":44.556763,
"longitude":14.882576,
"isFree":true,
"going":1,
"waitlist":0,
"organizerName":"The Dublin Travelers Club - JoinMyTrip",
"organizerUrl":"https://www.meetup.com/joinmytrip-dublin-travel-club",
"groupMembers":5803,
"category":"Travel & Outdoor",
"hostNames":["Gabo"],
"topics":["Travel","Solo Travelers","Vacations"]
}

🗂 Key output fields

Fields not applicable to a given source are returned as null so every row has the same shape.

❓ FAQ

Which platforms and URLs are supported? Eventbrite (search /d/..., event /e/..., organizer /o/...), Lu.ma (event luma.com/{slug}, city/calendar pages), and Meetup (find /find/?source=EVENTS&..., group /{group}/events/, event /{group}/events/{id}). Each URL is auto-classified by host. Anything else is skipped.

How do I tell the sources apart in the output? Every row has a source field — eventbrite, luma, or meetup. Core columns are identical across sources; each adds source-specific extras (see Key output fields).

Why is organizerEmail sometimes null? It applies to Eventbrite and Lu.ma only (Meetup is a closed community and exposes no organizer contact). For those two, the actor finds the organizer's own website and best-effort extracts a public contact email; if no site is linked or no email is exposed, the field is null — that's expected.

Why are some venue/geo fields null? Those are online events (isOnline: true) — there's no physical venue.

Does it paginate? Eventbrite search pages paginate via ?page=N and are walked automatically. Lu.ma city pages and Meetup find pages return the events present on the page (Meetup uses cursor pagination, not numbered pages) — pass multiple URLs for breadth.

How does monitoring mode work? With monitoringMode: true, events whose ID was already delivered to you are skipped (no fetch, no charge). The first run seeds your baseline; later runs return only new events.

Can I scrape private or attendee data? No. Only publicly available event and organizer/group pages — no logged-in content, no attendee data.

💬 Support

• For issues or feature requests, please use the Issues tab on the actor's Apify Console page.
• Author's website: https://muhamed-didovic.github.io/
• Email: muhamed.didovic@gmail.com

🛠 Additional services

• Custom output shape, extra fields, or one-off datasets: muhamed.didovic@gmail.com
• Need another event / ticketing source added (Ticketmaster, Dice, Bandsintown, etc.)? Drop an email.
• For API access (no Apify fee, just a usage fee for the API): muhamed.didovic@gmail.com

🔎 Explore more scrapers

If this Events Scraper was useful, see other scrapers and actors at memo23's Apify profile — covering events, job boards, real estate, social media, and more.

⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Eventbrite, Inc., Lu.ma, Meetup, or any of their subsidiaries or affiliates. All trademarks mentioned are the property of their respective owners.

The scraper accesses only publicly available event, organizer, and group pages on eventbrite.com, luma.com, and meetup.com — no authenticated endpoints, attendee data, or content behind a login. The best-effort organizer email (Eventbrite & Lu.ma) is collected from the organizer's own public website. Users are responsible for ensuring their use complies with each platform's Terms of Service, applicable data-protection law (GDPR, CCPA, etc.), and any contractual obligations of their own organisation, including lawful basis for any outreach.

SEO Keywords

eventbrite scraper, luma scraper, lu.ma scraper, meetup scraper, events scraper, event data api, multi-source events scraper, scrape eventbrite, scrape luma events, scrape meetup events, eventbrite organizer emails, luma host emails, event lead generation scraper, event organizer leads, meetup group members scraper, meetup rsvp data, eventbrite ticket price scraper, scrape events by city, event aggregator feed, event marketing leads, sponsorship prospecting, eventbrite api, meetup api, luma api alternative