Meetup offers two ways to authenticate with our API: OAuth and JWT. The right method depends on how your integration will be used and who needs access. This guide will help you choose the best option for your project.
🧑‍🧑‍🧒‍🧒 OAuth: For applications used by multiple Meetup accounts
OAuth is the best option when you’re building an application that other Meetup users will connect to. Each user gives your app permission to access their Meetup data—similar to how “Sign in with Google” works, but in the opposite direction.
When to choose OAuth
Choose OAuth if your application will allow multiple Meetup users (such as organizers, admins, or members) to:
Log into your tool
Authorize it to access their Meetup account
Manage events, groups, or other Meetup data through your interface
This is the most flexible option for platforms or tools intended for broad use.
How OAuth works
You create an OAuth client (client ID and secret).
Your application redirects users to Meetup’s authorization page.
Users review and accept a consent screen explaining what the app will access.
After approving, users are sent back to your app with an authorization code.
Your app exchanges that code for an access token and can make API requests on their behalf.
What to keep in mind
The creator of the OAuth client must have a Meetup Pro subscription—users who authorize your app do not need Pro.
Your app can access any user’s data only after they authorize it (and only within API schema limits).
Your developers can share the client ID and secret among their team.
All users will see the same app name when approving access.
👤 JWT: For single-account access and internal tools
JWT authentication is designed for customers who want to access only their own Meetup account data. This option is ideal for internal scripts, automated workflows, and dashboard integrations.
When to choose JWT
JWT is a great fit if you’re planning to:
Build internal automation (like announcing events automatically)
Export or sync your own network’s data
Create dashboards or reports for your organization
Avoid user login screens or individual authorization steps
Only the Meetup account that created the OAuth client will be represented in API calls.
How JWT works
You create an OAuth client using your Pro admin account.
Your tool generates a JWT token using that client’s credentials.
All API calls act as the single account that owns the credentials.
No authorization flow or user interaction is required.
What to keep in mind
JWT can only access the data of the account that created the OAuth client.
You can share your client ID, secret, and JWT token privately with your development team.
Anyone with those credentials can make the same API calls your account can, so manage them securely.
Still unsure which model fits your needs? Our team can help you choose the right path—just reach out through Support.