Flush vault secret cache

Clears the in-memory vault secret cache so the next resolution of every vault.<path> reference re-fetches from the configured backend (AWS Secrets Manager, GCP Secret Manager, or HashiCorp Vault).

Use this after rotating a secret when you cannot wait for the hourly background refresh. In a clustered deployment the flush is broadcast to all peer nodes automatically — you only need to call this on one node.

Returns 400 if vault integration is not enabled.

POST /api/vault/flush-cache

Error

A valid request URL is required to generate request examples

200

{
  "message": "vault cache flushed"
}

{
  "error": "vault is not enabled"
}

{
  "event_id": "<string>",
  "type": "<string>",
  "is_bifrost_error": true,
  "status_code": 123,
  "error": {
    "type": "<string>",
    "code": "<string>",
    "message": "<string>",
    "param": "<string>",
    "event_id": "<string>"
  },
  "extra_fields": {
    "model_requested": "<string>",
    "request_type": "<string>"
  }
}

Authorizations

Authorization · string · header · required

Management API authentication for /api/* endpoints. Use the Authorization header with Bearer <API key>. Virtual keys, dashboard/user/session tokens, and x-api-key headers are not supported on management APIs.

Response

200

application/json

Vault cache flushed successfully

message · string

Example:

"vault cache flushed"