# Changelog of Meetup Scraper - Events, Groups & Members Data Extractor (`haketa/meetup-scraper`) Actor

- **URL**: https://apify.com/haketa/meetup-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/meetup-scraper.md

## Changelog

### 1.0.1 — 2026-11-02

- **Verified against the live site.** A fresh search run (8 broad keywords in New York, `maxItems: 450`) returned **450 unique events in ~43 seconds** on default datacenter proxies, with **0 duplicates** on the event ID key.
- **Core-field coverage 100%.** `type`, `id`, `title`, `url`, `startDateTime`, `endDateTime`, `eventType`, `goingCount`, `status`, `groupName`, `groupUrl` and `groupMemberCount` were all populated on 100% of records; `venue` ~92%, `description` ~94%. No value bugs (`[object Object]`, scheme-less URLs, wrong types) were found.
- **Group & member modes re-verified.** A group-URL run confirmed rich group records (member count, category, organizer, coordinates, founded date, timezone, join mode) and working member extraction with role flags (`isOrganizer`/`isLeader`/`isProOrganizer`) at 100%.
- **README refreshed to the gold standard.** Output examples and the field reference now mirror real live-run data; added honesty notes on data-dependent fields (free events have no `feeAmount`, online events carry a placeholder venue, and Meetup now exposes only a thin public member profile so `bio`/`city`/`photo` are often `null`).
- No changes to input or output field names — fully backward compatible.

### 1.0.0 — 2026-07-02

- Initial public release of the Meetup Scraper.
- Three input modes: keyword + city search, event URLs, and group URLs (with optional group events and member sample).
- Extracts events, groups and members from Meetup's public GraphQL gateway with exact RSVP counts, fees, venues (lat/lon), hosts, topics and organizer data.
- Automatic city geocoding, cursor pagination (50 records/page), event de-duplication, datacenter→residential proxy escalation, and per-IP throttle retries.
- Export to JSON, CSV, Excel, HTML, XML or via the Apify API.