New Supplier Games SDK

Native game delivery and real-time operator communication for Suppliers

Released: 20 April 2026

---

The Supplier Games SDK lets your games run natively inside an operator's website — without iframes — with real-time two-way communication between your game and the operator. You as a supplier provide a JavaScript file that Hub88 loads directly on the operator's page, giving players a faster experience and unlocking live controls that weren't possible with iframes.

This SDK requires compatibility and works when the operator is using the Operator Games API SDK. If the operator uses a traditional iframe integration, the game continues to load via your existing URL as normal.

Why we built it

Once a game loads in an iframe, there's no clean way for an operator to control it (sound, theme, language) or for the game to report back what's happening (round started, error occurred).

The Supplier Games SDK fixes that — a consistent, documented communication layer between your game and the operator, available to every supplier without custom integration work on either side.

Key highlights

• No iframes as your game renders directly inside a container element on the operator's page.

• Two-way communication as operators send commands to your game (sendAction, sendCustomAction); your game dispatches events back (game-play-started, game-play-ended, game-notification, game-custom-event).

• Standard actions included as setSound is required for all suppliers; any other actions are agreed directly between you and the operator.

• Custom config at launch to return game_sdk_init_params from your /game/authorize endpoint to pass theme settings, feature flags, or environment URLs into your SDK at session start

• Backwards compatible as your existing iframe integration keeps working. Both /game/url and /game/authorize must stay active.

How it works

Phase 1: Session setup (server-side) Hub88 calls your new /game/authorize endpoint. Your backend initialises the session and returns any custom config via game_sdk_init_params, which Hub88 merges into the token sent to the operator.

Phase 2: SDK initialisation (client-side) Hub88 imports your JavaScript file from your CDN URL, instantiates GenericSupplierGames, and calls init(config) — including your game_sdk_init_params in config.meta. The init() authenticates, loads assets, and renders the game. When the Promise resolves, the game is live.

Phase 3: Game running Operators send commands via sendAction() and sendCustomAction(). Your SDK dispatches events to window via hub88-game-sdk-supplier-event. Wallet transactions continue through the Supplier Wallet API — the SDK handles frontend communication only.

What you need to build

1. Your existing Supplier API integration — unchanged and still required.

2. The Supplier Games SDK — a single JavaScript ES module file hosted at a stable CDN URL, exporting the GenericSupplierGames class

3. A /game/authorize endpoint — sets up the player session like /game/url, but without returning a game URL

A browser-based playground validator (available via Technical Operations Team) lets you check your SDK before sharing the CDN URL with Hub88.

Explore the SDK

See more in our comprehensive documentation Supplier Games SDK ↗.