API

You are reading the documentation for Bridge SDK v2. If you need the obsolete v1 documentation, see Documentation (v1).

Reference for Playgama Bridge SDK modules. Method names and behavior are identical on every platform — Bridge maps each call to the native platform SDK internally.

Required steps

These steps are mandatory for every game. Platforms verify them during moderation — a game that skips any of them can be rejected or behave incorrectly for players.

1. Wait for Bridge initialization before calling any SDK API. In Plain JS call bridge.initialize() and wait for the promise; engine plugins initialize automatically while the game loads (see Setup).

2. Localize the game using platform.language — read it once after initialization and use it as the source language for your localization system.

3. Save and load progress through Storage — never use localStorage directly.

4. Subscribe to the pause and audio state events. Platforms fire these events when the player switches tabs, minimizes the browser, or an ad opens — a game that keeps playing sound in the background fails moderation.

5. Send platform.sendMessage('game_ready') when the first playable frame is ready — platforms use this message to hide their loading screen and start analytics.

6. Show interstitial ads at natural pauses, such as level transitions or game over — platforms require them to qualify for revenue share.

Everything else — optional, but highly recommended

The remaining modules are not required to pass moderation, but each one directly improves monetization, retention, or platform ranking. Integrate as many as make sense for your game.

Monetization

• Advertisement → Rewarded — opt-in ads for in-game rewards (extra life, double coins, hint). Usually the highest-eCPM format because players consent.

• Advertisement → Banner — passive ads on idle screens (menu, lobby, pause).

• Advertisement → Advanced Banners — multiple banners with custom positions and responsive layouts, driven by config placements.

• Advertisement → AdBlock detection — detect blocked ads and show fallback messaging.

• Payments — in-game purchases, both consumable and permanent, with a single product catalog for all platforms.

Engagement and retention

• Leaderboards — competitive score tables.

• Achievements — milestones ("defeat the first boss").

• Tasks — daily / weekly / permanent quests with progress tracking and rewards.

• Daily Rewards — login streak rewards.

• Social — share, invite friends, join community, add to favorites, rate the game. Free organic acquisition.

• Cross-Promo — "more games" modal and games-list API to route players between your titles.

Platform integration depth

• Player — authorization state, player id, name, and avatar for personalization and server-side profiles.

• Device — device type, OS, orientation events, safe-area insets for notch-aware layouts.

• Remote Config — platform-managed flags to tune the game without a release.

• Clipboard — copy/paste for invite links and promo codes.