A small integration surface, documented end to end
One versioned REST API, one call per bet, and a widget you can embed three ways: next to a slot (game integration) or as an overlay on a casino site (casino integration). Here is what you build and where to find the details.
What you build
1. Signed API client
Your backend signs every request with HMAC using the key we issue you. Requests are versioned under /v1/partner and errors use stable numeric codes.
2. Sessions and the widget
Start a session for a player, receive a launch link, and embed the widget, next to your game or as a casino overlay, with our SDK or a plain iframe.
3. Bets and wins
Send each Extra Bet (for a casino, each play on a bet you choose) with your own bet id and credit the win from the response. Retries with the same bet id are safe and return the original result.
The API at a glance
- Sessions: start and close a player’s game session and get the widget launch link.
- Bets: one synchronous, idempotent call that plays the game and returns the win.
- Cancel: cancel a bet you could not complete on your side.
- Rounds: look up any Round by your bet id for support and reconciliation.
- Bet levels: read the levels an Operator offers for a game, with their prices in a currency.
- Players: block and unblock a player for responsible gaming.
Amounts travel as decimal strings, never floating-point numbers, so every currency keeps its exact precision.
Illustrative only. The field names below show the shape of a bet; the contract is defined in the docs and the OpenAPI file.
{
"sessionToken": "st_7f3a9c…",
"betId": "your-unique-bet-id",
"betCreatedAt": "2027-03-01T12:00:00.000Z",
"level": 5,
"amount": "0.50",
"currency": "EUR"
}Response
{
"status": "committed",
"betId": "your-unique-bet-id",
"roundId": "rnd_9QxL…",
"currency": "EUR",
"win": "12.50"
}Integration documentation
The Partner integration guide, with a track for game integration and a track for casino integration, is published here as it is written. Pilot Providers and pilot casinos get updates first.
- 01IntroductionWhat ReelXtra is, the two ways to integrate (game and casino), and how this guide is organised.
- 02ConceptsThe parties, games, triggers, bet levels, rounds and jackpot terms used throughout the API.
- 03OnboardingFrom early-access request to sandbox access, Groups and Operators and production go-live, for Providers and Operators.
- 04AuthenticationHMAC-SHA256 request signing, the canonical string, nonces, clock skew and test vectors.
- 05Sessions and widgetCreating and relaunching sessions, embedded and overlay widgets, SDK events, and reveal modes.
- 06BetsThe bet call, the trigger, the response, retries until a definite answer, cancel, and the carried-over bonus.
- 07ErrorsThe error format, every error code, whether to retry, and what to do.
- 08ReconciliationDaily reconciliation files per Partner, round look-ups, reports and the monthly settlement document.
- 09ComplianceResponsible gaming hooks, Compliance Profiles, trigger rules, bet limits and what stays with the Operator (including autoplay).
- 10GamesPartner-facing rules for Reel Stars, Reel Triple and Reel Streak.
- 11Go-live checklistEverything that must be true on your side before real-money traffic, with one checklist per integration stream.
Ready to integrate?
ReelXtra launches in 2027. We are inviting a small number of pilot Providers and pilot casinos to integrate early, help shape the product and be first to offer our Extra Games.