Skip to main content

Bitwarden connector setup

Polls organization event logs from the Bitwarden Public API (GET /public/events).

What you need first​

RequirementDetails
Bitwarden planOrganization with Public API access (Teams or Enterprise)
RoleOrganization owner (to view or rotate the organization API key)
RegionKnow whether your org uses the global (api.bitwarden.com) or EU (api.bitwarden.eu) stack

Use an organization API key (client_id starts with organization.). Personal API keys (user.…) cannot access the Public API.

1. Get the organization API key​

  1. Sign in to the Bitwarden web vault as an organization owner.
  2. Open your organization → Settings → Organization info.
  3. Scroll to API key and click View API Key.
  4. Copy the client_id and client_secret. Store them securely.

2. Perpetual credential​

  1. Log in to Perpetual. Open Settings from the user/org control at the bottom left of the sidebar (click your name → Settings), then go to Credentials → New Credential.
  2. Choose OAuth 2.0 Client Credentials.
  3. Fill in:
FieldValue
NameUnique identifier using letters, digits, and underscores only (e.g. bitwarden).
Allowed URL patterns*.bitwarden.com, *.bitwarden.eu
Token URLhttps://identity.bitwarden.com/connect/token (global) or https://identity.bitwarden.eu/connect/token (EU)
Client IDOrganization client_id from step 1
Client SecretOrganization client_secret from step 1
Scopesapi.organization
  1. Save the credential. Perpetual refreshes access tokens automatically (tokens expire in about 60 minutes).

3. Create the Bitwarden connector​

  1. Go to Datasets → Connectors → Create Connector.
  2. Select Bitwarden.
  3. Connector name: unique identifier (letters, numbers, underscores).
  4. Configure:
    • Bitwarden API access: select the credential from step 2.
    • Poll interval (minutes): default 5.
    • Region: global or eu — must match your Bitwarden stack.
  5. Optionally check Deploy, then save.

First run backfills roughly the last 24 hours of organization events. Subsequent polls advance in time windows with a short end buffer for API consistency.

Operational notes​

  • Event delay: Bitwarden batches client-side events; the connector ends each window slightly before run time to avoid gaps.
  • Key rotation: Rotate the API key in Bitwarden, update the Perpetual credential, then revoke the old secret.

Reference​