Skip to content

Bet Reports

General information

The Bet Reports API provides CSV feeds with reporting data about bets, sport events and tournaments.
For bets, each row represents a single selection (odd) within a bet, so a single bet can produce multiple rows.

Use cases

  • Revenue and margin analytics: aggregate stake, winSum, refundSum by sport, tournament, market, or bet type.
  • Customer behaviour: analyse how players use different bet types (type), system sizes (systemSizes), and bonus mechanics (isFreebet, isInsurance) over time.
  • Product performance: compare performance of markets (oddMarketId / oddMarketName) and selections (oddId / oddName / oddRatio) across sports and tournaments.

Typical integration pattern

1. Initial sync

  • Define the period you need and split it into time windows.
  • For each window, call the API with from and to and save the response to your storage. Depending on the period length, you may need one or more requests.

Important

Do not use windows larger than 3 days (prefer smaller windows).

2. Sync actual data

  • Sync data periodically using small windows (e.g. every 5 minutes). For each run:
    • set from = previous to
    • set to = from + window size
    • process in order and store the last to for the next run
  • The filter uses the updated_at field: each time an entity is updated, it will be returned in the window whose from/to range includes its new updated_at value, so the same entity can appear in different windows as it changes.

Swagger