Skip to main content
PUT
Error
Required Permissions How permissions work

Authorizations

Authorization
string
header
required

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 of BasicAuth).

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.

Authentication alone is not sufficient in Bifrost Enterprise: each operation page shows a Required Permissions table (Resource:Operation, for example Dashboard:View) above its Authorizations section, and the caller's RBAC role or management API key scopes must include what it lists, otherwise the request is rejected with 403 Forbidden.

A local admin — authenticated with the admin password, or any caller on a deployment with dashboard auth disabled — bypasses these checks and can call every management endpoint.

OSS setup lock. On Bifrost OSS, while dashboard auth is not active (no admin account, or auth disabled), every management endpoint except the public ones (/health, /api/version, /api/session/is-auth-enabled, /api/session/login, ...) requires the operator's setup token in the X-Bifrost-Setup-Token header, in place of Authorization. The token is set with setup_token in config.json or the BIFROST_SETUP_TOKEN environment variable. A missing header returns 401, a wrong token 403. The header stops working once dashboard auth is enabled. The dashboard instead trades the token once for an HttpOnly bifrost_setup_session cookie via POST /api/session/setup. See Required permissions for how permissions are derived and which endpoints are exempt.

Path Parameters

vk_id
string
required

Virtual key ID

Body

application/json

Update virtual key request

name
string
description
string
metadata
object | null

Replaces the key's metadata as a whole. Omit (or send null) to leave it unchanged; send {} to clear it. Keys are 1-256 characters of letters, digits, '.', '' and '-' and may not be system-reserved (isAsyncRequest, bifrost_alb*); values are strings of at most 512 characters; at most 50 entries.

provider_configs
object[]
mcp_configs
object[]
team_id
string
customer_id
string
budgets
object[]

Budget quotas assigned directly to this virtual key. Replaces all direct virtual-key budgets when provided; the removed singular budget and budget_id fields are not request fields.

rate_limit
object

Update rate limit request

is_active
boolean
calendar_aligned
boolean
allow_all_providers
boolean

When true, this virtual key may use every configured provider. provider_configs remain optional per-provider overrides. Omit to leave the current setting unchanged.

disable_content_logging
boolean | null

Tri-state. Omit to leave the current decision unchanged, null to clear it back to inheriting client.disable_content_logging, true to keep content out of the log store and out of OpenTelemetry export (other observability connectors follow their own disable_content_logging until they adopt the trace mark), false to force content into the log store. When content logging ends up disabled for a request, the log row is still written without content; with client.retain_content_in_object_storage on and an object-storage-backed log store, the full payload is then kept there as hidden content that the API and UI never serve. When client.allow_per_request_content_storage_override is on, the x-bf-disable-content-logging request header still takes precedence over this value for the log store.

reset_budget_usage
boolean

When true, zeroes current usage on the budgets reconciled by this update. The reset window is left alone: last_reset only ever advances, and never as a side effect of a configuration write, so the current window keeps its existing start and end.

expires_at
string

RFC3339 timestamp to set a new expiry (must be in the future), empty string to clear an existing expiry, omitted to leave it unchanged.

delete_after_expire
boolean | null

Override client.delete_expired_virtual_keys for this key. true or false set it, null resets the key to inherit the client setting, omitted leaves it unchanged. A value requires an expiry; clearing expires_at resets it to inherit.

Response

Virtual key updated successfully

Virtual key operation response

message
string
required
virtual_key
object
required

Virtual key configuration