Skip to content

Reports (Beta)

Reports are part of the integration responsible for synchronizing partner user bets with the Kero database. With this data, Kero team can analyze market statistics and improve the product. Below is a proposal for how this should be implemented on the partner’s side so that Kero can fetch all the required data.

  1. Prepare data according to “Report Data Specification” (see bellow)

  2. Connect to Kafka and send a bets reports via messages. Recommendation: Send data per game after markets were resolved.

Please use classic Kafka setup with the following configuration parameters:

Port: 9092
Bootstrap server: (ask support)
Username: (ask support for credentials)
Password: (ask support for credentials)
Protocol: SASL_SSL
Mechanism: PLAIN
Topic: (for dev `"demo.feed.bets"`)
Message Format: JSON
Key: Generated UUID
Required Headers:
- `partner`: name of the integration partner (e.g., KERO)
Heartbeat: Not required on your side — internal Kafka health is managed by client libraries.
FieldTypeRequiredDescription
kero_market_idstringKero UUID of the market
user_answerstringOption selected by the user. Example: answer_d
amountintegerBet amount.
profitstringProfit from bet (negative if "LOSE").
bet_idstringUnique bet ID
bet_created_utcstringTimestamp when a bet was created. Example: 2025-01-25T02:29:07Z
resolve_statusstringOutcome of the bet. Enum: "WIN", "LOSE", "CANCELED"
oddsstringAmerican format odds
probstringSelected option probability
user_idstringPartner user ID
user_namestringPartner user name
bet_typestringBet type. Enum: "SINGLE", "PARLAY"
parlay_idstringRequired for parlays
parlay_logicstringHow amount is handled for parlays. Enum: "exact", "divide"
market_namestringMarket name
selection_namestringSelected option name
currencystringCurrency code (ISO-4217)