Bootstrap Enterprise Access
This guide covers the minimal control-plane sequence for an enterprise integration.
Sequence
Issue an access token
Authenticate the integration and establish the bearer token that will back subsequent control-plane calls.
Read or admit the enterprise perimeter
Establish the tenant topology boundary before creating identities, policies, or downstream clients inside it.
Create service accounts
Create service principals for server-side integrations that need non-human access to the public API.
Create users
Add human actors that need direct tenant-facing access for operational review, setup, or governance tasks.
Define roles, assignments, and policies
Bind actor permissions and operational restrictions before enabling sustained financial activity.
Minimal Token Request
After token issuance, move into client and account topology setup.
Extracting Your Scope Reference
The access_token in the response is a JWT. Before making governance calls,
find your tenant reference: the topology perimeter that endpoints taking a
scope_ref parameter expect.
Decode the JWT payload (the middle part, base64url-decoded) and find the
b2b2x:tenant_ref claim:
sub is the bare service account id, the same value as your client_id.
b2b2x:tenant_ref identifies your tenant boundary. Pass it as scope_ref
where the endpoint declares that parameter. Other operations use account_ref,
parent_ref, or a path identifier; follow their endpoint reference: