// casino api integration
Connect slots, live casino, crash games and a sportsbook with one casino API integration. Your developers build it once, and our team helps at every step.
// how it works
Behind every game in your lobby there is a studio server, often called a remote gaming server (RGS). It runs the game logic. Your platform does not talk to each studio server directly: it talks to one API, and the aggregator passes each request to the right studio.
Three things travel through the integration. Your platform receives the game list with names, images and categories. When a player opens a game, the API returns a launch link. While the player plays, bets and wins move between the game and the player's balance.
How that last part works depends on the wallet model.
// wallet
APICasino supports both models: seamless wallet and transfer wallet.
// step by step
A casino games integration with APICasino runs in five steps.
Tell us about your platform, your markets and the content you need.
Our team shares the API documentation after reviewing your request.
Your developers connect the game list, game launch and wallet calls.
Pick the studios and games for your lobby.
Open the games to players. Our support stays with you after launch.
// slot api
Many teams start with a slot API, because slots are the largest part of most lobbies. With APICasino, the same slots API also brings live dealer games, crash games and a sportsbook, so a new vertical does not mean a new project.
Every slot games API request, live table and betting market goes through the same integration your developers already built.
// game list and launch
The game list is the base of your lobby. For each game it usually carries a name, a studio, a category and images, so your team can build categories, search and filters without adding games by hand.
When a player opens a game, your platform requests a launch link for that player and that game. The game then opens inside your site or app, on desktop or mobile.
New games appear in the list as studios release them. Your lobby can pick them up without any change to the integration.
// first call
Questions worth settling with our technical team before your developers start.
Seamless or transfer, and how your platform confirms bets and wins.
How your lobby requests a launch link and where the game opens.
Which calls your wallet answers and what happens when a call fails.
Which studios and game types you start with, and how new games reach your lobby.
Where your developers test the integration before real players see it.
How lost connections, repeated requests and refunds are handled.
// before you start
A casino API integration is a developer task on your side. Here is what usually takes part in it.
Someone who connects the game list, game launch and wallet calls.
With a seamless wallet, your platform confirms every bet and win.
Categories, search and game tiles on your site or app.
A decision on which studios and games to show in each market.
// faq
Didn't find yours? Ask it in the request form below.
A remote game server, or RGS, is the studio's server that runs the game. With APICasino you connect to one API instead of each studio's RGS.
No. Live dealer games come through the same API as slots.
No. We share it with operators after a request through the form below.
Both. You can connect with a seamless wallet, where the balance stays on your platform, or with a transfer wallet, where funds move to a game balance before play.
Our technical team, from the first request to launch and after it. Support works 24/7.
A slot API covers slot games only. A casino API covers the whole lobby: slots, live casino, crash games and betting. APICasino gives you all of them through one integration.
Yes. You choose which studios and game types to show, and you can add more later without a new integration.
// related
Tell us about your project. We review every request and contact you to discuss API access and how the catalog fits your lobby.
// studio
Listed in the APICasino catalog. Send a request and we'll tell you how it connects through the same API.