Developersv1.0

API docs.Build on Meetumo.

Events, communities, attendees, check-in and webhooks over one REST API.

Meetumo External API

Connect your application to Meetumo to access event data, attendee information, and perform check-ins programmatically.

Base URL

https://meetumo.ai/api/v1

Plan Requirement

The external API, OAuth token flow, and webhook management require an active Meetumo Pro subscription with API & Webhooks access. API calls for organizers without that feature return 403 PRO_REQUIRED.

Getting Started

  1. Confirm Pro access - The connecting organizer must be on Meetumo Pro with API & Webhooks enabled
  2. Register your application - Contact Meetumo admin to receive your client_id and client_secret
  3. Implement OAuth 2.0 - Use the Authorization Code flow to get access tokens
  4. Make API calls - Use your access token to call the API
  5. Set up webhooks - Receive real-time updates when events occur

Available Scopes

ScopeDescription
events:readRead events you organize.
communities:readRead your communities, branches, and members.
series:readRead community event series.
attendees:readRead attendee and ticket-holder details for your events.
stats:readRead aggregate event stats (sales, check-ins, feedback).
sessions:readRead event sessions and tracks.
session_attendance:readRead per-session attendance.
feedback:readRead event and session feedback responses.
resources:readRead event resources and materials.
speakers:readRead event speakers.
sponsors:readRead event sponsors.
exhibitors:readRead event exhibitors.
cfs:readRead Call-for-Speakers and its configuration.
cfs_submissions:readRead Call-for-Speakers submissions.
orders:readRead orders for your events.
tickets:readRead issued tickets for your events.
questions:readRead custom questions + responses.
checkin:writeCheck attendees in via QR code.
session_attendance:writeRecord per-session attendance.
webhooks:manageCreate, update, and delete your webhook endpoints.
agent:readLet external AI agents read your bounded Agent Mode projections (sales, demand, attendance, feedback, engagement, community health) over MCP. This permission grants only these aggregate reads; broader reads, drafts, and governed actions require separate consent.

Rate Limiting

API requests are limited to 100 requests per minute per client and organizer. Successful responses include the remaining request count. Rate limit errors also include reset metadata:

  • X-RateLimit-Limit - Maximum requests per window, included on 429 responses
  • X-RateLimit-Remaining - Remaining requests
  • X-RateLimit-Reset - Unix timestamp when limit resets, included on 429 responses