API reference
The Confabulous backend exposes a JSON HTTP API used by the web frontend, the confab CLI, and external integrations. All endpoints are prefixed with /api/v1 unless otherwise noted.
Authentication
Section titled “Authentication”- API key (Bearer token, used by the CLI) —
Authorization: Bearer cfb_.... - Session cookie (used by the web UI) —
confab_sessioncookie, set after OAuth or password login. CSRF is enforced via Fetch metadata validation; no token required. - Session cookie or API key — a few endpoints shared by the CLI and web UI accept either.
- Optional auth — canonical session reads accept an API key, a session cookie, or no credentials at all. Anonymous callers can only reach public shares.
Full authentication reference →
Endpoint groups
Section titled “Endpoint groups”CLI endpoints (API key auth)
Section titled “CLI endpoints (API key auth)”The bulk of the upload pipeline. Used by the confab CLI to register sessions and stream transcript chunks in real time as sessions progress.
GET /api/v1/auth/validate— validate an API key.POST /api/v1/sync/init— start or resume a sync session.POST /api/v1/sync/chunk— upload a transcript chunk.POST /api/v1/sync/event— record a session lifecycle event.PATCH /api/v1/sessions/{external_id}/summary— update a session’s summary.
External API endpoints (API key auth)
Section titled “External API endpoints (API key auth)”For programmatic integrations: a condensed, AI-readable transcript, the list of a session’s transcript files, and raw file downloads.
Web endpoints (session auth)
Section titled “Web endpoints (session auth)”Everything the dashboard talks to: current user, API keys, session list, title edits and deletion, shares, smart recap regeneration, trends, and organization analytics.
Canonical session access (optional auth)
Section titled “Canonical session access (optional auth)”One URL per session for owners, share recipients, and public-share viewers: session detail, sync file reads, session analytics, and GitHub links.
Full canonical access reference →
OAuth endpoints
Section titled “OAuth endpoints”Login and callback URLs for GitHub, Google, and generic OIDC providers, plus password login, CLI authorization, and the device code flow for headless machines.
Admin endpoints (super-admin only)
Section titled “Admin endpoints (super-admin only)”User management (create, activate, deactivate, grant or revoke admin, delete), system shares, smart recap prompt settings, card invalidation, and the unpriced-models report.
Public endpoints (no auth)
Section titled “Public endpoints (no auth)”Auth configuration, backend version, model pricing, and backend capabilities.
Utility endpoints outside /api/v1 cover health checks, the account deletion help page, and the CLI install script redirect.
Conventions
Section titled “Conventions”- Error responses — uniform error envelope.
- Rate limits — per-user and per-endpoint.
- Request body size limits.
- Email domain restrictions —
ALLOWED_EMAIL_DOMAINSenforcement. - Read-only identity (Demo Mode) — how mutating requests from the demo user are blocked.