API

Online casino API

One integration, every studio your licence allows. The API handles game launch, the wallet callbacks per bet and win, round history and the reporting your regulator wants, so you integrate once rather than per provider.

Request API documentation

Seamless wallet or transfer wallet

Two wallet models exist in casino aggregation. In a seamless (single) wallet the game provider calls your wallet for every bet and every win in real time; the player has one balance across everything. In a transfer wallet funds are moved into a provider sub-balance before play and back afterwards. Seamless is what players expect and what regulators prefer for reporting; transfer survives only for a few legacy studios. Our API is seamless first: you implement four callbacks (balance, debit, credit, rollback) once, and every studio behind the aggregation uses them.

What the API covers

  • Game catalogue: games with metadata (studio, type, RTP, volatility, features, supported currencies and jurisdictions) filtered automatically to what your licence permits.
  • Launch: signed game-launch URLs for real and demo play, with player, currency, language and licence context.
  • Wallet callbacks: balance, bet, win, rollback; idempotent, with round and transaction identifiers for reconciliation.
  • Bonuses: free spins and bonus money orchestrated across studios; per-market rule sets so a Finnish brand can be locked to retention-only with a 5× cap while an offshore brand is not.
  • Jackpots and tournaments: network and local jackpots, leaderboards, studio tournaments.
  • Reporting: round history for player support and disputes, GGR by game and studio, regulator exports in the formats the licences we serve require.

Content

Aggregators publish their catalogue sizes: Hub88 states more than 26,000 games; EveryMatrix and SOFTSWISS are reported at 40,000 to 45,000 games from 300 to 355 studios. The number that matters to an operator is smaller: the games your licence and your target studios' jurisdiction lists both allow, in the currencies your players use. We give you that list for your specific licence at scoping rather than a headline count.

Integration

REST with signed requests; sandbox with studio test environments; certification of your wallet callbacks against a scripted set of edge cases (double debit, rollback after win, currency mismatch, disconnected round). Two to six weeks from sandbox access to production keys for a platform team that has built a wallet before.

Frequently asked

Can we add our own games?

Yes. Your studio integrates once to our provider API and appears in the catalogue for your brands and, if you wish, for others.

Is live dealer included?

Yes, from the live studios whose jurisdiction lists include your licence; live content is the category with the strictest licence lists.

Does the API work for a crypto casino?

Yes; the wallet is currency-agnostic, and crypto balances are handled as currencies with the settlement in your crypto cashier.