canonical: https://jentic.com/apis/commmune.com/commune # Commmune Commune API Jentic publishes the only available OpenAPI specification for Commune API, keeping it validated and agent-ready. Commune is a Japanese community management and engagement platform; the v2 API exposes a small core surface for listing communities, fetching community detail, listing members, reading and creating posts, and listing events. The post creation endpoint is the only write operation in the spec - everything else is read access. Use it to mirror community activity, drive notification systems, or let an agent post announcements on your behalf. ## For AI agents List communities, members, and events on Commune, and create new posts in a community via one bearer token. ## Scope Does not handle direct messaging, payments, or course content - use for community post, member, and event read access plus post creation only. ## Capabilities - List every community accessible to the authenticated token via GET /communities - Fetch a single community record by id via GET `/communities/{id}` - List members across a community via GET /members - Read posts published in a community via GET /posts - Create a new post in a community via POST /posts - List scheduled and past events via GET /events ## Use cases ### Cross-Post Announcements from a CMS When an editorial CMS publishes an article, mirror the headline and link into Commune by calling POST /posts. The community manager sets the destination community id once, and every published article fans out automatically. Useful for keeping members informed without manual reposting. Example prompt: POST a new post to /posts with title 'New Article Live' and body containing the article URL ### Member Directory Sync Pull GET /members on a schedule and reconcile against an internal source-of-truth (HRIS or CRM) to detect new joiners and leavers. Combined with GET /communities, this gives a current map of who belongs to which community for downstream segmentation. Example prompt: List members via /members and join with an internal CRM email list to find members who have not been contacted this month ### Event Calendar Aggregation Surface Commune events alongside other calendar sources (Google Calendar, Eventbrite) in an internal portal. GET /events returns the event list which can be normalised into a unified schedule view, so members see one calendar instead of several tabs. Example prompt: Fetch all events from /events and normalise them into a calendar JSON with title, start_at, and url fields ### AI Community Manager via Jentic An AI agent connected to Jentic can draft an announcement, post it to Commune, and confirm members can see it - all without raw key exposure. Jentic stores the bearer token in your Jentic One instance and returns only execution results to the agent context. Example prompt: Use Jentic to search 'create a post in commune', load POST /posts, and execute with a draft announcement ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/communities` | List communities | | GET | `/communities/{id}` | Get a single community | | GET | `/members` | List members | | GET | `/posts` | List posts | | POST | `/posts` | Create a post | | GET | `/posts/{id}` | Get a single post | | GET | `/events` | List events | ## Key resources - **Communities** — List communities and fetch single community detail - **Members** — List the members of a community - **Posts** — List, fetch, and create posts in a community - **Events** — List scheduled and past community events ## Why Jentic - **Setup:** Wiring Commune by hand means learning its bearer auth, mapping its community, member, and post resources, and handling pagination yourself. Through Jentic you install once, import Commune from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Commune puts the community and post ids in the URL path (`/communities/{id}`, `/posts/{id}`), so a rule can pin your agent to reading a specific community or post. You choose the operations it may call, so you can allow reads and post creation while leaving anything else out unless you add it. - **Credential handling:** Your Commune bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list community members' or 'create a community post', and Jentic returns the matching Commune operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Circle Communities API** — Circle is a Western community platform with broader API coverage including write operations across most resources. - **Discourse API** — Discourse is an open-source forum platform with deep CRUD coverage across topics, posts, and users. - **Mighty Networks API** — Mighty Networks is a community-and-courses platform with similar member, post, and event primitives. ## FAQ ### Why is there no official OpenAPI spec for Commune API? Commune does not publish an OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call Commune 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 Commune API use? Commune uses a bearer token in the Authorization header. Through Jentic, the token is stored encrypted in your Jentic One instance and never enters the agent's context - the agent only receives the response of the operation it called. ### Can I create posts in a Commune community? Yes. POST /posts creates a new post in a target community; the request body includes the community reference, post title, and body content. This is the only write endpoint in the v2 spec. ### What are the rate limits for the Commune API? Commune does not document a public rate limit. In practice, modest paginated reads work reliably; if 429 responses appear, back off and retry. Avoid posting in tight loops to prevent member-facing spam. ### How do I create a Commune post through Jentic? Search Jentic for 'create a post in commune', load the schema for POST /posts, and execute with the title and body. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...). ### Does the Commune API support listing events? Yes. GET /events returns events scheduled in the community, including upcoming and past entries. Combine with /communities to scope events to a specific community. ### Can I limit what my agent is allowed to do with the Commune API? Yes. Jentic One is self-hosted by you, so your own rules decide which Commune operations the agent may call and which credentials it may use. You can allow only reads such as GET /communities, GET /members, GET /posts, and GET /events, and grant POST /posts for creating announcements while leaving every other operation out. Because Commune puts community and post ids in the URL path (`/communities/{id}`, `/posts/{id}`), a rule can also pin the agent to a single community or post.