Create Vault Connection
Create a new external vault connection.
Required Role: ADMIN or OWNER
Tier Limits:
- Free Tier: Maximum 1 vault connection
- Pro Tier: Maximum 10 vault connections
Connects your team to an external vault provider (1Password, Doppler, or Infisical). Credentials are stored encrypted and never returned in API responses.
1Password:
- Requires a service account token (starts with “ops_”)
- No additional configuration needed
Doppler:
- Requires a service token (starts with “dp.st.”)
- Requires project and config
Infisical (Universal Auth / Machine Identity):
- Create a Machine Identity in Project Settings -> Access Control -> Machine Identities
- client_id: UUID from Machine Identity
- client_secret: Secret string from Machine Identity
- project_id: Project ID (UUID) from Project Settings -> General
- environment: Environment slug (e.g., “dev”, “staging”, “prod”, “sandbox”)
- Optional: secret_path (defaults to ”/”)
Example for 1Password:
Example for Doppler:
Example for Infisical:
Authorizations
Body
Schema for creating a new vault connection.
Credentials are stored encrypted in AWS SSM Parameter Store - they are NEVER returned in API responses.
Provider-specific configuration:
1Password:
- access_token: Service account token (starts with "ops_")
- No additional configuration needed
Doppler:
- access_token: Service token (starts with "dp.st.")
- project: Doppler project slug (required)
- config: Doppler config name (required)
Infisical (Universal Auth / Machine Identity):
- client_id: UUID from Machine Identity
- client_secret: Secret string from Machine Identity
- project_id: Infisical project ID - UUID (required)
- environment: Environment slug e.g., "dev", "staging", "prod", "sandbox" (required)
- secret_path: Path to secrets folder, e.g., "/" or "/aws" (optional, defaults to "/")
Response
Successful Response
Schema for vault connection response (without sensitive data).