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

endpoint_ids
string

Comma-separated webhook endpoint ids. Omit for all endpoints.

events
string

Comma-separated event names, e.g. async_job.completed.

outcomes
string

Comma-separated delivery outcomes: delivered, retryable_failure, permanent_failure, exhausted.

status_class
string

Comma-separated response status bands: 2xx, 4xx, 5xx, or none for attempts where no response arrived. Bands are alternatives (OR).

request_id
string

Exact inference request id the delivery was raised for.

delivery_id
string

Exact delivery-run id (the webhook-id wire header).

start_time
string<date-time>

RFC3339 lower bound on attempt time. Ignored when period is set.

end_time
string<date-time>

RFC3339 upper bound on attempt time. Ignored when period is set.

period
enum<string>

Window resolved server-side. Takes precedence over start_time / end_time. Sliding periods (1h to 30d) end now; calendar periods (today, this_week, this_month) start at midnight in timezone.

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

IANA timezone that calendar periods are measured in. Empty or unknown values fall back to UTC. Ignored for sliding periods.

limit
integer
offset
integer

Response

A page of delivery history

deliveries
object[]
pagination
object