Introduction

The Cobuntu public API puts a community's members, sign-in, events, tickets, marketplace and content inside your own site or app. Call it over REST, with the typed JavaScript client, or render it with headless React components.

curl "https://api.cobuntu.com/api/v1/communities/your-community/events?upcoming=true" \
  -H "X-API-Key: $COBUNTU_KEY"

Base URLhttps://api.cobuntu.com (opens in a new tab), routes under /api/v1

AuthA community key in X-API-Key, plus a member session for member routes

FormatsJSON, amounts in cents, errors as { error, code }

Start here

Quickstart Embed in your own code API keys and scopes REST API reference JavaScript client React components

Common tasks

I want to…	Guide
Sign members in on my site	Sign in and recover accounts
Show events and take registrations	Show events on your site
Sell products and tickets	Run a marketplace · Add a cart and checkout
Let people apply to join	Build a public apply form
Give members an account area	Build the account area
Pull revenue into my reporting	Report on finances
Sign members into my own app	App handoff

What the API covers

Area	What you can do
Auth	Sign members in and up, email sign-in links, recover passwords, Continue with Google
Members	The member's own account, the directory, membership standing, tiers, applications and rules
Events	List and filter events, RSVP, invitations, attendance, and sync events from other platforms
Checkout	Ticket and basket checkout, quotes, buyer refunds, guest order links, donations
Commerce	Products, courses and categories, a cross-origin cart, host refunds and subscriptions
Content	Branding, articles, the map, co-creation, city autocomplete, feed posts, notifications, broadcasts
Finance	The community's ledger, settlements and totals for your own reporting
Apps	Sign members into an installed app, onboarding, per-member app data
User keys	Read one person's own products, courses and events with a user key

Every documented endpoint is live, and its method and scope are taken from the route definition rather than from memory. If a route is documented, you can build against it today. It is the verified, supported surface, and it grows as endpoints are documented.

Recommended shape

Call Cobuntu from your server, not from your app. Have your mobile or web app call your own backend, and your backend call Cobuntu. The secret key stays server side, and your app talks only to routes you control. The client is built for exactly this. Every community still manages itself in its own admin, whatever you build on top.

Where the API stops

Cobuntu supplies the data. Composing it into your own surface is yours.

If your app shows, say, one ranked "library" mixing articles, events, products and courses, that list is your product: call the individual endpoints, merge the results and rank them by your own rules. The API exposes primitives rather than aggregates shaped around one screen, so every integrator can compose them differently.

Almost everything is under /api/v1. One documented endpoint is not, and it is called out where it appears (Versioning).

Quickstart