The Dream API

One row per game for the window: handle (total staked), GGR, wager count, unique players, average bet, theoretical RTP as configured, actual RTP ((handle − GGR) ÷ handle × 100), and hold %. This is the whole casino-manager daily view in one call — which games earn, which run hot (actual RTP above theoretical), which are dead inventory.

An array of days, each with handle, GGR, NGR (GGR − bonus cost), deposits, withdrawals, net cash, actives, split by vertical. Feeds every line chart in a dashboard without walking raw wagers.

The same wager rows with a cursor: { rows: [...], nextCursor }. Makes every downstream report incremental and cheap instead of day-walking.

Ranked players with net win/loss from the house's perspective, handle, wager count, verticals played, VIP tier and agent. The daily 'who is beating us / who is feeding us' sheet every book runs on.

A 7×24 matrix of activity counts — staffing the cage/support desk, timing campaign sends, spotting bot-like off-hour patterns.

A matrix: each signup month × months-since-signup → % of the cohort still active and their GGR. The canonical LTV/retention view (standard in GiG Core / EveryMatrix).

Per bonus program: amount granted, converted to cash, forfeited, outstanding (current liability), completion rate, and NGR impact — whether each promotion pays for itself.

Subscriptions binding a report template + period (daily/weekly/monthly) + recipients; the platform emails the rendered report. The 'Monday 8am P&L in the owner's inbox' feature.

Each wager row gains fundSource: 'cash' | 'bonus' | 'free_spin' (and the split stake when one bet draws on both wallets). Finance can then publish cash hold without the bonus contamination caveat, and the bonus ledger can compute true wagering-requirement progress per instance.

Profile + balances + limits + KYC state + last login/IP + N-day totals (handle, net, wager count, deposits, withdrawals) + recent ledger in one response. Cuts the support screen from 11 round-trips to 1.

Per game/league for one player: handle, net, wager count, actual RTP experienced. Drives VIP-host conversations and RG interventions ('this player is chasing losses on one high-volatility slot').

The stored limit set + effective-from timestamps (limit increases must be delayed 24h–7d per most regulations; decreases apply instantly). GET twin returns current limits + pending changes.

The exclusion record: kind, term, start, registry it was propagated to; while active the platform must refuse logins/deposits and suppress ALL marketing. GET twin lists history.

One row per active exclusion: customerId, kind (SELF|OPERATOR|COOL_OFF), start, end or indefinite, and the registry it was propagated to. A history twin, or an updatedSince cursor, would let it be polled cheaply rather than re-read whole.

0–100 composite plus per-factor breakdown: payment risk (velocity, instruments), fraud signals (device/IP sharing), RG behavior score (loss-chasing, night play, limit hits), AML flags. The triage number every queue sorts by.

Device fingerprints (hashed), user agents, IPs with geo, first/last seen, and WHICH OTHER customerIds share any of them — the multi-account/bonus-abuse graph in one call.

Clusters of accounts sharing identity signals, each with a match confidence and combined bonus cost — the daily bonus-abuse review queue.

A freeze record blocking wagers/withdrawals but preserving login + support contact, with audit trail (who froze, why, when it lifts).

Named segment definitions (rules over deposits, activity, vertical, VIP, dormancy) materialized server-side; /members streams current membership. Feeds campaigns, bulk actions, and stake-factor policies.

A shared, audited note stream per player (author, timestamp, category: support/finance/risk/VIP), readable from every console that talks to the platform.

TEMP_PASSWORD mode: a one-time strong temporary password (returned once, must-change-on-login flag set, all sessions invalidated). LINK modes: a signed, expiring reset link delivered by the chosen channel with delivery status. Every reset lands in the audit log with actor + reason.

Count of sessions/tokens invalidated (web, wrapper sessions, kiosk). Pairs with passwordReset in the compromise runbook.

Event objects: id, league, sport, matchup, start time, status, market count. The backbone every sports report joins against.

For one event: total handle, bet count, average bet, and the split by market (ML/spread/total/props/parlay legs) and by side — where the money is, which side the book needs.

Per open event/market: open handle, worst-case and best-case P&L if each outcome hits, current max-bet, bet delay. Sorted by worst case; this is the trader's morning screen (SoftSwiss/GiG ship exactly this).

All unsettled wagers with risk/toWin, event, market, side, placed-at — feeds liability, early cash-out decisions, and void queues.

The corrected wager + a compensating ledger transaction, with an immutable audit entry (who, why, before/after).

The player's limit multiplier applied to every market max (0.1 = sharp cut to 10%, 2.0 = trusted recreational doubled), plus live-bet delay. GET twin lists all non-default profiles — the 'sharps board'.

Leagues with sport, season dates, default margin target, and per-league handle/GGR rollups for the trailing 30 days.

Every game: id, name, provider, category, THEORETICAL RTP as certified, volatility class, release date, enabled/disabled per brand. The reference table actual-RTP reports compare against.

The updated game status with audit trail — kill-switch for a game paying out anomalously (actual RTP way above theoretical) pending investigation.

Each progressive: current amount, seed, contribution %, last winner + date. Marketing (jackpot tickers) and finance (jackpot liability is a real balance-sheet line) both need it.

Current sessions: customerId, game, stake pace, session length, net position. The live floor-manager view; also an RG trigger source (marathon sessions).

The stored lobby layout per brand with scheduled game releases — an EveryMatrix CasinoEngine-style merchandising control.

Pending items enriched with the player's risk score, KYC state, bonus-abuse flags, lifetime deposits vs withdrawals, and method fees — everything an approver needs on one row.

Per method/PSP: current success rate, average settle time, status, and the cascade order (where a declined transaction retries next). PUT reorders the cascade.

Cases with reason codes, amounts, deadlines and representment status; POST attaches evidence. Feeds a win-rate report per method/PSP.

Per provider/day: platform-ledger total vs PSP-reported settlement, fees, and the itemized diff. The daily 'are we actually being paid' check.

The compensating transaction with linkage to the original, audit-stamped.

Every active hold on the wallet: pending withdrawal requests (id, amount, method, requested-at), bonus-rollover locks, and dispute freezes — plus the derived availableTotal / heldTotal / withdrawable numbers the player-facing wallet should show.

Rule-generated alerts: customer, rule, severity, amount, SoW/SoF request state, case status. POST moves a case through OPEN → INVESTIGATING → CLEARED/SAR_FILED with an immutable trail.

A regulator-format bundle per case: identity, account history, flagged transactions, prior alerts — ready to attach to the FIU filing.

Match results with list, score, and disposition workflow (confirmed false positive / true match → freeze + report).

The complete return dataset for the period: GGR/NGR by vertical and jurisdiction, tax due, new/active/excluded player counts, limit-setting statistics, and the player-funds segregation balance (liabilities vs segregated account).

Every privileged action: actor, operation, target entity, before/after values, IP, timestamp. Immutable, exportable.

Grant records per player with redemption tracking (spins used, winnings converted to bonus balance, expiry). GET twin reports redemption + cost per campaign.

Players flagged by rule: duplicate-cluster membership, bonus-to-deposit ratio outliers, min-rollover-then-withdraw patterns, per-flag evidence. Feeds the duplicates queue and grant blocklists.

A campaign object; GET …/{id}/stats returns delivered/opened/clicked/converted (deposits within attribution window) and per-player suppressions (RG/comm-prefs). Closes the marketing loop.

Tournament definitions (vertical, scoring rule, prize pool, dates) and live leaderboards. POST creates; the platform scores automatically from wager flow.

Mission definitions (rule, reward, active window) + completion counts + per-player progress. Drives the 'quests' retention surface.

A 0–1 churn probability with drivers (deposit frequency decay, session gap growth, net-loss streak) and a recommended intervention (reload offer / VIP call / rest nudge). Batch twin: /api/reports/churnRisk lists the top-risk cohort.

The stored coupon template with every knob above. Redemptions reference the code; the platform enforces sticky-at-withdrawal removal, rollover accrual with per-category game weights, and the max-win cap at cashout time.

The exact wallet strip the player-facing site renders: cash balance, bonus balance with sticky flag (sticky bonus is removed at withdrawal, not cashed), TOTAL remaining rollover in dollars (e.g. "wager $3,120 more to unlock withdrawals"), per-grant breakdown (code, granted, rollover done/required, expiry), and any active max-win caps. One call, one strip.

One row per bonus instance (stable bonusInstanceId, template/coupon code, granted/converted/forfeited/expired amounts, rollover done vs required, timestamps), with the same bonusInstanceId stamped on every wager row and BONUS-family transaction it touches. Turns the bonus ledger from grant-side accounting into a true instance roll-forward.

Brand list (skin domain, markets, currency) and makes brandId a first-class filter on every reporting endpoint.

A server-sent-events stream of platform happenings as they occur — live tickers, instant alert delivery, and incremental warehouse sync (linepros-sync could tail this instead of re-walking days).

Plan definitions (revshare %, CPA trigger, hybrid, negative-carryover policy) and per-affiliate computed earnings per period, with the player-level detail behind each number.

One row per provider: integration model (BetSoft = CWS seamless-wallet ExtSystem callbacks per WagerStreet/docs/betsoft-integration.md; RTG = seamless one-wallet), game-server host, bankId/operator id, connection status, and 24h callback volume. The provider-ops overview panel.

Per callback method (authenticate/balance/betResult/refundBet/bonusRelease/bonusWin/tournament for BetSoft): call volume, average latency, hash failures, idempotent replays served, business-error histogram (300 insufficient funds, 302 unknown refund tx, 500 invalid hash). The alarm feed for the wallet integration.

A diff for the day: provider-reported rounds/amounts vs wallet ledger — orphaned bets (debited, round never finished), unmatched wins, refunds without originals. Anything non-empty becomes a finance ticket.