Boss HubBoss HubDocs
ChangelogStatus
Getting started/Overview

Overview

Boss Hub is a B2B game platform that offers its own Boss Originals titles and connected providers in one place. A single Seamless Wallet integration gives you the whole catalogue; the balance stays with you, and every money movement reaches your wallet as a signed callback.

Two directions

DirectionPurposePage
Operator → Boss HubREST API: game list, game launch, round and transaction lookup, free rounds, jackpots, GGR reportsProvider API
Boss Hub → OperatorSeamless Wallet callbacks: authenticate, balance, bet, win, rollbackSeamless Wallet
Boss Hub → OperatorEvent notifications: big wins, stuck rounds, invoices, new games and moreWebhook events

How a round flows

Operator     ── POST /v1/game/launch ──▶  Boss Hub
Boss Hub     ── launch_url, session_id ─▶  Operator
Player       ── launch_url ─────────────▶  Boss Hub ── /authenticate ──▶  Operator
Game         ── round ──────────────────▶  Boss Hub ── /bet, /win, /rollback ──▶  Operator
Boss Hub     ── webhook events ─────────▶  Operator
  • You open a session for the player with POST /v1/game/launch; the response carries a single-use launch_url.
  • When the player opens that address, Boss Hub has you verify the token through authenticate and starts the game.
  • In each round bet debits the balance and win credits the winnings. If no bet reply arrives, a rollback follows.
  • You query results with GET /v1/rounds and GET /v1/reports/ggr, and receive important events by webhook.

Core rules

  • The balance stays with you. Boss Hub holds no balance. The supported wallet model is Seamless Wallet.
  • Every request is signed. Both directions use HMAC-SHA256. See Authentication & signing.
  • Wallet calls are idempotent. A repeat with the same transaction_id must receive the first processed result as is.
  • IDs are a prefix and a 26-character ULID (rnd_01M753KW12T4EMPVCZQB1C6YMC); transaction IDs get a suffix such as -b1. Examples are shortened. Do not parse IDs; store them as strings.
  • Business rule errors return HTTP 200. The body carries status: ERROR and a code. See Error codes.
  • Amounts are JSON numbers with two decimals, e.g. 148.60. Currencies are USD, EUR, TRY. See Currencies & languages.
  • There are two environments: Test (staging) and Live (production); each has its own API address, shown on the Integration & API page of the portal. Live requires an IP allowlist. See Environments & IP allowlist.

Where to start

Begin the integration with the Quickstart. For the money safety rules, read bet, win and rollback first. Before going live, all 42 scenarios of the test suite must pass.

Next →Quickstart