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.

Path Parameters

id
string
required

The webhook endpoint id.

Response

The webhook endpoint

A registered webhook endpoint. The signing secret is never included in this representation; custom header values are redacted.

id
string
name
string
url
string
events
enum<string>[]

A terminal async-job event a webhook endpoint can subscribe to:

  • async_job.completed: an async job finished successfully
  • async_job.failed: an async job finished with an error
Available options:
async_job.completed,
async_job.failed
headers
object

Custom delivery header values, redacted.

include_response
boolean
allow_private_network
boolean
disabled
boolean
max_retries
integer
retry_backoff_initial_seconds
integer
retry_backoff_max_seconds
integer
attempt_timeout_seconds
integer
max_response_payload_kbs
integer
max_concurrent_deliveries
integer
consecutive_failures
integer

Number of consecutive failed deliveries; reset on the next success.

last_success_at
string<date-time>
last_failure_at
string<date-time>
config_hash
string
created_at
string<date-time>
updated_at
string<date-time>