Skip to main content
POST
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.

Body

application/json

Create virtual key request

name
string
required
description
string
metadata
object

Custom key/value metadata for cost attribution (for example cost_center, project, owner, environment). 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[]

Provider configurations. When allow_all_providers is omitted or false, an empty list allows no providers (deny-by-default); when true, providers without a config are allowed with all models and keys.

mcp_configs
object[]

MCP configurations (empty means no MCP tools allowed, deny-by-default)

team_id
string
customer_id
string
budgets
object[]

Budget quotas assigned directly to this virtual key. Use this array instead of the removed singular budget or budget_id fields.

rate_limit
object

Create rate limit request

is_active
boolean
calendar_aligned
boolean
default:false
allow_all_providers
boolean
default:false

When true, this virtual key may use every configured provider. provider_configs remain optional per-provider overrides for budgets, rate limits, model allow/blacklists, and key selection.

disable_content_logging
boolean | null

The key's own content-logging decision. Omit or set null to inherit client.disable_content_logging. true keeps content out of the log store and out of OpenTelemetry export for this key's traffic (other observability connectors follow their own disable_content_logging until they adopt the trace mark); false forces content into the log store even when the client setting is true. 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.

expires_at
string<date-time>

Optional expiry timestamp. Must be in the future. Omit for a key that never expires.

delete_after_expire
boolean

Override client.delete_expired_virtual_keys for this key. Omit to inherit the client setting. Rejected with 400 when expires_at is not set.

Response

Virtual key created successfully

Virtual key operation response

message
string
required
virtual_key
object
required

Virtual key configuration