canonical: https://jentic.com/apis/meetup.com/meetup

# Meetup API

Jentic publishes the only available OpenAPI specification for Meetup API, keeping it validated and agent-ready. Meetup's v3 API is a GraphQL surface for accessing and managing groups, events, members, and RSVPs across the Meetup platform. The OpenAPI spec exposes 4 endpoints: the GraphQL endpoints /gql and /gql-ext for queries and mutations, plus /oauth2/authorize and /oauth2/access for the OAuth 2.0 flow that mints bearer tokens. Use it to discover events near a location, RSVP on behalf of a member, or pull group analytics into another product.

## For AI agents

Query Meetup groups, events, members, and RSVPs via GraphQL and run mutations to create or update events so an agent can manage Meetup activity from another platform.

## Scope

Does not handle ticketing payment, livestream hosting, or non-Meetup social platforms - use for Meetup groups, events, members, and RSVPs only.

## Capabilities

- Query groups by location, topic, or organiser through the /gql GraphQL endpoint
- Read upcoming and past events for a group including attendee counts and venue
- Create or edit an event on behalf of a group organiser via GraphQL mutations
- RSVP a member to a specific event and record their response
- Look up a member's profile, group memberships, and event history
- Exchange an OAuth 2.0 authorization code for an access token using /oauth2/access

## Use cases

### Community Event Aggregation

Aggregate upcoming Meetup events by topic and city into a community newsletter, internal dashboard, or partner site. The /gql endpoint lets a single GraphQL query pull groups, events, venues, and attendee counts in one round-trip, which is ideal for nightly aggregation jobs. Community managers use this to surface what is happening across many partner groups without scraping the Meetup site.

Example prompt: Send a GraphQL query to /gql that returns events in city=Berlin with topics=python in the next 30 days, including event title, date, and venue name.

### Programmatic Event Publication

Publish events into Meetup from an internal events tool so organisers do not maintain duplicate calendars. A GraphQL mutation against /gql creates the event with title, date, venue, and description, and the agent can update it later if details change. This is useful for organisations running a portfolio of Meetup groups synchronised with a CMS.

Example prompt: Run a GraphQL mutation against /gql to create an event titled Quarterly Hack Night for group urlname=berlin-py with start time 2026-07-15 18:00 and an online venue.

### RSVP-Driven Capacity Planning

Use the GraphQL surface to read RSVP counts in real time and reconcile them with venue capacity, waitlist policy, and AV requirements. Operations teams hit /gql at intervals leading up to an event and decide whether to enable the waitlist or release more spots. This avoids the operational drag of refreshing the Meetup UI and copying numbers into a planning sheet.

Example prompt: Query /gql for the RSVPs on event id 12345 every hour, return going_count and waitlist_count, and post a Slack message when going_count crosses the venue_capacity threshold.

### Agent-Driven Group Onboarding

When a new community is launched, an agent can stand up the Meetup group's first three events, invite founding members, and confirm their RSVP without a community manager touching the dashboard. Through Jentic the agent searches for the create-event mutation, loads the GraphQL schema, and executes the mutation chain safely. This collapses a multi-hour onboarding playbook into one agent run.

Example prompt: Create three weekly events for group urlname=ai-builders with titles supplied by the user, then send RSVP mutations for the supplied list of founding members.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /gql | Run GraphQL queries and mutations against Meetup data |
| POST | /gql-ext | Extended GraphQL endpoint for additional schema fields |
| GET | /oauth2/authorize | Begin the OAuth 2.0 authorization code flow |
| POST | /oauth2/access | Exchange an authorization code for a bearer access token |

## Key resources

- **GraphQL** — Run queries and mutations against the Meetup data graph including groups, events, members, and RSVPs
- **Authentication** — OAuth 2.0 authorize and access endpoints to mint bearer tokens for member-scoped calls

## Why Jentic

- **Setup:** Wiring Meetup by hand means running its OAuth 2.0 authorize and access exchange, refreshing bearer tokens, and composing GraphQL documents for its /gql endpoint. Through Jentic you install once, import the Meetup API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Meetup routes everything through a single GraphQL endpoint (POST /gql) where the query or mutation travels in the request body, so scope the agent to the operations it needs, such as reading upcoming events or RSVPs. You choose the operations it may call, so a mutation that changes a group runs only if you include it.
- **Credential handling:** Your Meetup OAuth 2.0 token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list upcoming Meetup events for a city' or 'get RSVPs for an event', and Jentic returns the matching /gql operation with a GraphQL schema fragment so the agent calls the right query without browsing the reference docs.

## Related APIs

- **Facebook Graph API** — Facebook Events covers a broader social graph than Meetup's group-centric model.
- **Ticketmaster Discovery API** — Ticketmaster Discovery surfaces ticketed live events at venue scale.
- **Google Calendar API** — Google Calendar handles personal calendar entries derived from Meetup events.
- **Twilio Messaging API** — Twilio Messaging delivers SMS reminders to Meetup attendees ahead of an event.

## FAQ

### Why is there no official OpenAPI spec for Meetup API?

Meetup ships a GraphQL API rather than a REST OpenAPI specification. Jentic generates and maintains an OpenAPI wrapper so that AI agents and developers can call Meetup API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Meetup API use?

Meetup uses OAuth 2.0: redirect users through /oauth2/authorize to grant access, then exchange the code at /oauth2/access for a bearer token sent in the Authorization header. Through Jentic the bearer token is stored encrypted in the vault and injected per request.

### Can I create or edit Meetup events via the API?

Yes. Send a GraphQL mutation to /gql with the create-event or edit-event field - the calling user must be an organiser of the target group and the bearer token must carry the matching scope.

### What are the rate limits for the Meetup API?

Meetup applies per-token rate limits and points-based GraphQL cost accounting. Heavy aggregation queries should batch fields and respect the X-RateLimit-Remaining header on responses; if you hit a 429, back off through Jentic before retrying.

### How do I query upcoming events through Jentic?

Search Jentic for query Meetup events in a city, load the schema for the /gql operation, and execute with the GraphQL document for the events query plus the desired filters. Jentic returns the GraphQL data block with events, venues, and counts ready to render.

### Can I use the Meetup API without organiser permissions?

Yes for read queries - public group and event data is visible to any authenticated bearer token. Write mutations such as creating events or editing groups require the user to be an organiser of the target group.

### Can I limit what my agent is allowed to do with the Meetup API?

Yes. Because Jentic One is self-hosted, you set the rules for which Meetup operations your agent may call. Meetup routes everything through a single GraphQL endpoint (POST /gql), so you can scope the agent to only the queries it needs, such as reading upcoming events or RSVPs, and exclude mutations that create or edit events and groups. A group-changing mutation runs only if you explicitly allow it, and the OAuth 2.0 bearer token stays under your control rather than in the agent's context.