Skip to main content
Scopes define exactly what your app can do on a user’s behalf. Busha has a flat allowlist of 12 scopes. Anything outside this list is rejected at registration with invalid_scope. Request only what your integration needs. Users see your scope list on the consent screen — asking for more depresses conversion. Users can only Approve or Cancel the full bundle; they cannot cherry-pick individual scopes. Admin approves your partner client overall (not per scope). After approval, approved_scopes = requested_scopes.

​
Identity scopes

These are protocol-level scopes. Busha hides them from the consent screen, but they control whether you receive an id_token and a refresh_token. Request them if you want those tokens.

​
Wallets and balances

​
Trading

​
Transfers

​
Wallet addresses

​
Recipients

​
Common combinations

Always include openid and offline_access in production integrations unless you deliberately want a single-session, one-hour token with no refresh capability.