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

tool_names
string

Comma-separated list of tool names to filter by

server_labels
string

Comma-separated list of server labels to filter by

status
string

Comma-separated list of statuses to filter by. Values: processing, success, error, cancelled, input_required (for example success,error).

virtual_key_ids
string

Comma-separated list of virtual key IDs to filter by

llm_request_ids
string

Comma-separated list of LLM request IDs to filter by

user_ids
string

Comma-separated list of user IDs to filter by

team_ids
string

Comma-separated list of team IDs to filter by

customer_ids
string

Comma-separated list of customer IDs to filter by

business_unit_ids
string

Comma-separated list of business unit IDs to filter by

project_ids
string

Comma-separated list of project IDs to filter by

device_ids
string

Comma-separated list of device IDs to filter by

agent_names
string

Comma-separated list of registered agent names whose context IDs correlate the matching logs

session_id
string

Exact Bifrost session ID used for request correlation

agent_correlation_id
string

Exact caller-supplied agent correlation ID (the x-bf-agent-correlation-id request header)

user_agents
string

Raw User-Agent strings to filter by. Send a JSON array so values containing commas survive intact; a plain comma-separated list is also accepted.

apps
string

Detected client apps to filter by. Send a JSON array of strings or a comma-separated list.

start_time
string<date-time>

Start time filter (RFC3339 format). An unparseable value is rejected with 400 unless period is set.

end_time
string<date-time>

End time filter (RFC3339 format). An unparseable value is rejected with 400 unless period is set.

period
enum<string>

Time window resolved server-side; takes precedence over start_time and end_time. Sliding periods (1h, 6h, 24h, 7d, 30d) end now. Calendar periods (today, this_week, this_month) start at midnight of the current day, week (Monday) or month in timezone.

Available options:
1h,
6h,
24h,
7d,
30d,
today,
this_week,
this_month
timezone
string

IANA timezone that calendar periods are measured in (e.g. America/New_York). Empty or unknown values fall back to UTC. Ignored for sliding periods.

min_latency
number

Minimum latency filter (milliseconds)

max_latency
number

Maximum latency filter (milliseconds)

Search in tool arguments and results

Response

MCP latency histogram retrieved successfully

Time-bucketed latency histogram

buckets
object[]
bucket_size_seconds
integer<int64>