Authentication
The Brie API uses Bearer token authentication. Include your API key in the Authorization header of every request:
curl https://api.briehq.com/v1/me \
-H "Authorization: Bearer brie_pat_your_key_here"
API key types
| Type | Prefix | Scope | Use case |
|---|---|---|---|
| Personal Access Token (PAT) | brie_pat_ | All workspaces you belong to | Personal scripts, CLI tools, AI agents |
| Workspace Service Token (WST) | brie_wst_ | Single workspace only | CI/CD pipelines, team automations |
PAT (Personal Access Token)
Acts as you. Has access to all workspaces in your organization where you're a member. Best for personal use and development.
WST (Workspace Service Token)
Scoped to a single workspace. Cannot access other workspaces or create new ones. Best for automated systems that should only touch one workspace.
Creating an API key
- Go to app.briehq.com → Settings → Integrations → API Keys
- Click Create API Key
- Choose PAT or WST, select scopes, and set an optional expiry
- Copy the token — it's shown only once
Scopes
Each API key has a set of scopes that control what it can access:
| Scope | Allows |
|---|---|
slices:read | List and view bug reports |
slices:write | Create and update bug reports |
slices:delete | Delete bug reports |
workspaces:read | List and view workspaces |
workspaces:write | Create and update workspaces |
spaces:read | List spaces within workspaces |
spaces:write | Create spaces |
user:read | View your own profile |
keys:manage | Create, list, revoke, and rotate API keys |
webhooks:manage | Create, list, delete, and manage webhooks |
Tip: Follow the principle of least privilege. Only grant the scopes your integration actually needs.