Cocktail Manager API
Stable, versioned (/api/v1) REST API of the Cocktail Manager. Authenticate with a workspace API key (Bearer JWT). This is the recommended contract for all integrations.
Authentication
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- API Key: SessionCookieAuth
Workspace API key (JWT), scoped to a single workspace. Create one under Workspace → Settings → API Keys and send it as Authorization: Bearer <token>. Each key carries a set of permissions; the required permission is documented per operation (see the Permission schema for the full list).
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Instance master API key — the INSTANCE_MASTER_API_KEY server env value, sent as Authorization: Bearer <token>. It is instance-wide (NOT scoped to a workspace) and bypasses the per-operation permission checks, so it authorizes every workspace operation. Intended for self-hosting / instance administration, not for third-party integrations. Call GET /me to introspect a token (its isMaster flag is true for this key).
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Logged-in user session (browser cookie). Used by the few workspace-member operations that act on the caller's own identity (e.g. leaving a workspace, creating/revoking API keys) and therefore do NOT accept API keys — neither a workspace key nor the instance master key.
Security Scheme Type: | apiKey |
|---|---|
Cookie parameter name: | better-auth.session_token |