Britive platform release 2026.09.02 is now live in production.

Manually Trigger Secret Verification

Prev Next
Get
/api/v1/secretmanager/vault/{vaultId}/secrets/{secretId}/verify

Manually triggers verification for a single secret (one secret per call, no bulk trigger). Request is dispatched to the broker/agent asynchronously; this response does not wait for the result — check the verification history or the secret's lastVerificationStatus for the outcome.

Security
HTTP
Type bearer
Path parameters
vaultId
stringRequired

Vault identifier

Examplea6ed82f6-32b5-46d8-a3a3-c36cc574abd9
secretId
stringRequired

Secret identifier

Examplesecret-123
Responses
202

Verification request accepted and dispatched

400

Bad request. Returned for the following violations:

  • SM-0022 — vault is an internal vault (verification isn't supported for internal vaults)
  • SM-0097 — the secret is currently locked/being updated
  • SM-0189 — verification isn't enabled for this secret
  • SM-0190 — a verification is already in progress for this secret
404

Not found. Returned for the following:

  • SM-0084 — secret not found or has been deleted