Data Overview
This page describes the data Scout stores about your players' activity on the platform, and the data that stays on your side. Use it to plan your data-vault or regulatory reporting feed: everything Scout holds can be joined to your own wallet and KYC records using the bet ID and the user ID.
Data We Store
1. Money Movements
Every call Scout makes to your wallet is logged. This log is the core of any data-vault feed, because each row lines up with a debit or credit in your wallet.
| Field | Description |
|---|---|
| Type | buyin, buyin_refund, payout, repayout (a corrected payout after results change), rake, rake_refund |
| Bet ID | The entry (fantasy team) ID — bet.uid in the callbacks |
| Pool ID | The contest (tournament) ID — pool.uid in the callbacks |
| Amount and currency | The amount charged or paid, plus a converted amount and currency for cross-currency contests |
| User ID and client | The user ID (user.uid) and the client (white-label) ID |
| Ticket ID | Set when the entry was paid with a free ticket or voucher rather than cash |
| Admin ID | Set when a staff member made a manual adjustment |
| Outcome | A failed flag and the error text if the wallet call failed, callback_at (when your wallet confirmed it) and created_at |
2. Contest (Pool) Definition
- Name, sport, and the leagues or seasons and fixtures involved.
- Entry fee and currency, with per-operator fees and multipliers for shared pools.
- Rake % or cut %, guaranteed prize pool, and freeroll flag.
- Maximum entries in total and per user.
- Prize distribution type and the full prize ladder (prize per rank).
- Registration or lock time, and when the winner was declared.
- Status: open, running, settled or cancelled.
3. Pool Totals
- Number of entries, number of unique players, actual prize pool, and the guaranteed amount.
- A log of each change to the entry count, showing how the pool built up over time.
4. Player Entries
- Entry ID, user, contest, and when the entry was created and last updated.
- The lineup or picks, together with a timestamped record of every lineup change. This is useful evidence that nothing changed after the lock.
5. Outcome and Settlement
- Points, final rank and the payout per entry, broken down by prize scope (overall, a single gameweek, and so on).
- How the score was built: the player stats used in scoring, plus any bonuses.
6. Free Entries and Promotions
- The free-entry value and currency, its type (marketing, satellite, qualifier), expiry date, who approved it, and which contest it was used in.
7. Player Data
- Only what your JWT gives us: the user ID (
idclaim) and username (usernameclaim), both required in the token (see Authentication). - Alongside these, Scout records the player's country, locale, operator (white label), and when the player was first and last seen.
Data We Do Not Store
The following stays on your side, so it belongs in your own data-vault feed, not Scout's:
- Real identity and KYC.
- Wallet balance, deposits and withdrawals.
- Responsible-gambling limits and self-exclusion.
- The player's IP address, device and session data.
Example: One Entry, Joined Up
This is how a single entry looks when the records above are joined together:
contest 81234 · Premier League GW8 · entry fee 5.00 EUR · rake 10% · 1,432 entries · pool 6,444.00 EUR
entry 5_550_001 · user uid "op-77812" · created 2026-10-03T14:02Z · lineup edited 2× (last 2026-10-04T10:58Z, lock 11:00Z)
txn buyin -5.00 EUR 2026-10-03T14:02:01Z callback_at 14:02:01Z
txn rake (0.50 EUR) recorded with the buy-in
settled 2026-10-06T22:10Z · points 312.5 · rank 14/1432
txn payout +40.00 EUR 2026-10-06T22:11Z callback_at 22:11:03ZJoining With Your Records
Join Scout's data to your own wallet and KYC records using:
- Bet ID — the entry ID, sent as
bet.uidin every Fantasy Sports callback. - User ID — sent as
user.uidin the callbacks; it is theidclaim from the JWT you issue for the player.