Player

Optional module for player identity, profile data and platform authorization.

Authorization Support

Check this before showing a login button. Authorization support depends on the host platform.

bridge.player.isAuthorizationSupported
chevron-rightPlatform support · 17 of 28 platformshashtag

Supports: absolute_games, bitquest, crazy_games, discord, facebook, huawei, microsoft_store, msn, ok, playdeck, playgama, samsung, telegram, tiktok, vk, y8, yandex

Does not support: dlightek, game_distribution, gamepush, gamesnacks, jio_games, lagged, poki, portal, reddit, xiaomi, youtube

Is the Player Currently Authorized

Use this to decide whether protected features are available right now, such as account-based saves, personalized content, or social actions.

bridge.player.isAuthorized

Player ID

Returns the player's platform ID when available. Use it for display, analytics correlation, or backend verification, but do not rely on it until authorization is confirmed.

bridge.player.id

If the platform supports authorization and the player is currently authorized, this returns their platform ID. Otherwise, it returns null.

Player Name

Returns the display name provided by the platform. Use it for profile UI, leaderboards, friend lists, or social prompts.

Returns null when no name is available; otherwise returns a string.

Player Avatar

Returns available player avatar URLs. Use the largest suitable image for profile UI, lobbies, or leaderboard rows.

Possible values: an array of avatar URLs sorted by increasing resolution, or an empty array.

Player Extra Fields

Returns platform-specific authorization data. Properties vary by platform.

Use this data on your backend to verify authorization. Playgama API verification currently supports only playgama, msn, and microsoft_store.

Player Authorization

Start the platform authorization flow. Call this from a direct player action, such as tapping a login button, before enabling account-only features.

Last updated