Product · Slots
Slots API: slot games from many studios on one wallet
The slots API puts video slots, jackpot slots, cluster-pays titles and classic three-reel games from many studios behind one integration. Adding a studio your market already allows is a configuration change, not a new wallet project.
{
"id": "prg_gates_of_olympus",
"studio": "Pragmatic Play",
"category": "slots",
"features": ["free_spins", "multiplier"],
"devices": ["desktop", "mobile"],
"currencies": ["EUR", "USD", "BRL"]
}Catalogue
What the slots API returns for every title
Slot game API metadata
Studio, mechanics, device support, thumbnails and currencies, plus RTP and volatility where the studio publishes them.
Video slots API
Modern five-reel and grid titles with bonus rounds, which make up most of the catalogue and most of the play.
Jackpot slots API
Studios run their own progressive pools. Jackpot wins reach your wallet as normal credits and are flagged in reporting.
Slots provider API filters
Filter by studio, feature or release date to build lobby rows. New releases can surface automatically.
Free spins
Award studio-side free rounds through the same contract. The free spins API page covers the details.
Slot gaming API sessions
Each session is tied to a player, currency and language. One expired token does not take down the rest of the lobby.
Slots API integration
Slot game integration in four calls
Slots integration is the simplest place to start, because every spin is a self-contained debit and credit.
- 01
Fetch the catalogue
Call the slot games API, cache the response and render your lobby from it.
- 02
Launch a session
Request a launch URL with player, currency and language through the slots game API.
- 03
Answer wallet calls
Debit the stake, credit the win, and return the new balance each time.
- 04
Reconcile
Compare daily GGR per studio against your own ledger totals.
Aggregation architecture vs individual studio contracts
Direct studio integration requires building and maintaining distinct API adapters, unique error-handling matrices, bespoke session timeout rules, and separate financial reconciliation pipelines for every provider. Aggregation removes that fragmentation: studios sit behind one wallet contract and one consolidated daily GGR report.
Our slot aggregation platform provides granular control over mathematical configurations. Many tier-1 studios offer multiple certified RTP variants (e.g., 96%, 94%, 92%). During onboarding, we help operators lock in compliant RTP configurations matching local regulatory mandates (such as MGA or UKGC specifications) and prevent unauthorized math switches.
High-spin-per-minute load — bonus buys, free-spin sequences and network tournaments stacked on the same evening — is the pattern that decides whether a slots platform feels stable or breaks. The gateway routes that traffic, but the response time your wallet answers with is what the studio actually feels. Size the wallet for tournament nights before you schedule one, and confirm the promotional toolsets you plan to use (drops and wins, localized tournaments, API-triggered free rounds) are supported on the titles you enable.
Player experience runs on lightweight, responsive HTML5 game clients with instant portrait and landscape switching, detailed game history inside the client, and multi-currency conversion between fiat and approved cryptocurrencies handled at the wallet.
Who controls what in a slot game
Responsibility for the parts of a slot game is split between the studio, the aggregator and you. It helps to know which party you are negotiating with.
| Element | Controlled by | Notes |
|---|---|---|
| RTP and volatility | Studio | Some studios certify several RTP versions, and your licence may restrict which one you use |
| Game certification | Studio and test lab | Certificates are per jurisdiction; we pass them on during onboarding |
| Catalogue and launch | Turnkeyxgaming | One slots API for casino teams, whatever the studio |
| Balance and limits | Operator | Your wallet and responsible-gambling tools stay authoritative |
| Lobby merchandising | Operator | You decide what appears first; the API only supplies the data |
Catalogue pages that sit beside slots
These are not reel slots. They share the casino wallet and have their own lobby job.
- Fish-shooting roomsRepeated shot debits in a shared room.
- RNG tablesSoftware wheels and shoes, no camera.
- BingoTickets, a called sequence, a pattern.
- KenoPicked numbers and a draw.
- Scratch cardsOne stake and one reveal.
Launch planning
How many studios to switch on first
Every extra studio is more than another row of tiles. It is certificates to file, campaigns to check against individual titles, and a longer reconciliation file. Pick the launch size deliberately.
| Launch mix | What you gain | What it costs you |
|---|---|---|
| Two or three studios | Every title reviewed properly before it appears, and lobby rows that fill instead of trickle | Promotions depend on a small set of games, so one disabled title is visible from the home page |
| Eight to twelve studios | Room to split rows by feature and to retire a studio without emptying a page | Each title still needs its own certificate check and its own campaign eligibility review |
| Twenty studios and more | Depth for a catalogue-first brand and coverage of niche mechanics players search for | Curation becomes a job: thin rows, repeated mechanics and a daily file naming studios you never promoted |
Worked example
One spin, four ledger events and one retry
A 0.40 credit spin settles as a debit, a credit and one balance response for each of the two calls. Every call carries the same transaction UUID the launch request produced, so when a weak connection times out and the client retries, your wallet answers with the stored balance instead of taking a second 0.40. That idempotency check is the difference between a retry and a double charge.
Suppose the same spin triggers a free-round award. The paid round closes with its own two calls, and the awarded spins settle as further rounds flagged as campaign. If the player's connection drops on the third awarded round, the client resumes where it stopped and a retried call returns the balance already on record. A settlement written twice shows up later as a few pence of studio discrepancy per incident, and the daily GGR file is where those pence are found.
The failure worth rehearsing before the first tournament is a wallet that answers slowly under a burst of spins. The client retries, the ledger holds two debits for one visible spin, and the player's balance drops for a stake they watched once. With a transaction UUID on every call the incident closes with a one-line support answer; without one it becomes a manual ledger hunt. The wallet contract behind this is the same seamless wallet every other catalogue family uses.
Onboarding
What to put to each studio before a title is enabled
- Which jurisdictions the title is certified for, and a copy of the certificate for your compliance file. Approval for one market does not transfer to the next, and the scope is confirmed in writing during onboarding.
- Whether the feature-buy button may be shown on your licence. It is part of the game's configuration on the studio side, not a switch in your lobby.
- Whether the title accepts externally awarded free rounds. Support differs from game to game inside one studio's line-up; the mechanics live on the free spins page.
- How the studio names the title in its reporting line, so the daily file matches your ledger without a mapping table bolted on afterwards.
- How a jackpot win reaches the ledger on the titles that carry a pool, and what the win line should show a player who won a share rather than the full amount.
Contract shape
Slot aggregator or direct studio contract: the same games, different work
A slot aggregator is a commercial layer, not a fourth game type. The slot games still come from studios, and each round still settles on your wallet. What changes is how many contracts and integrations stand between the lobby and those games. An online slots API through an aggregator gives you one launch call and one wallet contract across the catalogue; a direct studio contract gives you a narrower list and a separate integration per supplier.
The trade is control against breadth. A direct deal can carry bespoke commercial terms and a closer relationship with one studio, and it is the right shape when that studio's slots are the product. An aggregator is the better fit when the lobby needs depth, regional titles and a studio list that changes without a new project. Either way, ask for the certified titles per market in writing, because neither model makes a global catalogue approved where you operate.
FAQ
Questions operators ask
How should a new brand choose slot studios?
Ask which studios in the catalogue are certified for the market you are launching, and whether you can take the games without a white-label platform. A long list does not help if those titles are not allowed on.
Can I choose which RTP version a slot runs at?
Only where the studio certifies several versions and your licence allows the one you pick. The API exposes the version that is configured; it cannot change a certified game.
Do jackpot wins need special handling?
They arrive as credits like any other win, with a jackpot flag. Large wins can trigger your own verification rules before withdrawal. That is your policy, not the studio's.
Does retiring one slot title affect the rest of the lobby?
No. Enablement is per title, and the launch call and wallet contract are shared, so the other titles keep running while you switch one off. The operational detail is on the disabling one title page.
What should we rehearse before scheduling a slots tournament?
A burst of debits, a slow wallet response and the retries that follow. The transaction UUID decides whether a retry becomes a duplicate stake or a stored balance returned as-is.
Where do jackpot wins appear in reconciliation?
Under the studio's reporting line, in whatever shape the studio's contract specifies. Ask how pool wins are reported during onboarding and match your ledger against that shape from day one.
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.
- eCOGRA
Independent testing and RNG certification for online gambling software.
ecogra.org
- UK Gambling Commission
Remote gambling and software technical standards.
www.gamblingcommission.gov.uk
Keep reading
Related pages
- Product · Casino APICasino APIThe casino API is one contract — a catalogue, a launch call and wallet callbacks — built once and reused for every studio we connect.Read
- Feature · Free spinsFree spinsAward free-spin campaigns across studios in one call. Wins arrive as flagged credits on your wallet, with no cash stake behind them.Read
- Studio · Pragmatic PlayPragmatic PlayPragmatic Play slots such as Gates of Olympus and Sweet Bonanza, plus the studio's own live casino and bingo, on one wallet.Read
- Studio · PG SoftPG SoftPG Soft portrait slots such as Fortune Tiger and Mahjong Ways, built for upright phones across Asian and Brazilian lobbies, on one wallet.Read
- CompareSlots vs live tablesA slot settles in a second from an RNG. A live table waits on a dealer and can void the round if the video stream fails.Read
- Guide · LobbyLobby rowsA lobby row should name what the player came to play, not the studio's release email or a raw popularity sort across studios.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.