Build on the Communal Platform API
A REST API with OpenAPI 3.1 and a per-organization MCP server, so your systems and your AI assistants can work with programs, memberships, attendance, and activities. Both are in beta, and endpoints and capabilities are actively expanding.
Connect your AI assistant
Give Claude, ChatGPT, or Gemini a seat at the front desk. Every organization gets its own private connection, so your assistant answers from your live data: rosters, registrations, bookings, renewals.
Setup takes about two minutes in your assistant's settings, and the docs walk you through every app. It only sees what you can see, and it asks before it acts.
How many spots are left in Spring Soccer U10?
45 of 45 filled, 6 on the waitlist. Want me to email the first family when a spot opens?
Also works in Claude Code, Cursor, and VS Code.
API capabilities
Programmatic access to the core data behind your organization. The API is in beta. These are the endpoints available today, with more on the way.
Programs & Registration
List and retrieve programs and registration opportunities. Query program signups to connect registration flows to your own portals or reporting tools.
Membership Types & Cards
Retrieve membership types, archive or unarchive them, and trigger digital membership card delivery to members.
Attendance
List and retrieve attendance sheets and individual attendance records. Power check-in workflows and track who showed up.
Users
Update user records in your organization. Keep member profiles in sync when changes happen in external systems.
Card Delivery Activity
Query digital membership card delivery activities with filters like date range and status to track card distribution.
Why integrate with Communal
Built for developers who need reliable, standards-based access to nonprofit and community organization data.
OpenAPI 3.1 specification
Use the spec with codegen tools, API clients, or documentation viewers. Generate SDKs in any language from the contract.
Consistent JSON responses
Every endpoint returns structured JSON with data, meta, and links. Write integration code once and reuse patterns across resources.
Standard Bearer authentication
HTTP Bearer tokens in the Authorization header. No proprietary auth flows to learn. Works with any HTTP client or framework.
Full control for custom integrations
When Zapier isn't enough, the API gives you direct access for reporting pipelines, custom portals, mobile apps, and AI workflows.
What you can build
Here's what teams are building with the beta API today.
Sync member and program data with your CRM
Pull program signups, membership types, and attendance data into Salesforce, HubSpot, or your own database. Push user updates back from external systems.
Learn more →Build custom member portals & mobile apps
Use program, membership, and attendance endpoints as your backend for branded member experiences like self-service portals, native apps, or kiosk check-in.
Learn more →Reporting & analytics dashboards
Pull attendance records, program signups, and card delivery activity into BI tools or custom dashboards for board reports and grant applications.
Learn more →Connect to AI assistants & agents
Expose Communal's read endpoints as tools for LLMs to summarize attendance sheets, query program signups, or check membership types.
Learn more →The docs have the rest
Authentication, every endpoint, worked examples, and the MCP setup guide, all in one place. Start with the getting-started guide and ship something for your community this afternoon.
Frequently asked questions
It is the REST API for the Communal platform, documented with OpenAPI 3.1. The API is currently in beta, with endpoints for programs, program sign-ups, membership types, membership cards, attendance, card delivery activities, and user updates. All endpoints use standard request patterns and Bearer token authentication.
The beta API includes endpoints for listing and retrieving programs, registration opportunities, and program signups; listing and retrieving attendance sheets and records; managing membership types (including archiving); sending digital membership cards; querying card delivery activities; and updating user records. More endpoints are being added as the API expands.
Use HTTP Bearer authentication: send your access token in the Authorization header. Obtain credentials and learn which environments apply (production uses https://api.getcommunal.com/api) from Communal when API access is enabled for your organization.
The full API documentation is available at docs.getcommunal.com. It includes the complete OpenAPI specification, endpoint details, request and response examples, and authentication guides. Your team can also use the spec with codegen tools and API clients.
Yes, in a controlled way. Typical patterns wrap API calls in server-side functions or agent tools so secrets stay off devices, and humans review actions that affect membership or payments. Design for clear error handling and avoid exposing tokens to end users or public repositories.
API access is available to customers who need programmatic integration. Since the API is in beta, we work closely with early adopters to prioritize new endpoints and ensure the integration meets your needs. Contact Communal through a demo or your account contact to get started.
The API uses JSON for all requests and responses. Responses follow a consistent structure with data, meta, and links fields where applicable, so your integration code can parse results predictably across all endpoints.
Plan your API integration
Book a demo to discuss API access, scopes, and the right integration pattern for your organization.
Book a Demo