Roulette API: live dealer, auto and software roulette through one integration

Three kinds of roulette behind one word

When operators ask for a “roulette API” they usually mean one of three products, and the difference matters more for the lobby than for the code.

• Software (RNG) roulette. A random number generator decides the pocket. No video, no timer, the player spins when ready. In our game list these carry game_type: table.
• Live dealer roulette. A real wheel, a croupier, a studio or a land-based floor on camera, and a betting window that opens and closes on a countdown. These carry game_type: live.
• Auto roulette. A real, filmed wheel with a mechanical ball launcher and no croupier. Rounds are short and the table runs continuously. It is live content — game_type: live — even though nobody is dealing.

All three open through the same launch call and settle through the same callbacks documented in our API reference. The integration is identical; the player experience and the betting rhythm are not. Live and auto tables are part of the same live dealer API that carries baccarat, blackjack and game shows.

The wheel decides the maths

Before any branding or multiplier, the wheel sets the return. A European wheel has 37 pockets and a single zero, which puts the house edge at 2.70% and the return to player at 97.30%. An American wheel adds a double zero, 38 pockets, and the edge rises to 5.26% — a return of 94.74%.

French rules keep the single-zero wheel and add La Partage or En Prison on even-money bets: when the ball lands on zero, the player loses half or has the stake held for the next spin. On those bets the edge drops to about 1.35%. If your market is European, the American wheel is usually a poor choice to feature; if your players are used to it, offer it but do not lead with it.

Live roulette formats and what they change

Studios have built many formats on the same wheel. The ones below are the ones operators ask about; the studio figures come from Evolution’s own game pages.

• Standard live roulette. A dealer, a wheel, a betting timer. The baseline.
• Speed roulette. A shorter cycle between spins. Evolution publishes 25 seconds from start to finish for its Speed Roulette. More rounds per hour means more debits per player-hour.
• Multiplier roulette. Evolution’s Lightning Roulette strikes between one and five lucky numbers each round with payouts between 50x and 500x. To fund them, an ordinary straight-up win pays less than the classic 35:1 — 29:1 on that table.
• Auto roulette. No croupier, a machine-launched ball, short rounds, open all day.
• Immersive, dual-play and VIP tables. Multiple cameras and slow-motion replays; wheels on a real casino floor streamed online; high-limit tables with their own limit sets.

Bets, chips and the wallet

Roulette is the game where one round can produce the most wallet movements, because players build a layout chip by chip. Expect several debits per round and at most a few credits.

• Batched chips. Many clients confirm chips in groups. Straight-ups placed early and a neighbours bet added late can arrive as two debits sharing one round_id.
• Call bets are still chips. Voisins du zéro, tiers and orphelins are combinations of ordinary bets placed from the racetrack. The wallet sees money, not bet names.
• One pocket, several winners. A number can pay a straight-up, a split and a column at once. Whether that arrives as one credit or several is the studio’s choice; your handler should accept either.
• De-duplicate on call_id only. Every callback has a unique call_id. Round and game ids are for traceability, not for rejecting calls.
• Refusing a chip is fine. If a debit would overdraw the player, answer error: 1 with the current balance; the client removes the chip rather than failing the round.

The signature rules, the cents convention and the rollback flag are the same as for every other game, and are set out on the seamless wallet page.

Latency: the betting timer and your callback

The stream reaches the player from the studio, not through you, so video quality is out of your hands. Debit speed is not. A live roulette window closes on a countdown, and a bet whose debit has not been answered when it closes does not make the spin.

The practical target is a debit answered in well under a second, every time, including at the peak of an evening. Keep the balance check simple, avoid synchronous calls to other systems inside the handler, and host the endpoint where network distance is short. Always state the device type when requesting a launch URL; without it a number of platforms turn the request down, and mobile players would miss the client designed for their screens.

Results, history and the winning-number strip

The spin result lives in the game, not in the wallet, and our history reflects that. getPlayerHistory returns one line per round for a player — stake, win, net, number of legs merged, rollback flag and timestamps, paged in blocks of up to five hundred — which is what support needs to answer “was I paid for that spin?”.

What it cannot return is the number that came up. The documentation says so in general terms: round outcomes stay in the game and are never passed to the money side. The hot-and-cold statistics and last-numbers strip players see are drawn by the game client. If you want them on lobby tiles, that is table data a studio supplies under its own agreement, not something any wallet-based API can reconstruct.

Bet limits and currencies

Limits are set per table and per currency, and the launch call carries the currency that selects them. The catalogue and currencies evolve continuously; the up-to-date list is always in the API. If a market needs lower minimums, pick an auto or standard table rather than a VIP one, or serve the currency whose limit ladder fits. A player’s currency is fixed when the player is created; call getCurrencies to see which ones your account can use.

Restricted markets are handled per player from the country you send on a real-money launch. Where a studio holds no licence for that country, the request is turned down immediately with a readable reason, which beats a table that breaks mid-session.

Building a roulette shelf

A workable first shelf is one standard live table, one speed or auto table, one multiplier format and one software roulette for low stakes and demo play. Add French rules for European audiences, VIP limits once you have the players, and an American wheel only where it is expected.

For the other two live table games, the live baccarat API page covers road maps and commission rules and the live blackjack API page covers seats and mid-round decisions. The overview of live content through one integration is on the live casino API page, and if you want software roulette available as demo play in some markets and not others, see our guide to demo mode per jurisdiction.

Roulette API — questions operators ask

Sources and last update

Round times, multiplier ranges and the 29:1 straight-up on Lightning Roulette are Evolution’s numbers, used here to illustrate the market. Pocket counts and house edges are textbook roulette arithmetic. The API behaviour described matches our published reference.

• Evolution, published pages for Speed Roulette and Lightning Roulette (games.evolution.com). Checked 24 September 2026.
• The SoftAggregator reference, sections on the game list, currencies, launching, player history and callbacks — read again on 24 September 2026.

Last reviewed: 24 September 2026. If a figure here has changed, write to [email protected] and we will update the page.

Explore more