Meetup Events Scraper

What this Actor scrapes

Meetup is where AI, data, startup, and tech communities run their events — and every public listing is a B2B-intent signal. This Actor searches Meetup's public events feed by keyword (optionally scoped to a city), reads each event's server-rendered data (no login, no API key), and turns it into clean, structured rows: when and where the event is, whether it's in-person or online, how many people are going, the capacity, the fee, and which group is hosting it — with a direct link to that group's Meetup page.

Pair it with our Lu.ma Event Discovery Scraper for a two-Actor events-intelligence suite covering the same B2B buyer across both platforms.

What we handle for you

• 🛡️ Browser fingerprint impersonation — curl-cffi mimics real Chrome / Firefox / Safari TLS handshakes so Meetup serves a browser, not Python.
• 🌐 Proxy rotation via Apify Proxy — a fresh session and exit IP whenever you need one.
• 🔁 Retries with exponential backoff on 403 / 408 / 429 / 5xx — up to 5 attempts per page, so a transient block never costs you a row.
• 🧮 Aggregate RSVP counts, no PII — we emit the "going" count only; individual attendee identities are never touched.
• 🧊 Clean, typed dataset rows — Pydantic-validated, ISO-8601 timestamps, stable IDs, JSON / CSV / Excel export straight from the Apify Console.
• 💰 Pay-Per-Event pricing — you only pay for events that land in your dataset. No data, no charge.

Use cases

• Event-led lead gen — surface hosting groups and their Meetup pages for the topics your buyers care about.
• Community & ecosystem mapping — track which AI / data / startup groups are active in a city over time.
• Competitive intelligence — watch a rival's or partner's event cadence, turnout, and pricing.
• Sponsorship prospecting — find well-attended events worth a partnership pitch, ranked by going count.
• Trend research — aggregate events across keywords and cities to spot what's heating up.

Input

Paste this into the Apify Console, or send it as the run input over the API. Proxy settings are on by default; you rarely need to touch them.

{
  "keywords": [
    "ai",
    "startup"
  ],
  "location": "New York, NY",
  "eventType": "any",
  "maxEventsPerKeyword": 50,
  "includeDescription": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

Output

One row per result, schema-validated before it is written. Export JSON, CSV, Excel or XML from the run, or read it over the API.

titleevent_urldate_timeevent_typeis_onlinegoing_countmax_ticketsis_freefee_amountfee_currencyvenue_namevenue_cityvenue_stategroup_namegroup_url

{
  "search_keyword": "ai",
  "event_id": "315229748",
  "title": "Build the AI Future: LinuxONE & IBM Hands-On in NYC",
  "event_url": "https://www.meetup.com/ai-modeling-and-machine-learning-in-action-sponsored-by-ibm/events/315229748/",
  "date_time": "2026-07-21T08:30:00-04:00",
  "event_type": "physical",
  "is_online": false,
  "going_count": 50,
  "max_tickets": 50,
  "is_free": true,
  "fee_amount": null,
  "fee_currency": null,
  "venue_name": "IBM 1 Madison Avenue",
  "venue_address": "1 Madison Avenue",
  "venue_city": "NYC",
  "venue_state": "NY",
  "venue_country": "us",
  "latitude": null,
  "longitude": null,
  "group_name": "IBM AI - New York City",
  "group_url": "https://www.meetup.com/AI-Modeling-and-Machine-Learning-in-Action-Sponsored-by-IBM/",
  "description": "Join us in New York City for a full-day, hands-on meetup...",
  "scraped_at": "2026-07-10T15:00:00+00:00"
}

Pricing

You pay only for results that land. Cap any run with maxTotalChargeUsd. See pricing & billing for worked examples.

Limitations

• Per-keyword results are page-limited. Meetup's public find feed serves roughly the first ~27 events per search, and it does not expose a reliable cursor for deep pagination on this surface. We deliberately do not ship a fragile pagination hack (reliability beats depth — a Devil Scrapes rule). To widen coverage, run several keywords (and/or several locations) in one run; each keyword is its own search.
• Geo coordinates are sparse. The find feed exposes venue name and address but usually not latitude / longitude, so latitude / longitude are frequently null.
• Public feed only. Private, members-only, or draft events are not accessible.
• Attendee lists are out of scope — see Privacy & GDPR above.