Coolify Octri Demo
POST/security/integration-tokens

Create a Secret Manager integration token

Creates and validates an integration token for Doppler, Infisical, or Vault. Supply provider, name, and token; metadata is optional. A 201 response confirms the integration token was created.

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

4 body fields

Secret Manager integration token details. provider, name, and token are required.

metadataobjectoptional
Additional metadata for the integration token.
namestringrequired
The name to assign to the integration token.
providerstringrequired
The Secret Manager provider: `doppler`, `infisical`, or `vault`.
Allowed:dopplerinfisicalvault
tokenstringrequired
The integration token to validate and store.

4 status codes
201Returns confirmation that the integration token was created.
400Returned when the supplied integration token is invalid.
messagestringoptional
401Returned when the request is unauthenticated.
messagestringoptional
422Returned when request validation fails.
errorsobjectoptional
messagestringoptional

Error handling

A 400 is returned when the supplied token is invalid. A 401 is returned when the request is unauthenticated. A 422 is returned when validation fails; provider, name, and token are required, and provider must be doppler, infisical, or vault.