Online slots API and slot games provider

What is an online slots API?

An online slots API is a single integration that lets an operator launch thousands of slot games from many studios without building a separate connection to each one. As your slot games API provider, SoftAggregator aggregates the catalogue, normalises every title's metadata and handles game launch and wallet messaging behind one consistent interface.

Slots are the backbone of almost every online casino lobby — they drive the majority of sessions, spins and gross gaming revenue. That makes the depth and freshness of your slot catalogue a direct lever on player retention. With our aggregation platform you get breadth (200+ providers), depth (the full back-catalogue) and freshness (new releases added continuously) without any extra engineering each time a studio ships a hit.

You pull the game list, request a launch URL for any slot and embed it in your own lobby. A seamless wallet handles every bet and win, so player funds always stay on your platform.

Slot types and what's included

One integration covers the full spectrum of slot formats players expect:

• Video slots — the modern standard, with rich features, expanding wilds and bonus rounds.
• Megaways and high-volatility slots for players chasing big multipliers.
• Jackpot slots — network and in-game jackpots that drive retention and big-win excitement.
• Feature-buy titles that let players buy directly into the bonus round.
• Classic and fruit slots for players who prefer simpler mechanics.
• Free rounds awarded programmatically on supported games to power promotions.

Each game in the list endpoint comes with its thumbnail, category, free-round support flag, demo-play flag and a stable launch hash, so building and merchandising your slots lobby is straightforward.

How slots integration works

The slots API is a single REST API. You authenticate with the credentials issued after approval, call the game-list endpoint to pull every slot, create a player and request a launch URL that you load in an iframe. For free spins, you call the free-rounds endpoint with the slot, number of spins, bet level and validity period, then list or remove them as needed.

Money flows through the seamless wallet: our platform calls your callback for each spin (debit) and each win (credit), with a unique transaction id for de-duplication. You can also offer demo play for any supported slot. Go-live is four steps — register, get approved, integrate and test in the sandbox, then top up credit and open the slots to players. Full detail is in our API documentation.

Slot supply is where aggregator catalogues overlap most heavily, which is why the choice rarely comes down to game count — what SOFTSWISS publishes about its own aggregator makes a useful reference point when you compare figures.

Why operators choose SoftAggregator for slots

• The freshest catalogue. New slot releases reach your lobby continuously with no extra integration work.
• One balance, one integration. The seamless wallet keeps player funds on your platform.
• Fully opaque white-label. Every slot runs under your brand and domain; providers stay invisible.
• Promotion tooling. Programmatic free rounds for welcome offers, reloads and retention campaigns.
• Live reporting. Per-game bets, wins, RTP and GGR so you can merchandise your best performers.

Slot API checklist: read the game list first

Before writing any lobby code, a team integrating a slot API should look closely at one response: the game list. It decides how much work the lobby will take and how well it will age. With SoftAggregator, each entry carries:

• A normalised category (game_type) separate from the studio's own label, so video slots, Megaways and jackpot titles can be filtered without a hand-built mapping.
• A stable identifier (id_hash, in the form provider/GameName) that survives catalogue updates, so favourites and recently-played rows do not break.
• A demo flag, so a "try for free" button only appears where demo play works; the free casino games API page explains demo mode.
• Studio name, studio logo and a thumbnail for each slot, enough to build provider filters and tiles straight away.

For promotions, free rounds via the API cover welcome offers, reloads and retention campaigns on supported slots, and the set-up is agreed with each operator.

One slot catalogue, different lobbies by market

A slot API delivers the same catalogue to everyone, but no two lobbies should look the same. Operators in Turkey and Brazil often put high-volatility and feature-buy slots up front; South Asian lobbies tend to mix low-stake slots with crash games; crypto audiences in Europe frequently browse by studio, from Pragmatic Play and PG Soft to Hacksaw Gaming and Nolimit City. The player currency passed at launch sets the balance and the bet steps shown inside the slot, so the same game works for an INR player and a EUR player without a second integration.

From sandbox to live slots

The usual path is short. API keys arrive at signup. The team pulls the game list in the sandbox and builds the lobby. The wallet side needs three callbacks (balance, debit and credit) and a signature check, after which test spins can be played end to end. Going live is a matter of topping up credit and switching the lobby on. Each spin produces one debit and, when it wins, one credit, each with a unique transaction id so a retried callback is never paid twice. The fast integration guide gives the typical timeline, the no-setup-fee page covers what the API does not charge for, and every method is in the API documentation.

Online slots API FAQ

Explore more