Bitwarden

Manage organization members, groups, collection permissions, policies and event logs through Bitwarden's organization Public API. All 19 existing tools remain available, with exact collection and policy reads added for safe discovery and readback.

Connect with an organization API key from the admin console and choose the matching US or EU identity region. Personal user.* keys, Secrets Manager machine tokens, SCIM keys and local vault sessions are separate products and are not accepted. This integration does not read vault passwords, export vaults, run the CLI, manage developer secrets or expose a person identity. The organization ID is bound to authentication. Organizations require the provider's applicable Teams/Enterprise features.

Organization access tokens expire after the provider-specified lifetime (normally 60 minutes). Renewal repeats the native client-credentials exchange under the original organization, client credentials and region. Existing unmarked connections can use their still-valid saved token but must reconnect once before automatic renewal; no identity is invented for them. Region configuration is owned by authentication.

Available tools cover members (list, get, invite, update, remove, reinvite, revoke/restore), groups (list, get, create, update, delete), collections (list, get, update, delete), policies (list, get, update), event queries and directory import. Collection creation, user account confirmation and vault/secret CRUD are outside this API's supported surface. Policy routes use numeric policy types; an existing policy UUID passed to update_policy is resolved through list_policies first.

The current published API no longer accepts accessAll or legacy Manager role 3. Legacy Boolean inputs remain accepted as false for compatibility; true is refused before effects. Legacy output flags are null when absent from the native response. Use explicit collection assignments. Updates preserve omitted external IDs, assignments, hide-password/manage flags and existing Custom-role permissions before the provider's replacement PUT. Explicit assignment arrays replace that entire set; explicit permission objects replace Custom permissions. Updates refuse before replacement when the existing field needed for preservation is not exposed. Read results include optional association/configuration availability flags: a false flag means the current value is unknown, even when the legacy array is empty or configuration is null. Avoid concurrent changes: there is no documented atomic compare-and-swap. Native mutation receipts are checked against the requested state, and exact group readback precedes a dependent membership change. Group membership is a second write, so an acknowledged group followed by association failure is reported as a partial effect requiring exact-ID reconciliation.

Event queries preserve native date defaults, refuse conflicting selectors and repeated cursors, and stop with an error rather than truncate beyond 100 pages or 10,000 records. Responses are bounded to 4 MiB. Import counts describe submitted entries; native acknowledgment does not independently prove every downstream invitation, removal or directory effect. Invitation email, access changes, policy enforcement and audit retention require explicit authorization in a controlled organization.

No live provider operation was performed during this refresh. The private suite is active with safe read scenarios and gated exact-owned group/invitation lifecycles; collection deletion, policy enforcement, bulk import and accepted-user access changes require independently controlled prerequisites.

Official sources: Public API guide, published API schema, API product boundaries.