Scopes and Returned Fields
Portal-owned scope reference synchronized with the current OAuth scope definitions.
Scope model
These scope definitions are sourced from the current portal configuration. Request only the scopes your integration needs, and remember that `profile` is required for every client.
Profile(required)
Access to your username and basic profile
Profile Information
Access to your email address
Email Address
Subscriptions
Access to your club membership and subscription details
Subscription Status
Listings
Access to your marketplace listings and trades
Marketplace Listings
Roles
Access to your platform roles
User Roles
Gaming
Access to your linked gaming accounts (Battle.net, Discord, Steam) and Discord server list
Gaming Accounts
Relics
Access to your relics balance and transaction history
Relics Balance
YouTube Channel Identity
Access to linked YouTube channel IDs for comment identity matching
YouTube Channel Identity
External Club Integration
Allow this client to provision and manage users via the external club integration flow
External Club Integration
This scope enables a specialized integration path rather than exposing a fixed userinfo field list.
Provisioning and webhook enrichment
This scope enables partner services to provision or link users through the external-club flow and optionally attach partner-owned data to the OAuth userinfo response.
Required provisioning fields
Optional enrichment fields and headers
`encryptedPassword` must be a bcrypt hash. The full provisioning guide lives at External Club Integration.
Wallet Embed
Allow this client to resolve delegated external-club session tokens for embedded wallet experiences
Wallet Embed
This scope enables a specialized integration path rather than exposing a fixed userinfo field list.