Create a client session
Create a short-lived client session for one existing UPA, from your backend.
accountId or externalUserId. Both are strict lookups: this endpoint never creates or updates a UPA, so create the account through the Partner API first.
Grant only the permissions this browser or mobile flow needs; omitted permissions default to account:read. Each permission also requires the matching app module and issuing credential scope. The app secret stays on your backend. Pass the returned clientSessionToken to the client, which exchanges it once for a client bearer token.
See Authentication.Authorizations
Headers
Body
- Create client session request
- Create client session request
Bind the client session to exactly one UPA using either identifier.
Least-privilege operations embedded in this account-bound client token. Each permission also requires the matching app module and issuing credential scope.
1 - 6 elementsAccount-bound browser/mobile authority granted by the partner backend. This is narrower than the issuing app credential and cannot enable a disabled app product.
account:read, payments:read, payments:write, deposits:read, deposits:write, vault_payments:write Response
Client session token
Account-bound browser/mobile authority granted by the partner backend. This is narrower than the issuing app credential and cannot enable a disabled app product.
account:read, payments:read, payments:write, deposits:read, deposits:write, vault_payments:write