Casino game aggregator API for online operators

What is a casino game aggregator API?

A casino game aggregator API is a single technical integration that connects your online casino to dozens of game studios at once. Without an aggregator, every studio means a separate contract, a separate integration and a separate certification cycle — months of engineering before a single game goes live. With our aggregation platform, you integrate one REST API and the entire catalogue becomes available instantly.

SoftAggregator acts as that single connection point. We normalise game metadata, wallet messaging, free-round handling and reporting across every provider, so your team works with one consistent interface instead of fifty different ones. The result is faster launches, lower maintenance and a catalogue that keeps growing without any extra integration work on your side.

Whether you are launching a brand-new casino or expanding an existing lobby, the aggregator API gives you a future-proof foundation: a seamless wallet that keeps player funds on your platform, transparent per-provider pricing and live gross gaming revenue (GGR) analytics.

What's included in the API

One integration unlocks the full library and every operational tool you need to run it:

• 40,000+ games across online slots, live dealer casino, crash and instant games, and classic table and card games.
• 200+ premium providers aggregated behind a single endpoint, with new studios added continuously — no extra integration required.
• Game list endpoint returning every title's metadata, thumbnail, category, free-round support and a stable launch hash.
• Seamless-wallet callbacks for balance, debit and credit, so player money always stays on your side.
• Free rounds and bonus tools to award free spins programmatically on supported providers and power your promotions.
• Real-time reporting on bets, wins, RTP and GGR — per game, per player and per period — inside your operator backend.

How the integration works

Every method is a POST request with a JSON body to a single base URL, authenticated with the api_login and api_password you receive after approval. You call getGameList to pull the catalogue, createPlayer to register a player and getGame to receive a launch URL you load in an iframe.

Money flows through the seamless wallet: our platform calls your callback URL for every balance check, every bet (debit) and every win (credit), passing a unique transaction id you use to de-duplicate. Your endpoint always returns HTTP 200 and reports outcomes in the JSON body, with balances expressed as integer cents. A timestamp-and-key signature protects every callback.

Going live is four steps: register your operation, get approved and receive opaque credentials, integrate by pointing your wallet callback at our endpoint and testing in the sandbox, then go live by topping up your credit and opening the games to players. Because the API mirrors the standard seamless-wallet specification, integration is measured in days. Full method-by-method detail lives in our API documentation.

Casino games aggregator software: what it replaces

Operators usually arrive at casino games aggregator software after pricing the alternative. Contracting studios directly means a separate commercial agreement, a separate technical integration and a separate certification cycle for each one. Ten studios is ten of everything, and the tenth costs as much engineering as the first. The aggregation layer exists to collapse that into a single relationship.

What the software actually does is less glamorous than the game count suggests, and more valuable. Each upstream studio exposes its own launch flow, its own wallet messaging, its own metadata vocabulary and its own idea of what a game category is. The aggregator absorbs those differences and presents one normalised surface: one authentication scheme, one catalogue format, one wallet contract, one reporting model. Your team writes against that surface once.

It also absorbs change over time, which is the part that is easy to underestimate at signature. Studios revise their protocols, retire titles, add currencies and alter launch parameters. Handled directly, every one of those is a ticket on your roadmap. Behind an aggregation layer, they are absorbed upstream — new studios appear in the same game list endpoint you already call, and you decide whether to expose them.

Where a casino aggregator software layer does not help is the parts you own: your player accounts, your cashier, your bonus engine, your compliance obligations. An aggregator that offers to take those over is selling you a platform, which is a much larger decision. If the gap you actually have is content, the narrower product is the one to buy.

A casino API module for a platform you already run

Not every operator is starting from nothing. Plenty already run a platform — accounts, cashier, bonuses, reporting — and need only the games. In that case the integration behaves as a casino API module: a self-contained block you attach to an existing system rather than a platform you migrate onto.

The module owns exactly three things: the game list, the launch URL and the wallet callbacks. It never touches your player records, your payments or your bonus engine, and it carries no front end of its own — the lobby stays yours. That boundary is what lets a team add API casino games to a live product without a replatform, and remove or extend the catalogue later without a second engineering project.

The wallet contract: what to check before you integrate

The seamless wallet is the part of an aggregation integration that decides whether your nights are quiet. Player funds never leave your system: we call your callback URL for every balance check, every debit and every credit, and your response is the authority. That keeps reconciliation and compliance on your side of the line, and it puts a handful of edge cases squarely on the specification.

• Idempotency. A network timeout is not a failure — it is an unknown. Every money-moving call carries a transaction identifier, and a repeat of the same identifier must return the original result rather than moving money twice.
• Round identity. A bet and its settlement belong to the same round. If a settlement arrives without the round it belongs to, it should be refused rather than guessed at — a credit with no matching debit is how an operator ends up paying for turnover that never happened.
• Refused is not failed. "Insufficient funds" is a business answer and must be distinguished from a transport error, or a retry loop will turn a declined bet into a settled one.
• Zero and negative amounts. Some outcomes legitimately settle at zero. Your callback needs a defined behaviour for that case instead of treating it as malformed.
• Reconciliation. You should be able to pull a transaction history per player and match it against your own ledger without asking anyone for an export.

These are worth reading in any vendor's specification, not just ours. Our implementation is documented method by method in the API documentation, and the mechanics are covered in more depth on our seamless wallet casino API page.

Launching a game: device, currency and session

Getting a launch URL is a single call, but three parameters cause most of the support tickets we see, and they are worth getting right on day one.

Device is not optional. A launch request that omits the device type will fail for a large share of the catalogue, because many studios serve distinct desktop and mobile builds and have no default. If a subset of games "does not open" while the rest works, this is the first thing to check.

Session currency is decided at launch. The currency the game opens in comes from the launch call, not from your wallet's base currency. If a player's account is in one currency and the game opens in another, the mismatch is in the launch parameters. Currency support also varies by studio rather than being uniform across the catalogue, so it is worth requesting the game list filtered by the currency you intend to serve rather than assuming the headline count applies to all of them.

Some titles launch under a different identifier than the one they are listed under. This is normal in aggregation — a studio's live tables in particular are frequently exposed through a launcher entry distinct from the catalogue entry. The launch endpoint resolves it; you do not need to maintain the mapping yourself.

Currencies, markets and catalogue control

Currency is handled per player rather than per brand, so one integration can serve players in different currencies without a second account. Where a licence requires a single currency, a site can be locked to it instead. Both models run on the same API — the difference is configuration, not integration work.

The catalogue is filterable, and filtering is usually what you want rather than exposing everything. Titles carry category, studio, currency support and market metadata, so you can build a lobby that reflects your licence and your audience: restrict by market where you must, hide studios you have not cleared, and surface the categories your players actually open. New studios appear in the same game list endpoint as they are added upstream, and stay hidden until you choose to show them.

If you are launching into a market with an unusual currency, ask for the catalogue filtered by that currency before you plan the lobby. It is a more honest number than the total, and it is the one your players will experience.

Onboarding: what happens after you apply

There is no sales cycle to get through and no integration fee to negotiate. You request operator access, we review the application, and approved accounts receive API credentials and a callback URL configuration. From there the sequence is short: point us at your wallet endpoint, pull the game list, launch a game in demo mode, then run a real-money round end to end and reconcile it against your own ledger before you open to players.

Teams that have integrated a seamless wallet before typically reach that first reconciled round in days rather than weeks, because the pattern is familiar and the documentation is public — you can read it before you talk to us, which is rather the point. One account can serve several sites, each with its own callback URL, so a second brand does not mean a second integration.

Commercially, the model is prepaid: you top up a balance rather than negotiating a minimum commitment, and rates are quoted per provider rather than as a blended average. We do not publish rates, and neither does anyone else in this market — what we can tell you is what to ask for. Our page on entry fees sets out what is and is not charged.

Live casino and sportsbook through the same integration

Live dealer content runs through the same wallet contract and the same launch flow as slots — there is no second integration and no separate wallet to maintain. The operational differences are real but narrow: live tables are latency-sensitive, so the round trip between the game and your callback matters more than it does on a slot, and table availability changes through the day. Detail lives on our live casino API page.

Sports betting is a genuinely separate product rather than a category of the casino catalogue: a different feed, different settlement timing and a different risk model. It is available alongside the casino integration for operators who want both under one supplier — see the sports betting API and white-label sportsbook pages. If you only need games, you never touch it.

Why operators choose SoftAggregator

Operators pick our aggregation platform because it removes friction at every stage of the lifecycle:

• One balance, one integration. Player funds never leave your wallet, so reconciliation and compliance stay clean.
• Fast onboarding. Register, get approved and receive keys quickly — the API follows a familiar seamless-wallet pattern your developers already know.
• Fully opaque white-label. Your brand, your domain, your credentials. The underlying providers and the aggregation layer stay completely invisible to your players.
• Transparent reporting and pricing. Per-provider economics and live GGR, RTP and bet/win analytics, with prepaid credit control and low-balance alerts.
• Built to scale. Low-latency game delivery and reliable wallet messaging engineered for high-volume distribution.

Casino game aggregator API FAQ

Explore more