Introduction

What ReelXtra is, the two ways to integrate (game and casino), and how this guide is organised.

On this page

Pre-release draft (API v1). ReelXtra launches in 2027. Field names, error codes and host names in this guide can still change before general availability. Changes will be announced to early-access Partners before they take effect.

ReelXtra lets you offer our Extra Games — small, fast side games with optional progressive jackpots — next to slot games and casino bets, without building or certifying them yourself.

You integrate as a Partner: the party whose backend calls the ReelXtra API (application programming interface). There are two integration streams. They use the same API; they differ in who you are, where the widget sits and what triggers a play.

Game integrationCasino integration
Partner kindProvider: a game studioOperator: an online casino
Where the widget sitsEmbedded in your slot's game pageAn overlay on the casino site, independent of any game
What triggers a playEach base spin of your slotAny casino bet the Operator chooses
Who decides which bets trigger a playYou (the Provider)The Operator, with its own trigger rule
Default revealWhen your reels stop (you call reveal)Immediately

Both streams can run at the same Operator for the same player at the same time. Read the chapters for your stream; shared chapters have Game integration and Casino integration callouts where they differ.

How it works: game integration

When a player spins your slot with the Extra Game switched on, your backend takes the Extra Bet from the player's balance and sends it to ReelXtra. We play the Extra Game with our game engine (lab certification in progress) and return the win in the same HTTP response. Your backend credits the win. At the same time our widget, embedded in your game page, receives the result and shows the Extra Game animation as soon as your reels stop.

One spin with the Extra Game: the player spins, your backend debits and sends the bet to ReelXtra, credits the win from the response, and the widget shows the held result when your client calls reveal

How to read it: the numbers give the order, and time runs downwards. Your backend debits the base bet and the Extra Bet (step 3), sends the signed bet (4) and credits the win it gets back in the same response (5, 6). The widget receives the result at the same time but holds it (7) until your game client calls ReelXtra.reveal(roundId) when the reels stop (8), then plays the animation and shows the win (9).

How it works: casino integration

The Operator shows the ReelXtra widget as an overlay on its casino site. When the player takes a casino bet that the Operator's trigger rule selects, the Operator's backend checks that the player has the side game switched on (the widget reports it with ready and optInChanged; ReelXtra refuses a play while it is off, see The on/off switch decides play), takes the Extra Bet from the balance and sends a play request to ReelXtra. We play the Extra Game and return the win in the same HTTP response. The Operator credits the win. The overlay receives the result and shows it at once.

One casino play with the Extra Game: the Operator backend applies its trigger rule, debits the Extra Bet, sends the bet to ReelXtra, credits the win, and the overlay shows the result at once

How to read it: the numbers give the order, and time runs downwards. The Operator backend takes the casino bet, applies its trigger rule and debits the Extra Bet (steps 3 and 4), sends the signed bet (5) and credits the win from the response (6, 7). The overlay receives the result and shows it at once (8, 9).

In both streams ReelXtra never holds player money and the widget never sends a bet: only your backend does.

What you build

  1. Server side (both streams): sign requests (HMAC), create a game session per player and game, send one POST /v1/partner/bets per Extra Bet, and handle retries and errors as described here.
  2. Client side:
    • Game integration: embed the widget with one line of our SDK (or a plain iframe), and call reveal when your reels stop.
    • Casino integration: mount the widget as an overlay. Nothing else is needed on the client when plays are revealed immediately (the casino default).
  3. Operations (both streams): reconcile daily, and forward responsible-gaming actions such as player blocks.

What you don't build

  • Game maths, random number generation or certification of the Extra Games.
  • Jackpot pools, contributions or jackpot settlement between casinos.
  • Any wallet on our side: ReelXtra never holds player money. The Provider's backend and the Operator keep the balance; we only tell you the win.

How this guide is organised

ChapterWhat it covers
ConceptsThe terms used in the API: Partner, Provider, Operator, Extra Game, Trigger, Bet Level, Round, Pool.
OnboardingSandbox access, keys, your Groups and Operators and the go-live path for each stream.
AuthenticationRequest signing, with test vectors.
Sessions and widgetCreating and relaunching sessions, embedded and overlay widgets, reveal modes.
BetsThe bet call, the trigger, retries, cancel, statuses and the response fields.
ErrorsEvery error code and what to do about it.
ReconciliationDaily files, round look-ups and reports.
CompliancePlayer blocks, bet limits and jurisdiction rules.
GamesPartner-facing rules of each Extra Game.
Go-live checklistEverything you must have in place before real-money traffic, one list per stream.

The machine-readable contract is the OpenAPI 3.1 file openapi.yaml that accompanies this guide. The Partner API is built from the same request and response types the file describes (one typed record per body, in the project ReelXtra.PartnerApi.Contracts), and our automated tests compare the file with those types, property by property: names, required or optional, null or not, and type. A field the file lists is a field the API sends, and a field the API sends is in the file.

Hosts

EnvironmentHostPurpose
Sandboxhttps://sandbox.reelxtra.netIntegration and testing with test keys and test outcomes. It hosts all three Domains (Open, Regulated and White label), so whichever Domain you are onboarded into, you test here.
ProductionSupplied at go-liveReal-money traffic, one host per Site. Your Domain (Open, Regulated or White label) is set at onboarding, not chosen by the host.

Each Site has one host, and the path says who is calling:

PathForUsed by
/v1/partner/...The signed Partner API (application programming interface).Your backend only.
/v1/public/...The widget app, the SDK (software development kit) script, round history pages and the live connection.The player's browser.

You never call /v1/public from your backend, and the widget never calls /v1/partner. The reelxtra.net host names may change before launch; the production host is supplied at go-live.