🔗Supplier Integration Service

The PlayFusion API Game Provider Content

We have taken every effort to ensure the accuracy of the content provided in this document at the time of its publication. However, please be aware that this document is subject to future changes. As necessary updates arise, we will release new versions to ensure the most accurate and up-to-date information is available.


  • Game Launcher URL – Allows TBB to:

    • Generate game launch sessions for players.

  • Game Events – A Seamless Wallet integration. Triggered by the Supplier to:

    • Request the player’s balance.

    • Send bet transactions to deduct from the player’s balance.

    • Send win transactions to credit the player’s balance.

    • Refund a previously completed transaction.

  • Free Spin API - Allows TBB to:

    • Create an award (free rounds) for a player on the supplier's side.

    • Cancel an award (free rounds) assigned to a player on the supplier’s side.

  • Game Insights - Allows TBB to:

    • Retrieve valid bet levels (amount) for the specified game and currency, which are used during free spin creation.

    • Requests the historical game graphic link for a given round ID from the Supplier.

  • Addendum — Error Codes Reference.

    • Contains all possible error codes and their meanings.


Getting Started

To begin integrating with TBB, ensure you have the following:

  • Game Launch URL you, as the Supplier, must provide this URL to TBB for generating gameplay sessions.

  • Game API URLyou, as the Supplier, must provide this URL to TBB, which will be used for Free Spins, Bet Levels, and Historical Rounds.

  • Provider ID – provided by TBB.

  • Provider Name – provided by TBB.

  • Password – provided by TBB, used for signing requests (HASH).

  • Wallet URL – provided by TBB.

To receive the required credentials, please contact us at info@thebetbrothers.com. Our technical integrations team will guide you through the setup process.

Request Signing with HMAC-SHA256

All request bodies must be signed using HMAC-SHA256 with your secret key. The signature must be included in the X-REQUEST-SIGN header of the request.

Last updated