A Meetup API alternative for community and local events

By Elliot Harris, FindLocal · Last verified September 26, 2026

We checked Meetup's details against their public docs on September 26, 2026. Things change, so follow the source links. FindLocal's numbers come live from our database. Meetup is a trademark of its owner, and this page isn't affiliated with or endorsed by them. Spotted a mistake? Email a correction.

What Meetup’s API does well

Meetup organizes everything around groups: organizers, members, RSVPs. If you run a network of chapters, say a user group in forty cities or a nonprofit with local branches, the GraphQL API lets you automate it. You can publish events, read RSVPs and report across a Pro network. That’s the product Meetup Pro sells, and API access comes with it.

Why it’s hard to use for a discovery app

Getting access is the first problem. Meetup’s help center says only members with an active Meetup Pro subscription can create new OAuth consumers, and that having Pro doesn’t guarantee approval. Pro is priced per group and aimed at organizers. If you’re building a consumer app that shows what’s on nearby, you’d be paying for organizer tools you won’t use just to reach the API.

The API has also moved around. The REST API is gone, and in February 2025 the GraphQL schema changed again: keywordSearch became eventSearch and groupSearch, and some fields were renamed. Rate limits are counted in query points (500 per 60 seconds), so a request’s cost depends on how deep the query goes.

Then there’s coverage. Meetup only knows about events run by Meetup groups, and plenty of local events live on a venue’s own calendar instead. A brewery’s Tuesday trivia, a comedy club’s open mic and a library’s toddler storytime usually aren’t on Meetup. People clearly want this data, judging by how many Meetup scrapers exist. But a scraper that breaks Meetup’s terms of service is a risk to your product.

How FindLocal handles it

We collect events from the venues directly, every day, and keep them in one catalogue. It leans toward the small recurring events that make a neighborhood feed worth opening. The table above counts them from the live data.

The API is REST with ordinary query parameters. Creating a key takes a few minutes and the free tier doesn’t ask for a card. The same key works with our MCP server if you’re building an AI agent. Each event comes back as flat JSON with the title, date and start time in the venue’s time zone, venue name and coordinates, neighborhood, category, price, image, and links to the event and ticket pages.

Moving a Meetup-based feed over

Most local-events features built on Meetup find events near a point, filter by topic and show the next few weeks. On FindLocal that’s one request:

• Near a point: near=<lat>,<lng>&radius_km=<n> sorts by distance. Or use city=<slug>.
• By topic: cat= with slugs like community, workshop, fitness or literary, or free text with q=.
• Time window: when=week, when=weekend, or a specific date.

You won’t get RSVP counts or group membership. We describe events, not who’s going.

Using both

If you run Meetup groups, keep using Meetup’s API for your own chapters. FindLocal can fill in everything else happening in the same city that week, so your app isn’t limited to one platform’s organizers.

When to pick Meetup

Pick Meetup’s API if you already pay for Meetup Pro and your product is about managing groups, members and RSVPs. If you want a public feed of what’s on in a city, you’ll get more events with less hassle somewhere else.

Try the same query on FindLocal

Community events and workshops in Chicago this week, which is the sort of feed people usually build on Meetup.

curl -H "Authorization: Bearer $FINDLOCAL_KEY" \
  "https://findlocal.community/api/events?city=chicago&cat=community,workshop&when=week&sort=date"

No key yet? Run it in Explore to see the results and map, or use the keyless playground. Full reference: API docs · docs as Markdown for your LLM.

FAQ