A valid request URL is required to generate request examples{
"customers": [
{
"id": "<string>",
"name": "<string>"
}
],
"count": 123,
"total_count": 123,
"limit": 123,
"offset": 123
}List customers attached to a business unit
A valid request URL is required to generate request examples{
"customers": [
{
"id": "<string>",
"name": "<string>"
}
],
"count": 123,
"total_count": 123,
"limit": 123,
"offset": 123
}| Permission | Granted via |
|---|---|
BusinessUnits:View | RBAC role or API key scope |
Authorizations
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 ofBasicAuth).
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. See Required permissions for how permissions are derived and which endpoints are exempt.
Path Parameters
Query Parameters
1 <= x <= 100x >= 0Was this page helpful?