Get started
Overview
KOI is a remote game server. We run the games and produce every result; your platform keeps the player, the wallet and the money.
How an integration works
A KOI integration has two directions:
| Direction | Who calls | What happens |
|---|---|---|
| Your platform → KOI | You | Open a game session, list your games, query a balance, grant free bets. |
| KOI → your platform | KOI | Signed wallet callbacks debit bets, credit wins, revert bets and read balances. |
The player never sends money to KOI. Each bet is debited by your wallet through a callback, and each win is credited the same way. If your wallet refuses a bet, the bet does not happen.
Key concepts
| Concept | Meaning |
|---|---|
| Partner account | Your KOI account. It owns an access token, four callback URLs and the list of games enabled for you. |
| Access token | Secret used as a Bearer token on every API call and as the key of the callback signature. |
| Player | A player of your platform, identified by the user_id you send. KOI creates it on first launch. |
| Session | A game session opened by request-access. It has a token, a currency, a language and an expiry. |
| Round | One play. Collective games (crash, double) share a round between players; slots open one round per bet. |
| Transaction | A wallet movement: bet, win or rollback. Each one has a unique provider_tx_id. |
Integration models
Operators integrate directly: one partner account, your own wallet. Start with Launch a game and How the wallet works.
Aggregators use the same API on behalf of the brands they serve, routing sessions and callbacks per brand. Read Aggregator integration.
What KOI guarantees
- Results are produced on the server. The game client only displays them.
- Every callback is signed with HMAC SHA-256. See Signature verification.
- Every bet and win carries a unique
provider_tx_id, resent unchanged on retries. See Idempotency & retries.