- Personal Anthropic keys - saved under the caller’s account and used by
default. Scoped per
(user, organization)so you can separate keys across contexts. - Organization Anthropic keys - set by org owners/admins and shared with
every member. Two policies control how they interact with personal keys:
individual: every member uses their own personal key. The org key, if set, is ignored.enforced: the org key is used first; per-member personal keys are only used as fallbacks if no org key is configured.
Values are never returned by any endpoint on this page. Responses include
only a masked preview (
sk-ant-***...XXXX) and a “connected” / “has_key”
flag. Treat keys as opaque, write-only values once stored.Personal Key
GET /api/user/anthropic-key
Required scope:
integrations:readHeaders
Response
PUT /api/user/anthropic-key
Required scope:
integrations:writeHeaders
Request Body
Response
Same shape asGET /api/user/anthropic-key, with connected: true.
DELETE /api/user/anthropic-key
Required scope:
integrations:writeHeaders
Response
Same shape asGET /api/user/anthropic-key, always with
connected: false.
Organization Key
Organization context is required for all org-key endpoints. Set
X-Organization-Id to match the path org_id, or use an org-scoped API
key whose org ID matches.GET /api/organizations//anthropic-key
Required scope:
integrations:readPath Parameters
Response
PUT /api/organizations//anthropic-key
Required scope:
integrations:writeenforced, you must include an api_key.
Path Parameters
Request Body
Anthropic API key. Must start with
sk-ant- or sk- when provided.
Required when switching to policy="enforced" for the first time.Response
Same shape as the GET response, reflecting the updated key and policy.DELETE /api/organizations//anthropic-key
Required scope:
integrations:write"individual". Members fall back to their personal keys (or are prompted)
the next time they create a session.
Path Parameters
Response
Same shape as the GET response, withhas_key: false, key_preview: null,
and policy: "individual".