Agent-ready OpenAPI document · curated by JenticSocial MediaSocial Managementbearer4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For 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.
Use for: Find all upcoming Meetup events for a topic in my city, List the members of a group I organise, Create a new event for my group with a venue and description, RSVP yes to an event on behalf of a member
Not supported: Does not handle ticketing payment, livestream hosting, or non-Meetup social platforms - use for Meetup groups, events, members, and RSVPs only.
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.
Install Jentic One Beta
Connect the Meetup API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meetup API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeetup.com%2Fmeetup" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmeetup.com%2Fmeetup" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Meetup API.
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
Patterns agents use Meetup API for, with concrete tasks.
★ 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.
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.
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.
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.
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
4 endpoints — jentic publishes the only available openapi specification for meetup api, keeping it validated and agent-ready.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
M
Meetup API
- AI-Aware (A-)71/100
100
Foundational Compliance61
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
38%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
53%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
69%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Meetup API through Jentic.
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.
GET STARTED