Turnkeyxgaming

Guide · Definitions

What is the difference between a casino API and an aggregator?

The terms get used interchangeably, which confuses buying decisions. A casino API is an interface; an aggregator is a business that offers one API in front of many studios. This guide untangles them, along with game providers.

6 min readUpdated By the Turnkeyxgaming team

Three terms, three different things

TermWhat it isExample
Casino APIAny interface for listing, launching and settling gamesA single studio's own API, or an aggregator's
Game provider (studio)A company that builds and certifies gamesA slot studio with its own API for its own titles
Game aggregatorA company offering one API in front of many studiosTurnkeyxgaming: 300+ studios behind one contract

Casino game aggregator vs game provider

A game provider gives you its own games through its own API, which is a deep relationship with one catalogue. A casino game aggregator gives you many providers' games through one API, which is breadth with one relationship. Large operators often use both: direct deals with their top two or three studios for commercial reasons, and an aggregator for everything else.

The technical difference is smaller than the commercial one. Both expose catalogue, launch and wallet calls. The aggregator adds translation across studios, per-market certification records and one reconciliation file. The direct integration comparison works through the costs.

Which one do you need?

If you need breadth quickly, use an aggregator. If one studio makes up most of your revenue and you have the engineering capacity, a direct deal can improve margins on that studio. Most brands start with an aggregator, then add direct deals once they know their players' preferences.

Three questions that stop a sales call using one word for three products

Ask whose games are behind the endpoint. If the answer is a single studio, you are buying that studio's casino API, which is a real interface and a narrow catalogue. If the answer is a list of studios you do not have to integrate one by one, you are talking to an aggregator, and the next question is which of those studios are actually certified for your licence. If the answer adds registration, the cashier and a bonus engine, those are platform products sold beside the API. Price them as separate lines.

The wallet call will look similar in all three conversations, which is why the words collapse. Catalogue, launch and settle are the shared shape. Translation across protocols, a per-market certification record and one reconciliation file are the aggregator's additions. A studio does not need the translation because it only speaks its own protocol. Write down which of those extras you are being charged for before you compare two proposals that both said 'API'.

Compare the studios behind the endpoint, not the noun

Two quotes can both say casino API and describe a single studio, a hundred studios, or a hosted casino. List the studios, the markets they are cleared for, and whether the player account is in the price. The noun will not do that work.

Three proposals, one noun, one integration team

A mid-size operator ran a tender and received three documents headed casino API. The first was an aggregator: 300+ studios behind one wallet contract. The second was a studio selling its own catalogue, with its own launch format and its own callback shape. The third was a platform vendor whose API included games as one line beside the player account, cashier and bonus engine. All three were priced as a percentage, and two were within a tenth of a point of each other.

The engineering lead estimated the work from the wallet contract. Proposal one needed one adapter. Proposal two needed that adapter plus the studio's own protocol and a second reconciliation file. Proposal three needed the vendor's callback shape, documented but not negotiable, and assumed the player account lived in the vendor's system. That last clause was the real difference: the cheapest-looking proposal would have moved the player ledger out of the operator's platform, which is a migration rather than an integration. The white label comparison covers how far that can go.

Six weeks in, the tender's mistake surfaced. Finance had compared three rates as though they bought the same thing, and one of them included a cashier the operator already ran. Re-scoring took an afternoon once each proposal was broken into the same lines. Do that before the shortlist, not after the contract is drafted.

Break each proposal into the same lines

LineAggregatorSingle studioPlatform with games
Studios behind the endpointEvery studio carried, subject to certificationOne catalogue, plus whatever you integrate yourselfWhichever studios the vendor resells
Callback shapeOne contract, translated per studioThe studio's ownThe platform's own
Player accountStays in your platformStays in your platformOften moves to the vendor
ReconciliationOne file across studiosOne file per studioBundled with platform reporting
Counterparty if a title is withdrawnThe aggregatorThe studioThe platform vendor
What you still buildLobby, KYC, cashierLobby, KYC, cashier and an adapterConfiguration and migration

FAQ

Questions operators ask

Is every casino API an aggregator?

No. A studio's own API is a casino API but not an aggregator, because it only offers that studio's games.

Is a game provider the same company as the aggregator?

Sometimes one group owns both, and they are still different contracts. The provider made the games. The aggregator, if you are buying that, is the single integration in front of many providers. Ask which contract you are signing.

Can we call our own direct studio connections an aggregator?

Only if you actually normalise them into one contract, one wallet path and one report. A folder of separate studio APIs is several casino APIs. The word aggregator describes the layer that made them one.

Is a white label the same as an aggregator?

No. An aggregator supplies games and a wallet contract; a white label supplies an operation, often including the licence the brand trades under. They overlap only in putting games in front of players. The casino API vs white label comparison sets the two contracts side by side.

If our supplier resells another aggregator's studios, does it matter?

It matters when something breaks. Ask which studios arrive through a third party, who holds the studio contract, and whether those titles appear in the same reconciliation file. A resold studio with a different retry or reporting shape behaves like a second integration you did not plan for.

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.

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
  • Product · Game aggregationAggregatorOne aggregator contract for licensed operators: 40,000+ games from 300+ studios at 13% of GGR in Asia and 16% elsewhere.Read
  • ComparisonAggregator vs directDirect integration is a separate project for each studio. An aggregator is one connection placed in front of many studios.Read
  • GlossaryGame aggregatorA game aggregator links an operator to many studios through one integration, one contract, one shared wallet and one reconciliation file.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.

Telegram @turnkeyxhub WhatsApp Email Contact form