Flash Bet

#Overview

Flash Bet presents users with betting markets derived from live match events. Each betting market is displayed for a limited duration (default: 20 seconds, configurable by contacting the Sportradar integration team) as a First-In-First-Out (FIFO) queue. Users can quickly place bets on the presented outcomes, enhancing engagement and the overall betting experience.

1. The channel must have a Sportradar entity ID configured in the moderation UI, with the desired events selected. Additionally, the match must be upcoming or live to ensure markets and odds are available.

• How to Add SR Entity ID to Channels

2. When a match event appears in the chat, a suggested betting market is automatically pushed to the Flash Bet queue and served to users.

#Testing

For testing purposes, you can use the "Test Channel" feature in the Moderation UI to simulate match events and observe Flash Bet behavior.

• How to Test Channels

#Setup

#1. Enable Flash Bet

To enable Flash Bet within your Virtual Stadium widget, set the enableFlashBet property to true during widget initialization:

enableFlashBet boolean optional

Enables the Flash Bet functionality.

Enable Flash Bet:

SIR('addWidget', '#sr-vs-widget', 'virtualStadium', {
    enableFlashBet: true,
    // ... other configuration
});

#2. Moderation Setup

For a channel to have Flash Bet functionality, it must have a Sportradar entity id set.

• How to Add SR Entity ID to Channels
• Create Channel API

#3. Adapter Registration

Flash Bet requires adapter registration to function properly. See the appropriate adapter type based on your integration needs:

• Custom Adapter Implementation

#4. Handling Flash Bet Actions

When a user clicks on an outcome within the Flash Bet interface, the widget invokes your onAction callback. Virtual Stadium emits two action types for the same click:

Treat displayed odds as a snapshot only — re-validate the selection and fetch authoritative prices from your platform before placement. See Handling Selections and Odds for the shared selection flow.

onAction (type: string, data: object) => void optional

Callback function triggered when specific events occur in the widget.

Parameters:

type string required

Action type: "FlashBetOutcome" or "addSelectionsToBetSlip".

data ExternalOutcome or V2 selection bag required

For FlashBetOutcome, see ExternalOutcome object below. For addSelectionsToBetSlip, data.selections contains adapter v2 SelectionOutcome entries; optional events and markets bags carry hydrated adapter context.

Handling Flash Bet Actions:

function onAction

#5. External selection IDs (forceExternalSelections)

Set forceExternalSelections: true on the Virtual Stadium widget when your bet slip expects bookmaker (external) selection IDs instead of UF ids. See forceExternalSelections in the quick start for prerequisites.

Flash Bet event identifier: The widget reads relatedCompetitions[].clientId from channel info and sets externalEvent.externalId on the click payload. Configure the channel so the active match entry includes your bookmaker event id:

"relatedCompetitions": [{
  "channelId": "test",
  "srEntityId": "sr:match:71895968",
  "clientId": "thisIsClientId"
}]

The backend may return multiple related competitions; the widget uses the entry matching the active match. The UI handles a single event at a time.

Using external ids when available: For V2 UF selections, when forceExternalSelections is true and a mapper is available (adapter selectionUfToExternal or F3 via adapterDataSource: 'f3'), the widget emits external outcome/market/event ids in callbacks. If mapping is unavailable or fails, the payload uses UF ids (type: 'uf'). Selections that are already external pass through unchanged. V1 adapter integrations keep the previous behavior.

Payload type (on the ExternalOutcome object) is 'uf' or 'external' — not the onAction type string.

#Verified against

Behaviour documented here matches the widgets production branch and MR 15948 (BETS-30613):

#Flash Bet Timer Settings

Flash Bet Timer Settings let you control the timing parameters for flash bets across your organization. These settings determine both how long a flash bet remains visible to users when triggered and the maximum time it will wait if a bet stop occurs.

• Bet Stop Timeout specifies the duration (in seconds, default 65s) that a flash bet is paused when the market enters a "bet stop" state. During this period, the flash bet remains on hold before closing and moving to the next item in the queue if no update is received. If the market reactivates before the timeout ends, the countdown resumes from where it was paused.

• Flash bet timer settings (in seconds, default: 20s) define how long a suggested market is displayed to the user in the Flash Bet module. You can set different durations for channels linked to a match or a tournament with a Sportradar Entity ID, allowing you to tailor the user experience based on event type.

#Data Structures

#ExternalOutcome Object

#Event Object

{
  "id": "sr:match:12345",
  "srEventId": "sr:match:12345",
  "externalId": null
}

#Market Object

#Outcome Object

{
  "id": "4",
  "name": "Player A",
  "odds": "6.00"

{
  "externalEvent": {
    "id": "sr:match:71895968",
    "srEventId": "sr:match:71895968",
    "externalId": "thisIsClientId"
  },
  "externalOutcome": {
    "id": "4",
    "name": "Player A",
    "odds": "6.00",
    "oddsDecimal": 6,
    "status": {
      "isActive": true
    }
  },
  "externalMarket": {
    "id": "202",
    "status": {
      "isActive": true
    },
    "specifier": {
      "value": "setnr=2",
      "displayedValue": "2"
    },
    "name": "2nd set - winner",
    "outcomes": [
      {
        "id": "4",
        "name": "Player A",
        "odds": "6.00",
        "oddsDecimal": 6,
        "status": {
          "isActive": true
        }
      },
      {
        "id": "5",
        "name": "Player B",
        "odds": "1.08",
        "oddsDecimal": 1.08,
        "status": {
          "isActive": true
        }
      }
    ]
  },
  "type": "uf"
}

{
  "id": "202",
  "status": {
    "status": "active"
  },
  "specifier": {
    "value": "setnr=2",
    "displayedValue": "2"
  },
  "name": "2nd set - winner",
  "outcomes": [
    {
      "id": "4",
      "name": "Player A",
      "odds": "6.00",
      "oddsDecimal": 6,
      "status": {
        "isActive": true
      }
    },
    {
      "id": "5",
      "name": "Player B",
      "odds": "1.08",
      "oddsDecimal": 1.08,
      "status": {
        "isActive": true
      }
    }
  ]
}