Meetup Events Scraper
Pricing
from $0.03 / 1,000 result extracteds
Collect public Meetup event records from URLs or keyword searches. Export dates, venues, organizer labels and RSVP counts when available; coverage varies.
Public https://www.meetup.com/ find, group, or event URLs. Use these, Keywords, or both; at least one usable URL or keyword is needed (up to 100 combined source URLs). Only events exposed on each fetched page are collected; a group URL does not guarantee a complete calendar.
Terms used to construct Meetup search URLs. Results can include Meetup recommendations outside the requested topic. The Actor does not enforce keyword matching or offer a sort control.
Location text added to keyword search URLs, such as Berlin, Germany. This does not modify Start URLs. Meetup may resolve a different location, so inspect returned cities before using a regional dataset.
Shared upper limit on saved events across all sources, from 1 to 10000. The form/schema default is 10; when an API input reaches the runtime without this key, its fallback is 25. This is a ceiling, not a promise of coverage or a minimum result count.
Open discovered event detail pages for additional public fields. Enabled by default. Disable for a smaller sampling workload. Missing fields remain null; enrichment does not guarantee complete data.
Legacy accepted field, currently not used by the entrypoint. To retry pending sources from RUN_SUMMARY, put their URLs in Start URLs. No automatic checkpoint continuation is provided.
Optional connection settings used from the first request when configured. The form prefill explicitly disables Apify Proxy; omission is passed to the Apify SDK unchanged. Existing proxyConfiguration values, managed settings, custom proxy URLs and explicit opt-outs are passed through without a new selector or override. There is no automatic switch from a failed direct request to a paid proxy. Use only valid SDK proxy configuration; invalid settings are not converted to a fallback. Proxy use can incur platform charges.
