Online casino API for slots, live dealer and crash games
The IGP online casino API connects your platform to 150+ game studios and 18,000+ titles — slots, live dealer, crash and sportsbook — through one REST integration and a single wallet, with per-market control over what goes live where.
The short answer
What an online casino API actually is
An online casino API — also called a casino games API or an iGaming API — is the interface between your platform and the studios that make the games. Without one, every studio you sign is a separate build: its own authentication, its own game identifiers, its own wallet contract, its own reporting format, its own release schedule to keep up with. Ten studios means ten integrations to write and ten to maintain.
The IGP API replaces all of that with one connection. You authenticate once, read one catalogue, launch every game through the same call, and settle every round against a single wallet — regardless of which of the 150+ studios behind it built the title.
That is the whole proposition, and it is worth being precise about what it means in practice: adding a studio stops being an engineering project and becomes a setting in your back office.
What you integrate once
Authentication, catalogue retrieval, game launch, wallet callbacks and reporting. Five surfaces, documented, with a sandbox that mirrors production.
What you never integrate again
Every studio after the first. New providers are enabled from the back office; new releases from studios you already carry appear in the catalogue on their own.
Who this is for
Operators who already run a platform and need content on it. If you are building the brand from zero, the casino platform and white label routes include this layer already wired in.
One integration
Every vertical through the same endpoint
Slots, live dealer, crash, sportsbook, virtuals and lottery formats all arrive on one connection and settle against one balance — which is what makes cross-vertical bonusing possible at all.
Video slots
The bulk of the catalogue — classic and modern maths from Pragmatic Play, Play’n GO, Wazdan, Habanero, ELK, Hacksaw and 100+ more studios. See the slots API.
Live dealer
Real croupiers streamed from professional studios: blackjack, roulette, baccarat, game shows and regional card games with native-language dealers. See the live casino API.
Crash and instant
Aviator, mines, plinko and the wider instant-game category — short sessions, social mechanics, and the format that converts sports bettors into casino players. See the crash games API.
Sportsbook
Pre-match and in-play feeds across 100+ sports, with bet builder, cash-out and managed trading available on the same platform.
Virtual sports
Continuous simulated fixtures that fill the dead hours between real events — a retention layer most sportsbooks simply go without.
Bingo, lottery and fishing
Regional formats that carry real weight in specific markets: video bingo across Iberia and LatAm, fishing games across Asia.
Technical
How a casino API integration actually works
The honest version, in the order it happens. For a platform with a working wallet endpoint this is a two-to-four week job, and most of that time goes on wallet testing rather than on the catalogue.
Credentials and sandbox
You get an operator ID, an API key and a secret, plus a sandbox that mirrors production — same endpoints, same payloads, same game builds. Requests are signed; every call carries a hash so the server can prove it came from you. Nothing about this step is unusual, and it takes a day.
Catalogue sync
A single call returns the whole library as normalised JSON: game ID, studio, name, category, thumbnails, supported languages and currencies, device support, RTP configuration where the studio exposes it, and the jurisdictions the title is certified for. You cache it and re-sync on a schedule. This is the step that lets your lobby be built once instead of per studio.
Game launch
To open a game you send a signed request with the player ID, session token, game ID, currency, language and jurisdiction. You get back a URL to load in an iframe or a webview. The API resolves which studio, which build, which language pack and which regulatory configuration applies — your code does not need to know. Demo mode, mobile and desktop builds, and re-entry into an interrupted session all run through the same call.
Wallet callbacks
This is the part that decides whether the integration is good or painful. During play the API calls your endpoints: balance, debit, credit and rollback. Each call carries a unique transaction reference, and your side must be idempotent — the same reference arriving twice must never move money twice. Rollback has to be handled properly for the case where a round is voided after a debit already succeeded. Get idempotency and rollback right and you will never lose a cent; get them wrong and you will find out during a network blip on a Saturday night.
Reporting and reconciliation
Rounds, bets, wins, bonus contribution and jackpot events arrive in one normalised stream. You reconcile that against your own wallet ledger daily. Per-jurisdiction segmentation matters from day one, because duty calculations have to balance to the cent and retrofitting the segmentation later means re-deriving history.
Certification and go-live
Each game carries the markets it is certified for, and the API enforces that at launch: a title not certified for a jurisdiction cannot be opened by a player in it, whatever your lobby shows. You confirm the market configuration, run a final pass in the sandbox, and switch traffic. Adding studios after this point is a toggle.
Architecture
Seamless wallet or transfer wallet
The single most consequential decision in a casino API integration, and the one most often made by accident.
| Seamless wallet | Transfer wallet | |
|---|---|---|
| Where the balance lives | Always on your side — one source of truth | Funds move into a game session and back out |
| What happens per round | The API calls your debit and credit endpoints in real time | A transfer in before play, a transfer out after |
| Cross-vertical bonusing | Works — one balance across casino and sport | Difficult; balances are fragmented by session |
| What you must build | Real-time endpoints with idempotency and rollback | Transfer logic and orphaned-balance handling |
| Failure mode | A dropped callback, solved by idempotency | Money stranded in a session after a crash |
| Use it when | Almost always | Legacy platforms that cannot expose live endpoints |
Seamless is the modern default and the one we recommend: it gives a single live balance across every provider and every vertical, which is the precondition for a player acquired on football spending on slots without a second deposit. Our full breakdown of seamless wallet vs transfer wallet covers the edge cases in detail.
Slots API
Slots API: 18,000+ slot games through the same connection
Slots take the majority of play in almost every online casino, and the depth of the slot lobby decides whether a brand feels alive or empty. The slots API is the slot vertical of the casino API: the whole slot market from 150+ studios, without wiring it studio by studio.
What a slots API is
A slots API is the bridge between your platform and the studios that build slot games. Your platform requests the game list, launches sessions, settles bets and wins against your wallet and pulls round data for reporting, all over standard HTTPS calls. Games run on the providers’ servers; your platform stays the source of truth for accounts, balances and bonuses.
Every title arrives with the same metadata whatever the studio: RTP, volatility, features, themes and thumbnails. That is what lets you build a lobby by behaviour rather than by supplier — a high-volatility row for the stream crowd, classic reels for traditional players, portrait-mode games for mobile-heavy markets.
What is in the slot catalogue
Tier-one studios such as Pragmatic Play, Play’n GO, NetEnt and Microgaming; stream favourites such as Hacksaw and Nolimit City; mobile-first Asian studios such as PG Soft and JILI; land-based classics from Novomatic, EGT and Amatic; and new mechanics from Big Time Gaming and Booming.
Formats cover video slots, Megaways and cluster pays, progressive and fixed jackpots, classic fruit reels and bonus-buy titles, which you enable per market from the back office wherever you choose to offer them. The full roster is on the casino game providers page.
| Direct studio deals | IGP slots API | |
|---|---|---|
| Technical integrations | One per studio | One, total |
| Adding a studio | New contract and new build | A toggle in the back office |
| New releases | Chased per provider | Appear automatically |
| Game metadata | A different format per studio | One normalised schema |
| Wallet | Several flows to reconcile | One seamless wallet |
| Per-market control | Negotiated studio by studio | Configured in one place |
| Maintenance | Grows with every provider | Flat, whatever the catalogue size |
Built for regulated markets
New regimes write rules into the game client itself: autoplay restrictions, forced breaks, session alerts and per-market feature limits. Each one becomes a per-title question. Through one API it is configuration: you switch providers and individual titles on or off per jurisdiction, and each region receives exactly the catalogue you approved. Bonus-buy availability, demo play and jackpot eligibility sit in the same back office.
Slots API, slot game API or slot machine API?
Three names for the same thing. Slots API is the industry term; slot game API is common in developer searches; slot machine API tends to come from teams with a land-based background. Whichever you searched for, the requirement is the same: a documented interface that returns the catalogue, launches secure sessions on any device and settles bets and wins against your wallet in real time.
Live casino API
Live casino API: real dealers on the same wallet
A live dealer game is one real event watched and bet on by thousands of players at once: a croupier at a physical table in a licensed studio, a real wheel or shoe, and software whose job is to watch, record and settle. Nothing about the outcome is generated by software. Your platform never touches the studio; it talks to the same API as slots and receives a stream, a set of events and a settlement.
The table opens and your lobby sees it
A dealer takes the table and the game engine publishes it with its limits, language and rules. Your lobby requests the table list through the API: open or closed, seats free, limits, language and current round.
The betting window
The engine opens a timed window, synchronised to the studio rather than to the player’s device. The player stakes; the API validates the bet against your wallet in real time and reserves the funds. No balance leaves your platform.
The dealer acts and the result is read
The wheel spins or the cards leave the shoe. Optical recognition, RFID-tagged cards or wheel sensors read the result the instant it exists.
Settlement and archive
The engine resolves every position and pushes payouts back through the API; your wallet is the ledger. Result, bets, payouts and the video of the round are archived together, which makes a dispute answerable rather than arguable. On roulette the cycle repeats roughly every 30 to 60 seconds.
Why live is not slots, technically
Latency is a product feature. The betting window is a real countdown against a real dealer, so adaptive bitrate delivery decides whether the lobby feels premium or broken on a mobile network.
Capacity is finite. A table has a fixed number of positions, which is why bet-behind and regional tables exist.
Language is localisation. A dealer speaking the player’s language is worth more than twenty extra tables, so the catalogue is filtered by language and market.
State is shared. Every player sees the same round, so reconnection and mid-round disconnects are where weak integrations show themselves first.
Studios and tables
Live studios in the catalogue include Evolution, Ezugi, Pragmatic Play, Playtech, BetGames, SA Gaming, Vivo Gaming, 7Mojos, HoGaming, OneTouch and Absolute Live Gaming. Availability is confirmed per market, because not every studio is cleared everywhere.
Formats cover roulette, blackjack with bet-behind, baccarat with roads and squeeze, game shows, poker and dice, plus regional tables such as Teen Patti, Andar Bahar, Sic Bo and Dragon Tiger. Studios, tables, dealer languages and stake ranges are enabled per market from one back office.
Live casino API, live dealer API or live games API — three names for the same interface: a table list with languages, seats and limits, a secure low-latency session on any device, and real-time settlement against your wallet.
| Shared tables | Dedicated tables | Branded studio | |
|---|---|---|---|
| What it is | Studio tables shared with other operators | Tables reserved for your brand | An environment built around your brand |
| Time to live | Immediate once integrated | Short setup | A project |
| Branding | Studio branding | Your name on the table and felt | Full environment and dealer scripting |
| Best for | Launching and testing demand | Established volume in a market | Brands competing on experience |
| Integration work | None beyond the one API | None beyond the one API | None beyond the one API |
Most operators launch on shared tables and move right as volume justifies it. The integration does not change between them, so the commercial arrangement can grow without a second technical project. For choosing a supplier, see how to choose a live casino provider.
Crash games API
Crash games API: Aviator, JetX and 20+ crash studios
Crash and instant games arrive through the same integration and wallet as slots and live tables. What changes is the traffic pattern and the features you test, not the integration itself.
What a crash game is
A crash game is a single shared round. A multiplier starts at 1.00x and climbs until it stops at a point fixed by the game’s random number generator. Every player bets before the round starts and decides when to cash out: cash out before the stop and the stake is paid at the current multiplier; wait too long and it is lost.
The category grew out of Aviator from Spribe and JetX from SmartSoft. Studios now build mines, plinko, limbo and ladder games on the same quick-round logic, usually grouped with crash in the lobby as instant games. Short, social rounds are why many operators use them to bring sports bettors into the casino.
What changes in the wallet
A crash bet is debited when the round starts; a cash-out is a separate credit, often seconds later and decided by the player. Some games allow two bets per round, each its own transaction. A losing bet may get no further call or a zero-value result that closes the round, depending on the provider.
When a round ends, many players’ calls arrive together. Wallet latency that is fine for slots can cause timeouts here, and timeouts cause retries — which is why idempotency and rollback, covered in our integration checklist, matter even more for this category. Before launch, test auto cash-out (including when the player has closed the tab), two bets cashed out at different moments, free bets and how their wins are tagged, and where players find provably fair round checks.
| Studio | Known for | On record |
|---|---|---|
| Spribe | Aviator, plus turbo and instant games | Spribe OÜ, Estonia; UKGC licence 057302-R-333085-003; MGA licence from February 2021; Aviator live in Ontario since April 2023 |
| SmartSoft | JetX, launched 2018, and an X-series of crash and instant titles | Smartsoft Limited, Malta; MGA/B2B/925/2021; Romania ONJN 1180/28.06.2021 |
| Galaxsys | Crash, mines, plinko and limbo formats; 60+ games in 170+ currencies | MGA/B2B/592/2018; UKGC account 63601 |
| Aviatrix | Crash game with a customisable NFT aircraft carried between titles | Kiverly Ltd, Cyprus; AGCO Ontario B2B registration, December 2024 |
| Turbo Games | Crash, mines, ladder and keno, with roughly one release a month | TurboDev OÜ, Estonia 16488251 (register-confirmed) |
| BGaming | Crash and casual games with a documented provably fair system across 35 titles | MGA/B2B/785/2020 |
| Elbet | CrashClicker titles such as Rocketman and Soaring, plus Plinko | Elbet Limited, Malta; MGA/B2B/997/2023 (company-stated) |
| 100HP Gaming | Crash and instant games such as Astronaut, Chicken Pirate and Meta Crash | 100HP Group Ltd., Seychelles; Curaçao sub-licence claimed, no number published |
Licence details come from our provider profiles, which state where a fact is company-stated and where it was checked on a register. Also listed under crash in the catalogue: Gaming Corps, Mascot Gaming, Kalamba, Jili, Tada Gaming, Topspin, BetGames, Endorphina, Jacktop Play, Betcore Play, Champion Play, Betsolutions, Yoriginal Games and Abracadabra.
| Slots | Crash games | |
|---|---|---|
| Round | One player, one spin | Many players share one round |
| Wallet calls | Bet and win per spin | Bet at round start, separate cash-out |
| Peak load | Spread over time | Bunched at the end of each round |
| Player view | Private session | Shared curve and live bet list |
| Disputes | Replay of the spin | Round history and the multiplier at cash-out |
| Integration through IGP | One API | The same API and wallet |
Crash games API, crash game API or Aviator API? The same interface goes by several names. Many teams search for an Aviator API, but Aviator is a game made by Spribe, not a provider of its own: operators reach it through Spribe directly or through a casino games aggregator, and through IGP it runs on the same connection and wallet as the rest of the catalogue. For the market picture, see our crash games guide for 2026.
Which product
Casino API, aggregator or full platform
The same catalogue is reachable three ways. Which one you want depends on how much you intend to build yourself.
Casino API
The raw surfaces — catalogue, launch, wallet and reporting — for slots, live casino and crash, for teams building their own lobby and merchandising layer.
How the integration works →Casino game aggregator
The same content plus the back office: per-market toggles, lobby ordering, campaign tooling and reporting, managed for you.
Casino game aggregator →Platform or white label
For brands launching from zero: the platform and white-label routes include this content layer already wired in.
Casino platform →If you are weighing the difference between an API integration and a managed aggregator: the API gives you the raw surfaces and you own the lobby; the aggregator gives you the same content with the merchandising and market controls already built. Operators launching a brand from scratch normally take the platform instead, and add a sportsbook alongside it where the market is sports-led. Sweepstakes and social casino platforms use the same integration configured for dual currency — see the sweepstakes casino API.
Markets
Launch the API in any GEO
Content availability is enforced per jurisdiction at game launch, so one integration can serve several regulated markets with completely different lobbies.
Asia
Mobile-first, portrait-mode builds, local payment rails and the table and fishing formats Asian players actually look for. See iGaming solutions for Asia.
Latin America
Crash games, Spanish- and Portuguese-language live dealers and local currencies, configured market by market. Brazil prohibited online casino on 25 September 2026, so casino content is switched off there; other markets in the region keep their own rules. See solutions for the Americas.
Europe
One platform configured market by market: currencies, languages, stake and speed rules, and the reporting a regulator expects. See solutions for Europe.
Coverage extends to Africa, Canada and the Philippines, and the full picture is on the markets overview. One point worth making plainly: a lobby cloned across regions underperforms. Coverage analysis across six European markets in August 2026 found only two slot titles present in every top 30 — everything else is local, which is exactly why per-market control matters more than catalogue size.
Providers
The studios behind the API
150+ integrated providers, from the studios every lobby needs to the regional specialists that make a local lobby feel local.
The full list is on the casino game providers page — 150+ studios, A to Z. How operators get access to a specific studio is covered in our Pragmatic Play, Evolution and JILI API guide.
Evaluation
How to choose a casino API provider
Every supplier in this market says the same six things. The questions below are the ones that actually separate them, and they are worth asking before a contract rather than after. The full set, with what a good answer sounds like, is in our guide to the 20 questions to ask a casino API provider.
Ask about the wallet contract, not the game count
Request the idempotency and rollback specification in writing. A supplier who cannot hand you a clear document describing what happens when a callback is delivered twice, or when a round is voided after a successful debit, is a supplier whose integration will cost you money at some point.
Ask which studios, not how many
A provider count is a vanity metric. Check the specific studios and franchises against what the top brands in each of your markets actually carry — the overlap between markets is far smaller than most catalogues imply.
Ask about per-jurisdiction enforcement
Is market availability enforced at game launch or only reflected in the lobby? If it is only the lobby, one integration cannot safely serve several regulated markets, and you will discover that during an audit.
Ask for round-level reporting
Daily summaries are not enough. You need per-round data for duty reconciliation, bonus-cost analysis and honest per-title performance decisions. Ask to see the actual schema.
Ask what happens at 2am on a Saturday
Get the escalation path and the response commitment, and ask specifically what happens to open rounds when a single studio goes down. The answer tells you more about the supplier than any uptime number on a slide.
One connection
Every provider through one integration, on one balance
This is the part that decides how your platform behaves for the next three years, and it is easy to skip past in a supplier conversation.
Every one of the 150+ studios sits behind the same connection. Not one connection per studio that we manage for you — one connection, full stop. The same authentication, the same catalogue call, the same launch request, the same reporting stream, whether the title was built by Pragmatic Play, by a live studio in Bulgaria or by a crash developer in Georgia.
The practical consequence is that your first integration is your last one. Adding a studio afterwards is a switch in the back office rather than a sprint: no new credentials, no new wallet contract, no new reporting format to map, no second reconciliation to run. Operators who signed studios directly usually discover the cost of the alternative around the fourth provider, when the maintenance burden stops being linear.
Underneath it there is one balance. A player’s money does not live in a slots wallet, a live-casino wallet and a sportsbook wallet that have to be reconciled against each other — there is a single figure, held on your side, that every provider debits and credits in real time.
That single balance is what makes everything above the surface possible. A player can move from a football bet to a live table to a slot in one session without a transfer, a delay or a second deposit. Your CRM sees one customer rather than three. Your finance team reconciles one ledger rather than one per studio. And a bonus can be written once and honoured everywhere, because there is only one place for it to land.
One integration, one wallet, one view of the player. Everything else on this page is a consequence of those three.
For your engineers
What your developers get on day one
An API is only as good as the material around it. Everything below exists before you sign anything, because an integration that stalls on missing documentation is a launch date you lose.
Full REST reference
Every endpoint, every parameter, every error code, with request and response examples that match what the server actually returns.
Postman collection
Importable collection with environments pre-configured, so the first successful call takes minutes rather than an afternoon.
Sandbox that mirrors production
Same endpoints, same payloads, same game builds. What passes in the sandbox behaves identically when you switch traffic.
Wallet test harness
Deliberate duplicate callbacks, dropped responses and rollback scenarios, so idempotency is proven before real money touches it.
A named integration engineer
One person who knows your build, on a shared channel, rather than a ticket queue and a different responder each time.
Go-live checklist
The pass we run with you before switching traffic: certification coverage, market configuration, reconciliation, failover behaviour.
FAQ
Casino API — common questions
Connect your platform to 150+ providers
Tell us the markets, the verticals and the platform you run. You get sandbox credentials and a scoped integration plan for your platform.