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

Query Parameters

dimensions
string

Comma-separated dimensions to return. One or more of models, aliases, selected_keys, virtual_keys, routing_rules, routing_engines, stop_reasons, tool_call_names, apps, user_agents, teams, customers, users, business_units, projects, metadata_keys. Unrecognised values are ignored, and asking for none returns every dimension.

q
string

Free-text search within the requested dimensions. Passing it bypasses the response cache.

Response

Successful response

Available filter data response

models
string[]
selected_keys
object[]
virtual_keys
object[]
routing_rules
object[]

Available routing rules for filtering

CEL-based routing rule for intelligent request routing

routing_engines
string[]

Available routing engine types (routing-rule, governance, loadbalancing)

tool_call_names
string[]

Function names that logged responses have called, for the tool calls filter. Read from the persisted tool_call_names metadata, so it stays available when message content is not logged or is offloaded in hybrid storage mode.

projects
object[]

Governance projects that appear in the logs, for the projects dimension. Only projects whose rows carry a name are listed.