Skip to main content
All API requests require an API Key passed via the X-API-Key header. Obtain yours at Dashboard → Settings → API Keys.

Event Types

Casino events follow a three-phase lifecycle, all sent to the same endpoint. The Kafka topic is fixed: atlas.events.raw.casino.
All three events are linked by the same bet_id. Send open first, then win or lose when the round settles.

Track Casino Open

Track Casino Win

Track Casino Lose

Request Fields

Envelope Fields (all events)

string
required
Organization identifier.
string
required
Brand identifier.
string
required
Event type: open, win, or lose.
string
Player IP address at round time.
number
Player latitude at round time.
number
Player longitude at round time.
boolean
Marks the event as operator test traffic. When true, the event is accepted (202) but rerouted to an audit-only store — it never appears in analytics, dashboards or risk scoring. Defaults to false when omitted.

Casino Fields

string
required
Your internal user identifier. Must be consistent across all events for the same player.
string
required
Session identifier used to correlate multiple rounds within the same casino session.
string
required
Unique identifier for this game round. Must be the same across open, win, and lose events for the same round.
string
required
ISO 8601 timestamp of when the round happened.
string
Status of the bet round. Mirrors the event field: open, win, or lose. Optional but recommended for downstream ClickHouse consumers.
string
required
Your internal game identifier, or the provider’s game ID. Used for per-game analytics.
string
Optional provider-side game identifier when different from game_ext_id.
string
required
Human-readable game name (e.g., "Gates of Olympus", "Lightning Roulette").
string
required
Game provider name (e.g., "Pragmatic Play", "Evolution", "NetEnt").
string
required
Game category: slot, roulette, blackjack, baccarat, poker, live, virtual, crash.
string
Allowed values: WEB, MOBILE, APP.
number
required
Real-money bet amount. Excludes bonus amounts.
number
Bonus/free-spin bet amount. Tracked separately from real money for GGR calculation.
number
Real-money win amount. 0 for a losing round. Omit for open events.
number
Bonus win amount (wins from bonus bets).
string
required
ISO 4217 currency code (e.g. BRL).
number
Player balance before this round. Used for balance reconciliation.
number
Player balance after this round.
boolean
Indicates whether this bet was a free bet.

GGR Calculation

Atlas calculates GGR from casino events automatically:
Bonus GGR is tracked separately:
For accurate GGR reporting, always separate real-money and bonus amounts. Mixing them inflates GGR and breaks bonus liability tracking.

Batch Casino Events