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

providers
string

Comma-separated list of providers to filter by

models
string

Comma-separated list of models to filter by

status
string

Comma-separated list of statuses to filter by

objects
string

Comma-separated list of object types to filter by

selected_key_ids
string

Comma-separated list of selected key IDs to filter by

virtual_key_ids
string

Comma-separated list of virtual key IDs to filter by

project_ids
string

Comma-separated list of project IDs to filter by

routing_rule_ids
string

Comma-separated list of routing rule IDs to filter by

routing_engine_used
string

Comma-separated list of routing engines to filter by (routing-rule, governance, or loadbalancing)

tool_call_names
string

Comma-separated list of function names. Matches requests whose response called any of them, using the persisted tool_call_names metadata on the log row. Names are recorded even when content logging is disabled and stay on the row in hybrid storage mode; the call arguments are not.

complexity_tiers
string

Comma-separated list of routing complexity tiers to filter by (SIMPLE, MEDIUM, COMPLEX, or the legacy REASONING tier recorded on historical rows before it was merged into COMPLEX)

complexity_mechanisms
string

Comma-separated list of complexity decision mechanisms to filter by (semantic, decision, llm, session, or skipped)

session_id
string

Exact Bifrost session ID used for key stickiness and request correlation

start_time
string<date-time>

Start time filter (RFC3339 format)

end_time
string<date-time>

End time filter (RFC3339 format)

min_latency
number

Minimum latency filter

max_latency
number

Maximum latency filter

min_tokens
integer

Minimum tokens filter

max_tokens
integer

Maximum tokens filter

min_cost
number

Minimum cost filter

max_cost
number

Maximum cost filter

missing_cost_only
boolean

Only show logs with missing cost

Search in request/response content

request_id
string

Exact lookup on a log ID (which is the request ID). Takes precedence over the time range — start_time/end_time/period are ignored when it is set. roots_only is ignored too, so an ID naming a fallback child returns that child rather than collapsing it into its root.

roots_only
boolean
default:false

Hide rows whose parent_request_id points at another row matching the same filters, so each fallback chain lists as its root request. The root carries child_count, children_cost and children_tokens for the rows it hides. Ignored when parent_request_id or request_id is set.

group_sessions
boolean
default:false

Collapse every row sharing a session_id onto that session's earliest root request, which carries session_child_count, session_total_cost and session_total_tokens. Requires roots_only=true, and is ignored when session_id, parent_request_id or request_id is set. Sorting orders the collapsed rows by the root row's own value, not by the session total.

limit
integer
default:50

Number of logs to return (default 50, max 1000)

Required range: x <= 1000
offset
integer
default:0

Number of logs to skip

sort_by
enum<string>
default:timestamp

Field to sort by

Available options:
timestamp,
latency,
tokens,
cost
order
enum<string>
default:desc

Sort order

Available options:
asc,
desc

Response

Successful response

Search logs response

logs
object[]
pagination
object

Pagination metadata for list responses

stats
object

Log statistics

has_logs
boolean

Whether any logs exist in the system