Meetup APIunofficial
Public event discovery and advertised schedules from signed-out Meetup pages.
- meetup.com
all live 2 operations, checked by the installs that call them.
Try it
Set up API Anything for your agents:
npx -y api-anything setupThen ask your agent, which finds this site by itself, or call it from a shell:
api-anything pull meetup
api-anything call meetup eventSchedule namespace=ananda-yoga-and-guided-meditation eventId=317020116Operations
| Operation | Method | Login | Writes | Status |
|---|---|---|---|---|
eventSchedule(namespace, eventId) -> title, start, scheduleRead the public title and scheduled time of one Meetup event. |
GET | no | no | Live0 confirmations |
listGroupEvents(namespace) -> title, url, schedule, namespace, eventIdList the public event cards advertised on a Meetup group home page, in page order. |
GET | no | no | Live0 confirmations |
Notes
Use a public group URL namespace for listGroupEvents. It returns the event cards selected on that group's home page in source order, including cards in past-event sections. Duplicate cards can link to the same event. This is a partial advertised collection, without a completeness, ranking or availability guarantee. Schedule is literal local wording and can omit the year. Keep each returned namespace/eventId pair together when calling eventSchedule. Discovery links retain their observed group context; eventSchedule retains its fixed home_logged_out_near_location context.
Use the namespace and event ID together from a public Meetup event URL for eventSchedule. The start includes its UTC offset; schedule is the event page's local wording. This reads the advertised schedule without confirming the event will happen. No attendance, cancellation, recurrence expansion, organizer, location or contact data.
About these operations
Each operation is a request learned from Meetup's own web pages: API Anything replays it over plain HTTP and falls back to a browser when it must. Read them as JSON.