Platform Terms
| Term | Definition |
|---|---|
| Organization | Your Atlas account. An organization owns one or more brands and has its own users, roles, and billing. |
| Brand | A specific product operated under your organization — typically a domain (e.g., apostas.example.com). All event data is scoped to a brand. |
| API Key | A secret token used to authenticate calls to the Events API. Scoped to a brand. |
| Event | Any trackable action in your platform — bet placed, deposit made, user registered. Events are the raw material of Atlas analytics. |
| Pipeline | The real-time data path: event ingestion → Kafka → processing → analytics. |
| Dead-Letter Queue (DLQ) | A Kafka topic (atlas.events.dlq) that receives events that failed to be published to the primary topic. Used for replay and debugging. |
| Batch | A single API call that contains multiple events (up to 500). More efficient than individual calls for high-volume scenarios. |
iGaming Terms
| Term | Definition |
|---|---|
| Operator | A company licensed to offer sports betting or casino gambling to players. |
| GGR (Gross Gaming Revenue) | Total bets received minus total winnings paid out. The primary revenue metric. |
| NGR (Net Gaming Revenue) | GGR minus bonuses, promotions, and payment fees. The net profit metric. |
| Hold % | The percentage of total bets that the operator retains as revenue. Hold = GGR / Total Bets. |
| Cashout | A feature allowing players to settle a bet before the event ends, receiving a partial payout. |
| Open Bet | A sports bet that has been placed but the event has not yet concluded. |
| Round | A single casino game session (one spin, one hand, one roll). |
| Void Bet | A bet that is cancelled and the stake returned to the player, typically due to event cancellation. |
| Bonus | Free credits or free spins granted to players for promotions. Tracked separately from real-money bets. |
Compliance Terms
| Term | Definition |
|---|---|
| PLD | Prevenção à Lavagem de Dinheiro — Anti-Money Laundering (AML) in Portuguese. Required by Brazilian regulation (Lei 9.613/98). |
| KYC (Know Your Customer) | The process of verifying player identity before allowing withdrawals or high-value bets. |
| COAF | Conselho de Controle de Atividades Financeiras — Brazil’s Financial Intelligence Unit. AML reports are submitted here. |
| Responsible Gambling (RG) | Features that protect players from gambling-related harm: deposit limits, self-exclusion, time limits. |
| Self-Exclusion | A player-requested feature to be blocked from gambling for a defined period or permanently. |
| Cooling-Off Period | A mandatory or voluntary pause from gambling activity, shorter than full self-exclusion. |
Event Types
| Event Type | Domain | Description |
|---|---|---|
register | User | Player creates a new account |
update | User | Player updates their profile |
deposit | Transaction | Player adds funds to their account |
withdraw | Transaction | Player requests a payout |
open | Casino/Sport | Player opens a casino round or places a sports bet |
win | Casino/Sport | Casino round or sports ticket settles as a win |
lose | Casino/Sport | Casino round or sports ticket settles as a loss |
cashout | Sport | Player exercises cashout on an open bet |
HTTP Status Codes (Atlas-Specific)
| Code | Meaning |
|---|---|
202 Accepted | Event(s) accepted and published to Kafka. Async processing in progress. |
207 Multi-Status | Batch request partially succeeded. Check failed count in response. |
400 Bad Request | Request payload is malformed or missing required fields. |
401 Unauthorized | Missing or invalid API key / JWT token. |
422 Unprocessable Entity | Payload is well-formed but fails business validation rules. |
429 Too Many Requests | Rate limit exceeded. Back off and retry. |
502 Bad Gateway | Kafka publish failure. Event was routed to DLQ. |