CasinoQuery / Data & API docs
Know the data you’re building with.
Explore the fields, history, and coverage behind CasinoQuery. Compare recent records, daily summaries, game metadata, and player analytics. Download synthetic samples to explore the fields before planning your integration.
This reference covers selected fields checked against our stored data schema in September 2026. It is not an exhaustive dataset export or a production API specification. Contact us to confirm the fields, endpoints, authentication, and limits for your integration.
Explore the sample records.
| source | game_name | game_provider | bet_amount | payout | multiplier | currency | win_timestamp | created_at |
|---|---|---|---|---|---|---|---|---|
| stake | Example Slot A | Example Studio | 2 | 49 | 24.5 | USD | 2026-09-01T12:00:00Z | 2026-09-01T12:00:02Z |
| gamdom | Example Slot B | Example Studio | 1 | 0 | 0 | USD | 2026-09-01T12:00:01Z | 2026-09-01T12:00:03Z |
| duelbits | Example Slot C | null | 5 | 15 | 3 | USD | 2026-09-01T12:00:02Z | 2026-09-01T12:00:04Z |
| duel | Example Casino Game | null | 10 | 20 | 2 | USD | 2026-09-01T12:00:03Z | 2026-09-01T12:00:05Z |
/samples/player-analytics.jsonDownload JSON ↓JSON/samples/slot-activity.jsonDownload JSON ↓JSON/samples/game-history.jsonDownload JSON ↓JSON/samples/game-catalog.jsonDownload JSON ↓These files are fixed synthetic examples, not live API responses. Player usernames and figures in these files are fictional. The published coverage figures come from a separate verified collection snapshot.
Player analytics
830,248 casino-specific player records, counted exactly on September 8, 2026 · 00:29 UTC. Explore source usernames, captured activity, game preferences, and recorded results.
| Field | Type | Meaning |
|---|---|---|
user_name | string | Stored casino username; scoped to the source, not a verified real-world identity. Hidden identities must be suppressed in public displays. |
source | string | Casino source associated with this player record. |
total_bets | integer | null | Stored count of captured bets attributed to the profile. |
total_wins | integer | null | Stored win counter; source and aggregation rules must be confirmed before interpreting it as a win rate. |
total_wagered | number | null | Stored wager total. This table has no currency column; denomination and normalization require validation before monetary comparisons. |
total_payout | number | null | Stored payout total, subject to the same denomination and coverage limits. |
total_profit | number | null | Stored calculated profit field from captured activity, not a verified account balance or lifetime profit. |
biggest_payout | number | null | Largest stored payout in the captured profile history. |
biggest_multiplier | number | null | Largest stored payout multiplier. |
biggest_win_game | string | null | Game associated with the biggest stored payout. |
biggest_multi_game | string | null | Game associated with the biggest stored multiplier. |
favorite_game | string | null | Game recorded as the profile's most-played game in captured activity. |
favorite_game_count | integer | null | Stored play count for the favorite game. |
first_seen | datetime | null | First observed activity, not the account creation date. |
last_seen | datetime | null | Last observed activity, not a guarantee that the player is online. |
last_updated | datetime | null | Timestamp when the stored profile summary was refreshed. |
Count is an exact dated table-row snapshot, not distinct people or a count of publicly identifiable players. Matching usernames across casinos does not establish that they belong to the same person. Captured totals are partial observations. Monetary normalization and identity visibility rules must be confirmed for delivery. All downloadable profiles and figures are synthetic.
Recent casino activity
Captured bet records across slots and other casino games, with event details retained for approximately seven days.
| Field | Type | Meaning |
|---|---|---|
source | string | Casino source identifier. |
game_name | string | Game name reported or normalized during collection. |
game_provider | string | null | Provider label, when available. |
bet_amount | number | Recorded wager amount; interpret alongside currency. |
payout | number | Recorded return, including zero-payout events. |
multiplier | number | Recorded payout multiplier. |
currency | string | null | Stored denomination; original-unit normalization must be confirmed for delivery. |
win_timestamp | datetime | Stored event timestamp in UTC; field name also applies to zero-payout records. |
created_at | datetime | Database ingestion timestamp in UTC. |
Captured activity is not a complete record of every bet at each casino. Canonical catalog matching varies by record; the sample omits player identifiers.
Daily game history
Historical game and day summaries representing more than 318 million captured bets, beginning February 2, 2026.
| Field | Type | Meaning |
|---|---|---|
game_name | string | Game label associated with the daily summary. |
game_slug | string | Normalized game key used for daily aggregation. |
stat_date | date | Day covered by this summary. |
total_bets | integer | Number of captured events represented by this row. |
total_wins | integer | Events whose multiplier is at least 1, including break-even results. |
total_wagered | number | Sum of stored wager amounts; currency treatment must be agreed before comparisons. |
total_payout | number | Sum of stored return amounts. |
avg_multiplier | number | Mean multiplier among events with multiplier at least 1. |
max_multiplier | number | Highest observed multiplier that day. |
wins_100x | integer | Count of recorded events with multiplier at least 100. |
Daily summaries combine many events into one game/day row. Source counts and top-five events are also retained; this lightweight sample shows a subset of fields. Historical sums are stored counters, not a fresh event-level deduplication audit.
The daily history also preserves bets_by_source, a map of casino identifiers to counts, and top_wins, up to five selected events per game/day. Multiplier bands range from 2x through 1000x. All-time summaries are built from the same daily history; the two totals should not be added together.
Slot & game catalog
9,168 catalog records with game identity, provider references, and available game specifications.
| Field | Type | Meaning |
|---|---|---|
name | string | Catalog game name. |
slug | string | Catalog game slug. |
rtp_base | number | null | Catalog RTP percentage; variants and source settings can differ. |
volatility | string | null | Available volatility classification. |
max_win | number | null | Listed maximum win multiplier, when known. |
release_date | date | null | Catalog release date, when known. |
Catalog specifications have not been independently verified for every game. Field completeness varies; sample null values illustrate unavailable metadata. Provider references, features, RTP variants and further metadata can be scoped for delivery.
What the numbers mean.
How much data is captured each day and minute?
The September 7, 2026 snapshot at 16:08 UTC counted 3,995,831 events with timestamps in the preceding 24 hours. Dividing by 1,440 gives an average of approximately 2,775 per minute. These are observed casino bet records across slots and other games; the figure is not a slot-only count or a guaranteed collection rate.
Are all 21 casinos currently reporting?
All 21 listed sources had stored daily history and incoming records in the 15-minute check ending September 7, 2026 at 16:16 UTC. That check recorded 46,489 incoming events. Coverage changes over time, and a reporting source does not imply every game or bet on that site is visible. Stake US and Shuffle US are separate sources.
How is 318 million bets calculated?
The exact sum of daily bet counters was 318,398,244 across 1,157,275 game/day summaries covering February 2–September 6, 2026. The all-time cache returned the same total. These are overlapping views of the same captured history, not additional bets.
How many players are in the dataset?
An exact count of the player summary table returned 830,248 records on September 8, 2026 · 00:29 UTC. These are casino-specific records, not deduplicated people across casinos. The count includes stored records whose identity visibility has not been audited. Bet records carry a hidden-user flag; a populated username alone does not establish that it should be shown publicly. Public profile examples use fictional usernames and figures.
What happens after seven days?
Detailed live records are retained for approximately seven days. Older activity survives in compact daily game summaries, including source counts and selected top events. Historical access does not mean a complete export of every original individual bet.
Which examples use real data?
The homepage live preview shows up to six real recent records and refreshes every 20 seconds while visible. It includes game identity, casino, multiplier, timestamp, and available artwork; it excludes player details and monetary amounts. The game showcase uses a fixed real-data extract with its capture date displayed. Documentation downloads and public player profiles are synthetic examples.
Are the collection totals live counters?
No. Collection volume, historical totals, player count, and source coverage are dated, verified snapshots. They do not refresh automatically. Source availability, game matching, currency handling, and field completeness are confirmed for each commercial delivery.
Work with a sample today.
Download the recent activity JSON and save it as slot-activity.json. Run either example below from the same folder. These examples read a local file; no API key is needed.
// Node.js · run from the folder containing slot-activity.json
const fs = await import('node:fs/promises');
const sample = JSON.parse(
await fs.readFile('slot-activity.json', 'utf8')
);
console.log({ synthetic: sample.synthetic, records: sample.data });Reads the downloaded synthetic sample. No network request or API key.
Download slot-activity.json ↓Request API access.
Tell us about your product, preferred plan, and expected usage. We’ll confirm the available datasets, pricing, limits, and integration requirements with you directly.
Access details and authentication instructions are provided when your integration is arranged. These downloadable sample files are not a production API contract.
Contact us for API access ↗