What is a casino game aggregator?

By Soft of Games editorial team · Updated 2026-10-07

A game aggregator sits between your casino and the studios that make the games. You integrate once, and it gives you hundreds of studios through a single API, one wallet protocol and one set of reports. This guide explains the moving parts, the money flow and the limits.

The short version

A casino game aggregator is a company that has already signed and connected a large number of game studios, and resells access to all of them through one technical integration. Instead of writing a separate connector for each studio, you write one connector to the aggregator. When a player opens a slot, your site asks the aggregator for a game URL, and the aggregator asks the studio. When the player bets, the money movement comes back to you through the same channel.

That is the whole idea. Everything else, from game counts to reporting dashboards, is detail built on top of that one shortcut.

Why the job exists

Each studio has its own API. Some use REST with JSON, some still use SOAP. Some send a bet and a win as two calls, others bundle them into one “round” message. Rollback rules differ. Error codes differ. Free spin features differ. A casino that wanted 60 studios ten years ago really did have to write and maintain 60 connectors, and keep them alive through every studio’s version upgrade.

An aggregator absorbs that mess. It normalises every studio into one format, so your developers learn a single set of calls: launch, balance, debit, credit, rollback. When a studio changes its protocol, the aggregator rewrites its side. You never see it.

The second reason is commercial. Signing a contract with a large studio takes time and a minimum level of traffic that a new casino does not have. An aggregator already holds those contracts and spreads them across many operators, which is how a small brand can offer the same famous titles as a large one on day one.

How the pieces fit together

The catalogue call

After integration, you pull a game list from the aggregator. Each entry carries an ID, the studio name, the game type (slot, live, crash, table and so on), thumbnails, supported currencies and sometimes a mobile flag. You decide which entries to show. A good catalogue feed lets you filter by studio and type, because no player wants 30,000 tiles on one page.

The launch call

When a player clicks a game, your server sends the aggregator a request with the game ID, the player ID, the currency, the language and a session token. The aggregator returns a URL. You load it in an iframe or redirect the player. This step decides how fast the game feels. If it takes four seconds, players leave.

The wallet calls

Here is where the money moves. In the most common setup, called a seamless wallet, the player’s balance never leaves your system. The aggregator calls your server for each bet (“debit 2.00 from player 81442”) and each win (“credit 15.40”). Your server answers with the new balance. If your server says no, the bet does not happen. The other setup, a transfer wallet, moves money into a separate game balance before play. We cover both in detail in our seamless vs transfer wallet guide.

Reporting and settlement

At the end of the month the aggregator adds up bets minus wins per studio. That figure, gross gaming revenue, is the base for what you owe. Some aggregators bill monthly in arrears. Others, like SoftAggregator, work on a prepaid credit balance that you top up in advance. Either way you should be able to export round-level data and reconcile it against your own wallet logs.

What you gain

• Time. One integration instead of dozens. With a simple seamless wallet and decent documentation, a developer who knows your backend can get the first game launching in days.
• Breadth. SoftAggregator, for example, lists 40,000+ games from 200+ providers on its homepage. No new casino could sign that many studios directly.
• One invoice. Studio fees are rolled into one bill from one company.
• Faster additions. New studios appear in the feed and you switch them on. You do not run a project for each one.

What you give up

An aggregator is a middleman, and middlemen have costs that are easy to underestimate.

Margin. The aggregator takes a share on top of what the studio charges. On a big casino with heavy traffic on two or three studios, going direct to those studios can be cheaper. Most operators reach that point only after a few years.

Feature lag. When a studio launches a new promotional tool, the aggregator has to expose it through its own API. That can take months, or never happen. Free spin campaigns are the classic example. Some aggregators pass them through fully, some only partly, and some, SoftAggregator included at the time of writing, do not offer a free rounds API yet. If your marketing plan depends on free spins, check this first.

A single point of failure. If the aggregator has an outage, every game it supplies goes down together. Ask how they report incidents and whether they publish uptime.

Less control over the catalogue. The aggregator decides which studios it carries. If one of them drops a studio, you lose it too.

The main types of aggregator you will meet

Enterprise aggregators attached to a platform

Companies such as SOFTSWISS and EveryMatrix sell game aggregation as one product inside a larger casino platform. Their strength is depth: bonus engines, jackpot and tournament tools, account managers. The trade-off is a sales process, onboarding that is measured in weeks, and commercial terms aimed at operators with a business plan and a budget.

Pure game hubs

Hub88 and St8 focus on the game layer and sell it to platforms and operators who already have their own back office. They tend to be strong on API quality and on fitting into an existing stack.

Self-service aggregators

A newer model lets you sign up on a portal and get API keys without a sales call. SoftAggregator works this way: the account is approved automatically, keys are available immediately and there is free test credit for the first launches. It suits startups, crypto casinos and Telegram casinos that want to move quickly. The honest downsides are a smaller team than the enterprise names, lighter documentation, and no built-in tournament or jackpot tools.

Platform providers that include aggregation

Many turnkey platform providers bundle an aggregator so the operator never thinks about it. That is convenient, but it ties your game catalogue to your platform choice. If you leave the platform, you leave the games. Our white-label vs turnkey vs API guide goes deeper into that decision.

A worked example of one spin

1. The player clicks a slot on your lobby page.
2. Your backend calls the aggregator’s launch endpoint with player 81442, currency EUR, language de.
3. The aggregator returns a game URL. Your page opens it in an iframe.
4. The game client loads and asks for the balance. The aggregator calls your balance endpoint. You reply 120.00.
5. The player spins at 1.00. The aggregator sends a debit for 1.00 with a unique transaction ID. You deduct it and reply 119.00.
6. The spin wins 3.50. The aggregator sends a credit for 3.50 referencing the same round. You reply 122.50.
7. If the network drops between 5 and 6, the aggregator retries the credit with the same transaction ID. Your server must recognise the ID and not pay twice.

Step 7 is where most integration bugs live. Idempotency, meaning the same request applied twice has the same effect as once, is the single most important thing your developers need to get right.

When you should not use an aggregator

• You need only two or three studios and have the traffic to sign them directly.
• Your product is a single in-house game, such as a crash game, and third-party content is a sideshow.
• You run a sportsbook only. Note that some aggregators, SoftAggregator among them, carry a sportsbook through the same integration, so this is less of a dividing line than it used to be.

What to look at first

If you are shopping for one now, start with four checks:

• Ask for the live studio list for your target markets, with game counts per studio.
• Read the wallet documentation before any sales call. If it is vague about rollbacks and retries, expect pain.
• Launch a test game in your own environment and time the launch.
• Ask what is missing: free rounds, jackpots, tournaments, specific currencies.

Our guide to choosing a game aggregator turns those checks into a full list of questions.