Live dealers. Real tables. One API.

Strip away the interface and a live dealer game is one real event being watched and bet on by thousands of people at once. There is a physical table in a licensed studio. There is a croupier who spins a real wheel, deals from a real shoe, and calls the game out loud. Nothing about the outcome is generated by software — the software’s job is to watch, record and settle.

That is the whole reason the format exists. A slot asks a player to trust a random number generator they cannot see. A live table asks them to trust their own eyes. For a large share of players — particularly in markets with a strong land-based tradition — that difference is the reason they deposit at all.

What sits between the table and your player is a chain of systems: cameras and encoders, optical or sensor-based recognition of the result, a game engine that runs the betting window, and an API that carries table state one way and bets the other. Your platform never touches the studio. It talks to one interface and receives a stream, a set of events and a settlement.

Everything on this page is delivered through that single connection, alongside slots, crash and sport — the architecture is described on our casino API page.

People. A table is staffed around the clock, which in practice means three shifts, relief dealers, and a pit boss watching several tables at once. Dealers are trained to studio standard rather than casino-floor standard: they present to a camera, keep pace with a countdown they cannot see, and speak the language of the market the table serves.

Equipment. Regulation wheels and shoes, card shufflers, RFID or optical readers, multiple camera angles per table, and an encoder per feed. The equipment is calibrated and audited, because a mis-read card is a settlement error, not a cosmetic one.

The room itself. Studio lighting, acoustic treatment, redundant power and dual internet paths. A live studio that loses power mid-round has an incident to resolve with real money attached.

Oversight. Every round is recorded and retained. Supervisors watch for procedural errors, and the archive is what a regulator or a player dispute is settled against.

None of this is your problem when you take live through an aggregator, and that is precisely the point. Staffing rotas, croupier training, camera calibration, studio compliance and the licensing of the physical room all sit with the supplier. What you receive is a table that is open, a stream that plays, and events that settle correctly against your wallet.

The alternative — building it yourself — is a hospitality business with a broadcast department attached. Very few operators should be in it, and the ones who are usually start by renting a dedicated table first.

Sessions get longer. A slot session ends when the player decides. A live session ends when the player leaves a table they are sitting at, with a dealer they can see and a round already counting down. The format is built to make stopping feel like standing up and walking away, and it shows in average session length.

Average stakes are higher. Live tables attract a different player than the slot lobby does, and they arrive with different expectations about limits. A live vertical typically raises blended revenue per player even when it takes a modest share of total rounds.

Trust converts. In markets moving from land-based or grey play into regulated online, a visible dealer is the single most effective answer to the question every new player silently asks: is this rigged? You cannot argue someone into trusting an RNG. You can show them a wheel.

It fills the dead time in sport. A football match is ninety minutes of which a handful are eventful. A bettor between markets either opens something else or closes the app — and live casino has the closest rhythm to in-play betting of anything in the casino. On a shared wallet with your sportsbook, that is the highest-value cross-sell most operators have.

It holds the top of your player base. High-value players concentrate in live far more than their share of accounts suggests. A casino without live tables is not just missing a category — it is missing the room its best players expect to find.

It makes a brand look finished. A lobby with no live section reads as unfinished to anyone who has used a competitor, and that judgement is made in the first thirty seconds of a first visit.

Latency is a product feature. A slot tolerates a slow round. A blackjack table does not: the betting window is a real countdown against a real dealer, and a player whose stream lags behind the table loses the hand for reasons that have nothing to do with the cards. Delivery, adaptive bitrate and regional capacity decide whether your live lobby feels premium or broken.

Capacity is finite. A slot serves unlimited concurrent players. A dealer serves one table and a table has a fixed number of betting positions — which is why bet-behind exists, why studios run regional tables, and why the table mix you enable matters more than the table count.

Language is localisation, not translation. A dealer speaking the player’s language is worth more than another twenty tables, which is why native-speaking desks and regional studios exist and why a live catalogue must be filtered by language and market rather than dumped into one lobby.

State is shared. Every player at a table sees the same round. That makes reconnection, disputed bets and mid-round disconnects genuinely hard problems, and it is where weak integrations show themselves first.

Live tables carry obligations that slots do not. Stake limits, table availability, session behaviour and what a player may be shown while a round is running are written into market rules, and they apply per table rather than per brand. Several markets also require that the studio serving them holds its own local approval.

Through one connection that becomes configuration: you enable studios, tables and limit ranges per jurisdiction, and each market receives exactly the live lobby you approved for it. When a rule changes, the change is a switch rather than a round of supplier emails.

The reporting side matters just as much. Every round, every bet and every settlement is recorded against your wallet with a full audit trail, segmented per jurisdiction from day one — which is what a regulator asks for and what a duty calculation has to reconcile against.

If you are preparing an entry into a newly regulated market, the sequencing is covered in our operator guides, and a ready casino platform can carry the same content layer if you would rather not build the front end.

Casinos adding a live vertical open a second revenue line without touching the platform. Your wallet, bonusing and reporting stay as they are; live tables appear alongside the slots you already run.

New brands launch complete. A casino without live tables reads as unfinished, and adding the vertical later costs more attention than including it at launch.

Platform providers and white labels use it as the live layer for every brand they host, configuring tables, languages and limits per client and per market from one place.

Sportsbook operators use live dealers as the between-matches product, on the same wallet as the bet slip — see our sportsbook software.

The same interface goes by three names. Live dealer API is the most literal and the most common in North America. Live casino API means the same thing and dominates in Europe. Live games API tends to appear in developer documentation, where the distinction being drawn is against RNG games rather than against slots specifically.

Whichever term you searched for, the requirement is identical: a documented interface that returns the table list with languages, seats and limits, opens a secure low-latency session on any device, and settles every bet and payout against your wallet in real time. That is what this page describes — and it is one vertical of the same connection that carries the rest of your lobby.