Home · Products · Game Aggregator

One catalog. One sell API.

House keeps the master catalog. A desk does not integrate each studio on its own. It calls the sell API with its Client ID and launches only the titles house assigned.

GameXora desk with catalog, sessions, wallets, and the commercial ledger

On the catalog

What the aggregator actually runs

One house book for supply. Each desk receives a slice. Player chips stay on the operator wallet.

Lobby control

House enables, features, or hides a title once. Slots, live, table, crash, poker, virtual, and instant win sit in that catalog.

Studios

Provider cost is versioned on the house book. A desk can take one title, a set, or a studio. No new wire per studio.

Sell API

Providers, games, link player, start game. HMAC, an IP allow-list, and a traceId on every hop. Keys never sit in a browser.

Wallet callbacks

Session check, player details, balance, and move funds. Sign the path and treat each transaction id as idempotent.

Chargeable GGR

max(0, bets − wins) on the desk. Reports split by transaction, game, studio, and player. Not a second cut on the player.

Campaigns

Tournaments, prize drops, free spins, and cashback point at assigned titles. The desk sees a campaign only after house turns it on.

Studios

The same catalog, a narrower desk

A studio can be wide on the house book and limited on a Client ID. Ask house which titles belong on the desk.

CQ9 Elbet Endorphina Eurasian Gaming BGaming NetEnt Hacksaw Play’n GO

Open the full provider list and shortlist the studios you want house to assign.

Sell API

Launch in four calls

Open the game in a new tab. Do not iframe it. Keys never sit in a browser.

01
ProvidersGET
/api/v1/casino/providers

Confirms the desk key and lists supply assigned to this Client ID.

02
GamesGET
/api/v1/casino/games

Copy gameId from id or externalId.

03
Link playerPOST
/api/v1/casino/players/link

Map one userId to one live player wallet, then fund it.

04
Start gameGET
/api/v1/casino/games/start

Open location in a new tab. The session stays on GameXora.

FAQ

Catalog, launch, and the wallet

Does each studio need its own integration?

No. House holds the supply connection. A desk lists providers and games through the sell API and starts only what was assigned to its Client ID.

Can two desks launch different titles from the same studio?

Yes. The master catalog can hold the studio while each desk receives its own slice — one title, a set, or the studio.

Where does the player balance live?

On the operator wallet. Callbacks read the balance and move funds for bet, win, and rollback. Chargeable GGR is written on the desk ledger.

How should the game open?

In a new tab, from the location the start call returns. Do not iframe the session. Keys stay on the backend.

Call the sell API

House can issue a sandbox Client ID and a test player so you can link, fund, and start without touching live books.