Product · Casino API
Casino API for catalogue, game launch and wallet callbacks
The casino API is the contract your platform builds against: a catalogue of titles, a game launch call, and wallet callbacks that debit stakes and credit wins.
{
"player_id": "p_82731",
"game_id": "evo_lightning_roulette",
"currency": "EUR",
"language": "en",
"mode": "real",
"return_url": "https://your-casino.example/lobby"
}- Titles in the catalogue
- 40,000+
- Studios behind one contract
- 300+
- Wallet contract to build
- 1
- Typical integration window
- 24–72h
Scope
What the casino API actually covers
Slots, live tables, crash, fishing and table games from 300+ studios, including fishing titles, use that one contract. The casino API aggregator page is about why those studios sit behind one integration, and how reconciliation works, rather than how each call is shaped.
Strip away the marketing and a casino API is three contracts: a catalogue, a launch call and a wallet. The casino content API returns the titles your licence allows, with studio, category, device support, thumbnails and currencies. The game launch API opens a session for a signed-in player and hands back a URL for your game frame; the route and field names on this page are an illustrative shape, and the versioned request in your docs pack is the executable one. The wallet side calls your ledger to debit stakes and credit wins. Lobby design, bonuses, KYC and payments stay on your platform unless you take a turnkey build.
Your engineers own the player account and the money. They cache the catalogue, open a session with the launch call, and answer balance, debit, credit and rollback. A new studio does not mean a second wallet implementation, because the studio never talks to your ledger directly. Month-end reconciliation across studios is described on the casino API aggregator page.
Endpoints
The calls your team will actually use
Casino games API
List and filter titles by studio, category, device and market. Cache the response and refresh it on a schedule rather than on every page view.
Casino lobby API
Categories, tags and sort fields let you build lobby rows such as new releases or live roulette without hard-coding a studio name anywhere.
Game launch
Create a session with player, currency, language and return URL, then open the returned URL in demo or real mode inside your own frame.
Wallet callbacks
Balance, debit, credit and rollback requests hit your endpoint. The full contract lives on the casino wallet API page.
Casino API reporting
GGR by studio, title, brand and currency, so finance can reconcile one statement instead of chasing a dozen studio invoices.
Fishing games API
Fishing titles carry their own category flag, so you can give them a dedicated lobby row instead of burying them among the slots.
Fishing game integration without a second project
Fishing games are shooter-style arcade titles, popular across Asian and Latin American lobbies. Players fire at targets with a chosen bet value, and each hit can pay out.
What stays the same
- The same launch call and session token as every slot
- Debits per shot batch and credits per payout on your wallet
- Rounds show up in the same GGR report under their studio
What to plan for
- Higher callback frequency than a spin-based slot
- Landscape-first game clients on mobile
- A category filter, so fishing gets its own lobby row
The contract
One casino API contract, not a project per studio
Every studio integrated directly brings its own launch format, wallet protocol, certification pack and invoice. These rows are the shape of the contract you build. Why the studios are aggregated, and how the invoices are reconciled, is the casino API aggregator.
| Turnkeyxgaming casino API | Direct studio integrations | |
|---|---|---|
| Integrations to build | One | One per studio |
| Wallet protocols | One seamless wallet contract | A protocol per studio, often different |
| Adding a studio | A contract and configuration change | A new engineering project |
| Reporting | One GGR statement across studios | Separate statements to reconcile |
| Commercial terms | Published GGR share: 13% Asia, 16% elsewhere | Negotiated separately with each studio |
Architecture
Platform vs Aggregator vs Remote Gaming Server (RGS)
Understanding the clear separation of responsibilities prevents architecture bottlenecks and compliance delays. The Remote Gaming Server (RGS) is operated by each game studio (such as Pragmatic Play, Evolution, or Spribe) to execute the certified RNG math, render game animations, and return round-level results. The Aggregator (Turnkeyxgaming) standardizes these 300+ disparate studio protocols into a single normalized REST interface, handling player session validation, jurisdiction-based game filtering, per-session currency selection, and high-speed transaction routing. Currency conversion itself stays in your ledger and cashier: the aggregator binds a session to one currency, and the casino wallet API explains why that boundary matters.
The Operator Platform (PAM) owns player accounts, KYC verification, cashier operations, and responsible gambling controls. When integrating our casino API, your platform implements four webhook callbacks while our gateway shields your servers from individual studio nuances. If you do not operate an existing PAM or player ledger, our full turnkey casino solution provides the entire player account, payment, and front-end infrastructure out of the box.
When this casino API solution is the right fit
This casino API service is built for teams that already run, or are about to run, their own player accounts. As an iGaming casino API it fits well when:
- You hold, or are applying for, a licence in the markets you plan to serve
- Your platform can expose authenticated balance, debit and credit endpoints
- You want many studios without a separate integration for each one
- Finance needs one reconciliation file rather than one per studio
- You may add sportsbook or live casino later without a second wallet
Vocabulary
Casino game API, gaming API or platform API: which one is being bought
A team may arrive asking for a casino game API, a gaming API or a casino platform API, and the three are not the same purchase. This page describes the casino game API: the catalogue, the launch call and the wallet callbacks that let a studio's game settle on your ledger. A casino platform API is the player-account system around it, covered on the casino platform page. A studio's own remote gaming API is the interface behind one supplier's games, not a contract across suppliers.
The distinction matters at contract time. A unified casino API gives you one wallet implementation and one reconciliation file across the catalogue. If a supplier's quote describes a single studio's endpoint and calls it an aggregator, the wallet work is the same but the studio list is not. Ask which studios sit behind the endpoint before comparing rates, and read the aggregator page for the multi-studio side of the same product.
FAQ
Questions operators ask
Can an online casino API work with the lobby I already have?
Yes. The online casino API returns data, not a finished lobby. You render titles in your existing front end and open each game in your own frame, so your brand and layout stay as they are.
Is there a separate integration for fishing games?
No. Fishing titles use the same launch and wallet calls as every other game. The only difference is that the callback volume is higher, so make sure your wallet endpoint is sized for it.
How many studios can I switch on at once?
As many as your licence and target markets allow. Studio availability varies by jurisdiction, so we confirm the list for each market during onboarding instead of promising every studio everywhere.
What does the casino API cost?
Pricing is a share of gross gaming revenue: 13% for Asian markets and 16% elsewhere, confirmed in a written quote. The pricing page explains how that is calculated.
References
Sources and further reading
Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.
- Malta Gaming Authority
Licensing and player-protection rules for Malta-licensed operators.
www.mga.org.mt
- eCOGRA
Independent testing and RNG certification for online gambling software.
ecogra.org
Keep reading
Related pages
- Product · Game aggregationAggregatorOne aggregator contract for licensed operators: 40,000+ games from 300+ studios at 13% of GGR in Asia and 16% elsewhere.Read
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
- DocumentationAPI docsAuthentication, the game list, demo and real launch, AES-encrypted wallet callbacks and error handling, with test keys to start.Read
- IntegrationIntegrationSandbox keys, AES-encrypted wallet callbacks and the four wallet endpoints, then a 24–72 hour go-live once decryption and retries pass.Read
- Guide · ArchitectureHow a casino API worksOne casino round traced end to end: catalogue, launch, wallet callbacks, settlement and the report line the next morning.Read
- GlossaryRNGA certified random number generator decides software results. A live wheel or a dealt shoe is a different source of outcomes.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.