What is a Casino API? Architecture, callbacks and how operators integrate

A casino API is a REST (and often WebSocket) interface that exposes game catalogue, launch URLs, and wallet callbacks for a portfolio of certified casino games. Operators call the API to render a lobby, generate a per-player launch URL, and answer wallet callbacks (balance, bet, win, rollback) initiated by the games.

When the catalogue covers many studios behind a single API, the provider is called a game aggregator. AS Tech iGaming aggregates 80+ tier-1 studios into one API.

A standard casino API integration has four moving parts:

1. Aggregator API — owned by AS Tech, signs requests with HMAC-SHA256.
2. Operator backend — holds the wallet of record and answers callbacks.
3. Game studio servers — run the actual game logic; never talk to the operator directly.
4. Player frontend — loads the launch URL inside an iframe or new tab.

All money flows through the operator's wallet. Bets are atomic — a failed callback triggers an automatic rollback, so the player's balance is never left in an inconsistent state.

Four callbacks cover 99% of cases:

• balance — return the player's current real-money balance.
• bet — debit the player; must be idempotent on transaction_id.
• win — credit the player; usually paired with the original bet id.
• rollback — reverse a previous bet or win in case of failure.

Each request is HMAC-signed; the operator MUST verify the signature before mutating the wallet.

With AS Tech, the typical timeline is:

• Day 1 — sandbox keys issued, HMAC signing verified.
• Days 2–3 — game-list ingest, launch URL working in iframe.
• Days 4–5 — wallet callbacks implemented and rollback-tested.
• Week 2 — UAT, KYC checks, production keys and go-live.