A valid request URL is required to generate request examples{
"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": {
"provider": "openai",
"model_requested": "<string>",
"request_type": "<string>"
}
}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.
A valid request URL is required to generate request examples{
"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": {
"provider": "openai",
"model_requested": "<string>",
"request_type": "<string>"
}
}Authorizations
Management API authentication for /api/* endpoints. Use the Authorization header
with Bearer <token>, where <token> is one of:
- a Bifrost management API key,
- a dashboard session token issued by
POST /api/session/login, - base64 of
<admin-username>:<admin-password>(legacy equivalent ofBasicAuth).
Virtual keys (sk-bf-*) and the x-api-key header are not accepted on management APIs -
the sole exception is GET /api/governance/virtual-keys/quota, which is virtual-key-only.
Response
Vault cache flushed successfully
"vault cache flushed"
Was this page helpful?