Casino game aggregator: every game your casino needs, one integration.
IGP is a casino game aggregator for online casino operators, sweepstakes brands and white-label platforms. One API, one wallet, one contract — and a catalogue of 150+ game providers and 18,000+ certified titles behind it: slots, live dealer, crash, table games, bingo, keno and virtuals.
The definition
What a casino game aggregator actually is
A casino game aggregator is a company that has already signed, certified and technically integrated hundreds of individual game studios, and exposes all of them to an operator through a single API and a single commercial agreement. Instead of negotiating with Pragmatic Play, Evolution, Play’n GO, Hacksaw and 146 others separately, the operator signs once with the aggregator and receives the whole catalogue.
The word “aggregation” describes exactly what happens on the technical side. Every studio publishes its games with slightly different session handling, different bet and win message formats, different currency rules, different round-closing logic and a different reporting schema. An aggregator absorbs all of that variation and re-publishes it in one normalised form. Your platform learns one protocol; the aggregator translates it into 150+ dialects behind the scenes.
That is why operators describe an aggregator as a content layer rather than a supplier. A supplier sells you games. A content layer removes the engineering, legal and accounting cost of ever adding a game again — because the next studio you want is already inside the same connection, on the same balance, and appears in the same report.
For the operator the practical effect is simple: the question stops being “can we integrate this studio?” and becomes “do we want this studio in the lobby?” It is a product decision, not a development project.
A casino game aggregator gives an online casino access to many game providers through one integration, one wallet and one contract — instead of one integration, one wallet and one contract per provider.
Without an aggregator: 40 studios means 40 integrations, 40 sets of credentials, 40 certification cycles, 40 invoices and 40 reconciliation reports every month.
With an aggregator: 150+ studios means one integration, one set of credentials, one certification, one invoice and one report — and adding studio 151 is a configuration change, not a sprint.
The catalogue
What is inside a casino game aggregator catalogue
Aggregation is only useful if the catalogue covers everything a lobby has to fill. IGP carries all six verticals that a modern online casino needs, from the studios that drive volume to the regional specialists that make a market work.
Slots and Megaways
The bulk of the catalogue and the bulk of the GGR. Classic three-reel, video slots, Megaways, cluster pays, hold-and-win and bonus-buy mechanics from tier-1 studios and from the boutique providers that players hunt for by name.
Live dealer casino
Roulette, blackjack, baccarat, sic bo, dragon tiger and game-show formats streamed from licensed studios, including native-language tables for specific markets and branded environments where the studio supports them.
Crash and fast games
The category that built LatAm, India and Central Asia: Aviator-style multipliers, plinko, mines, dice, wheels and instant-win formats with low session cost, social mechanics and very high repeat frequency.
Table and card games
RNG roulette, blackjack, baccarat, poker variants, video poker and casual card formats. Cheap to run, expected by every player, and the quiet backbone of a lobby that has to look complete on day one.
Bingo, keno and lottery
Video bingo for Brazil and Latin America, keno and number games for Asia, lottery-style draws and scratch cards. Categories that most operators ignore until a market refuses to convert without them.
Virtuals and specialty
Virtual sports, fishing games, arcade titles and skill-style formats. The long tail that lets one catalogue serve markets with very different ideas of what a casino is supposed to contain.
An operator running a single brand rarely needs all six at launch. An operator running several brands, or one brand across several markets, always does — and the cost of discovering that mid-year is a new integration project per missing vertical. Aggregation is insurance against a roadmap you have not written yet.
The comparison
Aggregator, game provider and casino platform: what the terms mean
These three words are used interchangeably in supplier marketing and they describe three completely different things. Getting them wrong is how operators end up buying the same capability twice.
| Role | What it actually supplies | What it does not do | You need |
|---|---|---|---|
| Game provider (studio) | Builds and certifies its own games — maths, art, sound, RTP configurations, jurisdiction versions. Sells access to its own titles only. | Does not carry anyone else’s games, does not run your wallet, does not operate your casino. | As many as your players ask for |
| Casino game aggregator | Holds signed agreements with many studios and re-publishes all of them through one API, one wallet protocol and one report. Handles certification, currency, jurisdiction filtering and support. | Does not build the games, does not hold your licence, does not provide your player account system, payments or CRM. | One |
| Casino platform (PAM) | Player accounts, KYC, payments, bonusing, CRM, back office, responsible gaming controls and the lobby your players actually see. | Does not supply content. Every platform still needs games plugged into it. | One |
The clean mental model: the platform is the casino, the aggregator is the content layer, the studios are the content. A platform with no aggregator is an empty casino. An aggregator with no platform is a catalogue nobody can play. Most operators buy both, and the two integrate with each other exactly once.
A complication worth naming: many platforms bundle a content layer, and many aggregators resell platform access. That is convenient at launch and expensive later, because it welds your content to your platform. If you may ever change platform — and most operators do — keep the content contract separate so the catalogue moves with you instead of being rebuilt.
The mechanics
How a casino game aggregator works, step by step
Aggregation sounds abstract until you follow a single spin through it. Here is what happens between a player pressing the button and the money landing in your report.
One set of credentials, one endpoint
You receive an operator ID, a secret key and a sandbox URL. Your platform integrates against that one endpoint. Nothing in your codebase ever refers to an individual studio — studios are data, not code, which is the entire point of the design.
The game list is pulled, not hardcoded
Your platform calls the catalogue endpoint and receives every title you are entitled to, with the metadata a lobby needs: provider, category, RTP, volatility, supported currencies, mobile support, jurisdiction availability, demo support, thumbnails and a stable game ID. New studios appear in that response automatically.
A launch request opens the session
The player clicks a game. Your platform asks the aggregator for a launch URL, passing the player token, currency, language, return URL and device type. The aggregator resolves which studio owns the title, opens the session with that studio and hands back one URL to load in an iframe or a webview.
Every bet and win hits one wallet
From that point the studio talks to the aggregator, and the aggregator talks to your wallet through a single set of callbacks — balance, debit, credit, rollback. Whether the round belongs to a live blackjack table or a crash game, the message arrives in one format. This is the one-balance model: the player has a single balance across all 150+ providers and never moves funds between studios.
Round closure and reconciliation are normalised
Studios close rounds differently — some settle instantly, some hold a round open across free spins, some send deferred wins hours later. The aggregator absorbs that and gives you consistent round states, so your finance team reconciles against one ledger instead of 150 exports in 150 shapes.
Adding a studio is a switch, not a sprint
When you want a new provider, it is enabled on your account. Your next catalogue call returns their games and they run through the same wallet you already certified. No new integration, no new contract, no new certification, no release.
The real cost
Aggregator vs. integrating studios yourself
Direct integration is not wrong — large operators run direct deals with their top five studios for commercial reasons, and that is sound. It stops being sound around studio six, because the cost of a direct integration is not the integration. It is everything that happens afterwards, forever.
A single direct connection means a commercial negotiation, a technical integration, a certification cycle per jurisdiction, a support channel, a monthly invoice, a reconciliation process and an upgrade obligation every time that studio changes its protocol. Multiply by forty and you have a content operations department that produces no games.
The aggregator model collapses that into one of each. The engineering cost of your 150th provider is identical to the cost of your first: zero.
| Per 40 providers | Direct | Aggregator |
|---|---|---|
| Contracts to sign | 40 | 1 |
| Technical integrations | 40 | 1 |
| Wallet certifications | 40 | 1 |
| Monthly invoices | 40 | 1 |
| Reconciliation reports | 40 | 1 |
| Support channels | 40 | 1 |
| Cost of adding no. 41 | Full project | A toggle |
| Time to first game live | Months | Weeks |
The comparison assumes a mid-size operator with in-house development. For a white-label or start-up brand the direct route is usually not available at all — most tier-1 studios will not open a direct commercial conversation below a volume threshold, and aggregation is the only way to carry them.
One integration, one balance
Every provider behind a single connection
The commercial argument for aggregation is catalogue size. The operational argument — the one that decides whether your team enjoys the next two years — is that all of it runs on one connection and one balance.
One wallet, every studio
The player’s balance is the same balance in a Pragmatic slot, an Evolution table and a crash game. No transfers, no per-provider sub-accounts, no “insufficient funds” on a wallet the player did not know existed.
One session protocol
Launch, bet, win, rollback and round close are the same messages regardless of who built the game. Your engineers debug one flow, not one hundred and fifty.
One reporting schema
Bets, wins, GGR, rounds and player activity in one structure, per game, per provider, per currency, per day — exportable and reconcilable without normalising six different CSV dialects by hand.
One currency layer
Fiat, crypto and virtual-coin economies handled in the same place, with conversion and rounding rules applied consistently so a studio that only supports EUR still works for a player betting in BRL.
One jurisdiction filter
Game availability by market is configuration, not code. Titles a studio has not cleared for a jurisdiction simply do not appear in the catalogue response for players in that market.
One support line
When a round hangs at 02:00, there is one place to escalate and one party accountable for resolving it — instead of a studio and a platform pointing at each other while the player waits.
After launch
Why one catalogue is not one lobby
Access to 18,000 titles solves the supply problem and creates a curation problem. No player has ever scrolled 18,000 games, and a lobby that simply dumps the full catalogue converts worse than a lobby with 400 well-chosen ones.
The catalogue is the raw material. What turns it into revenue is the part that happens after integration:
- Market-appropriate selection. A Brazilian lobby that leads with video bingo and crash outperforms the same lobby leading with European video slots — and the reverse is equally true in Germany.
- Metadata you can merchandise on. Volatility, RTP band, mechanic, theme, release date and provider are what let you build “high volatility”, “new this week” and “Megaways” rows automatically instead of hand-curating them.
- Performance data per title. Rounds, unique players, average bet and GGR per game tell you which of the 18,000 deserve a position on the first screen this month.
- A release rhythm. Studios ship weekly. A lobby that surfaces new titles on a schedule gives returning players a reason to open the app on a Tuesday.
- Ruthless removal. Games that produce nothing after a fair trial come out. Lobby real estate is finite and a dead row costs you the row underneath it.
An aggregator that only hands over a game list has done half the job. The half that matters is the data and the guidance that tell you what to do with it.
Across the operators we supply, a lobby that performs usually runs on 300–600 active titles out of a catalogue of eighteen thousand — with the rest available for campaigns, market tests and seasonal rotation.
The top 50 games routinely produce more than half of casino GGR. Finding which 50 they are for your players is the work. The catalogue simply guarantees the right 50 are available to be found.
The practical rule: launch narrow, measure weekly, rotate monthly, and keep the full catalogue one toggle away for the moment a market or a campaign needs something you do not currently carry.
Market coverage
Any currency, any market your players are in
Catalogue and currency are the same problem seen from two angles. A studio that does not support the currency your players deposit in is not really in your catalogue, and a market that wants a category you do not carry is not really a market you serve.
| Region | What converts | Currency and payment reality |
|---|---|---|
| Latin America | Crash and fast games, video bingo, football-themed slots, live roulette with Portuguese and Spanish dealers | BRL, MXN, CLP, PEN, ARS — high-frequency, low-stake sessions; rounding rules matter more than they do anywhere else |
| Europe | Video slots, Megaways, bonus-buy mechanics where permitted, live blackjack and roulette | EUR, GBP, PLN, SEK, NOK — plus per-jurisdiction content restrictions that have to be enforced at catalogue level |
| Asia | Fishing games, live baccarat and sic bo, keno and number games, localised slot themes | Local currencies and heavy crypto usage; low-denomination handling and fast session load are decisive |
| Africa | Crash games, aviator-style multipliers, simple slots, virtual sports alongside betting | Mobile-money-driven, very low average stake, bandwidth-sensitive — lightweight games outperform heavy ones |
| North America (sweepstakes) | Slots and casual formats adapted to a dual-currency model | Gold-coin and sweeps-coin economies rather than fiat balances, with a distinct and fast-moving regulatory picture |
| Crypto-first brands | Crash, provably-fair-style formats, high-volatility slots | BTC, ETH, USDT and stablecoins with micro-denomination betting and instant settlement expectations |
All of it runs through the same integration. Currency is a parameter on the launch call, not a new connection — which is what makes launching a second market a commercial decision rather than another development cycle.
Due diligence
How to choose a casino game aggregator
Every aggregator claims a large catalogue and a fast integration. The questions below separate the ones that will still be easy to work with in year two.
Ask for the game list as a file, not a logo wall
A logo wall proves nothing. A machine-readable list — provider, title, category, RTP, volatility, currencies, jurisdictions, mobile support — proves the integration exists and lets you check for the studios your players actually search for by name.
Check which studios are live, not “coming soon”
Catalogues routinely list providers that are signed but not yet technically available. Ask which titles you could launch this week, and which are on a roadmap with no date attached.
Test the sandbox before you sign
You should be able to get keys, pull a catalogue and open a real game session in a test environment early in the conversation. An aggregator that cannot hand you a sandbox quickly will not be quick about anything else.
Read the wallet documentation carefully
Balance, debit, credit and rollback are where integrations go wrong. Look for idempotency handling, clear timeout behaviour, defined rollback semantics and an explicit answer on what happens to an open round if your platform is unreachable for ninety seconds.
Confirm jurisdiction filtering is enforced server-side
If blocking restricted titles in a given market is left to your lobby code, the compliance risk is yours. It should be enforced in the catalogue response and at session launch.
Understand the reporting granularity
Per-game, per-provider, per-currency, per-day, with round-level detail available on request. Anything coarser makes it impossible to tell which titles earn their lobby position.
Ask how new studios are released
The answer should be “we enable it and it appears in your catalogue call”. If it involves a release on your side, you have bought a directory, not an aggregator.
Find out who answers at 02:00
A hanging round is a player complaint within minutes and a chargeback within days. Ask for the escalation path, the response target and who owns resolution when the fault sits with a studio rather than the aggregator.
Who this is for
Operators a casino game aggregator suits
New casino brands
Launching with a credible lobby on day one. A brand with forty recognisable titles and no tier-1 studios reads as unfinished to players who compare it with the site they already use.
Established operators adding scale
Already running direct deals with a handful of studios and tired of the marginal cost of every additional one. Aggregation sits alongside direct contracts rather than replacing them.
White-label and turnkey platforms
Supplying content to many brands from one integration, with per-brand catalogue configuration so each operator gets a different lobby out of the same connection.
Sweepstakes and social casinos
Dual-currency economies that need the same content pipeline as a real-money brand, with the coin model handled at the wallet layer. See the sweepstakes game aggregator page for how that model differs.
Crypto casinos
Micro-denomination betting, instant settlement expectations and a player base that judges a site by whether it carries the specific crash game they came for.
Operators entering a new market
Where the existing catalogue simply does not contain what the new market plays — and the alternative is a separate integration project per territory.
Getting live
What integration actually takes
The honest version, with no rounding down. Most operators reach production in two to four weeks; the variable is almost never the aggregator side.
Week one — connect
Sandbox credentials are issued, your team reads the wallet specification and implements the four callbacks. In parallel you pull the catalogue endpoint and map the metadata into your own lobby model. Most teams have a game launching in test within a few days.
Week two — certify the wallet
We run the wallet test suite against your endpoint: balance checks, debits, credits, duplicate messages, rollbacks, timeouts and concurrent sessions. This is where the real time goes, and it is worth going slowly — a wallet bug found here is free, and the same bug found in production is a reconciliation dispute.
Week three — curate and configure
Choose the launch selection, set currency and jurisdiction rules, build the lobby rows, and check that restricted titles genuinely disappear for a test player in each restricted market. Bonus and free-round mechanics are configured here if you intend to use them.
Week four — go live and watch
Production keys, a controlled ramp, and then the part that never ends: reading per-game performance weekly and rotating the lobby against it. The integration is finished in week four. The merchandising work starts there.
In our experience the schedule slips for one reason far more often than any other: the operator’s wallet is not ready to be certified when the sandbox is issued. Building the four callbacks before kick-off removes most of the risk from the timeline.
FAQ
Casino game aggregator — common questions
A casino game aggregator is a supplier that has already integrated and contracted many individual game studios, and gives an online casino access to all of them through a single API, a single wallet and a single commercial agreement. The operator integrates once and receives the whole catalogue instead of negotiating and building a connection for every provider separately.
A game provider — a studio such as Pragmatic Play, Evolution or Play’n GO — builds and certifies its own games and sells access to its own titles only. An aggregator builds no games; it carries many studios and re-publishes them through one normalised integration. You typically work with one aggregator and, through it, with many providers.
A casino platform, or PAM, supplies player accounts, KYC, payments, bonusing, CRM and the back office. It contains no games. An aggregator supplies the games and no player management. Almost every operator needs both, and the two are integrated with each other once.
IGP carries more than 18,000 certified titles from over 150 game providers, covering slots, live dealer, crash and fast games, table and card games, bingo, keno, lottery formats and virtual sports. The realistic figure that matters, though, is how many of those you should put in your lobby — usually a few hundred, selected for your market.
Two to four weeks is typical from sandbox credentials to production for a team with an existing platform and available developers. The catalogue and launch calls are usually working within days; wallet certification is where the schedule is decided. Operators who build the four wallet callbacks before kick-off tend to land at the fast end of that range.
Yes. That is the core of the model. Every studio in the catalogue settles bets and wins against your wallet through one set of callbacks, so the player has a single balance across all 150+ providers. There are no per-provider sub-wallets and no transfers between studios.
It is enabled on your account and the studio’s games appear in your next catalogue call. There is no new integration, no new contract, no new certification and no release on your side. The engineering cost of your 150th provider is the same as the cost of your first.
Yes, and larger operators often do for their top few studios where the volume justifies a direct commercial relationship. Aggregation and direct integration coexist comfortably — the aggregator covers the long tail and the studios you cannot economically integrate one by one.
Currency is a parameter on the session launch call rather than a separate integration, covering major fiat currencies, Latin American and Asian local currencies, and crypto including BTC, ETH and stablecoins. Content availability is filtered per jurisdiction so restricted titles do not appear for players in markets where the studio has not cleared them.
You need whatever authorisation your target markets require of you as the operator — an aggregator supplies content, it does not carry your operating permissions. Studios also restrict titles by jurisdiction, and those restrictions are enforced in the catalogue regardless of what your own licence allows. This page is general information and not legal advice; take specialist counsel for the markets you intend to serve.
Bets, wins, GGR, round counts and player activity broken down by game, provider, currency and day, in one schema across every studio. That granularity is what lets you judge which titles earn their position in the lobby instead of guessing.
Yes. White-label and multi-brand operators run one technical integration with per-brand catalogue configuration, so each brand shows a different selection, a different currency set and different jurisdiction rules out of the same connection.
Free rounds and provider-side bonus mechanics are supported for the studios that offer them, configured through the same integration. Support varies by studio because the feature is built by the studio, not the aggregator — the available list is part of the catalogue metadata.
They describe the same thing from two directions. “Casino game aggregator” names the commercial relationship — one supplier, many studios. “Aggregation platform API” names the technical surface through which that relationship is delivered: the catalogue, launch and wallet endpoints. Our casino game API page covers the technical side in detail.
The content pipeline is the same; the economy is not. Sweepstakes brands run a dual-currency model with a promotional coin and a redeemable coin rather than a fiat balance, which changes wallet handling, reporting and which studios will make their titles available. The sweepstakes game aggregator page covers that model and its current regulatory picture.
See the full catalogue before you decide
Tell us the markets you serve and the categories you need, and we will send the current game list as a file — provider, title, category, RTP, volatility, currencies and jurisdictions — plus sandbox credentials so your team can open a real session this week.
Request the game list
