Implementing the Flash Bet Adapter Endpoints

#Intended Audience

• Developers implementing a custom adapter for Virtual Stadium
• Integrators managing real-time adapter communication between widgets and backend systems

#Goals

By completing this tutorial, you will:

• Understand the multi-step real-time flow of Flash Bet using modern adapter endpoints
• Implement the mandatory matchEventSuggestedSelection endpoint to receive live match events and suggest potential bets
• Implement either the market or eventMarkets endpoint to return localized markets/odds data
• Manage real-time odds updates, deactivations, and suspension states (e.g., during "bet stops") using active callbacks

#Prerequisites

Before implementing the Flash Bet-related endpoints, ensure you have:

• An active Sportradar Entity ID (srEntityId) managed and configured in your channel through the Moderation UI
• Access to the Adapter Types documentation for detailed references

#Overview

To fully support the Flash Bet UX, your custom adapter object implements:

1. matchEventSuggestedSelection (required) — Translates incoming match incidents (like goals, bookings, or tennis points) into potential market or outcome selections.
2. Either market or eventMarkets (required, mutually exclusive) — Supplies the active selections, outcome naming, and current odds to the Flash Bet UI, and provides the mechanism to push real-time status updates (like suspending or deactivating a selection to trigger a temporary suspension).

#Tutorial Steps

#Step 1: Register Your Adapter

Start by registering your adapter object using the global SIR function. Ensure only one adapter is registered per page load.

const adapter = {
    endpoints: {
        // Endpoints will go here
    }
};

SIR('registerAdapter', adapter);

#Step 2: Implement matchEventSuggestedSelection

Add the matchEventSuggestedSelection endpoint to suggestion list. This endpoint receives the incident's metadata via args and returns structured market selections.

const adapter = {
    endpoints: {
        matchEventSuggestedSelection: (args, callback) => {
            // args example:

#Step 3: Implement Market-fetch (Choose One)

The selections returned in Step 2 are resolved and rendered using either the market endpoint or the eventMarkets endpoint. Do not implement both. Choose based on your API capability and layout:

• Option A (market + availableMarketsForEvent): Implement this if your API serves market data and odds based on specific market/selection IDs (and specifiers), allowing subscription to individual markets.
• Option B (eventMarkets): Implement this if your API only serves market data and odds on an event level, returning all markets for the entire event ID in a single payload.

#Option A: Implement market

Choose this option if your system's API allows fetching and subscribing to updates by specific market/selection IDs.

const marketCallbaks = {};

const adapter = {
    endpoints: {
        market: (args, callback)

#Option B: Implement eventMarkets

Choose this option to supply and update markets for the entire match fixture collectively.

const eventMarketsCallbacks = {};

const adapter = {
    endpoints: {
        eventMarkets: (args, callback) => {
            // args example:

#Step 4: Handle Real-Time Suspensions & Bet Stops

If a match incident occurs that pauses play (like a goal revision or court medical timeout) right before outcomes resolve, you should suspend the active Flash Bet to prevent users from placing invalid bets.

By default, the suspension is held in the UI for 65 seconds (configurable in your Moderation UI settings). To trigger this state, execute your active endpoint callback with an updated market status.

#Example: Push Suspension Update (Using Market Callback)

// Retreive active callback saved during step 3 Option A
const key = "sr:match:12345:202:setnr=1";
const activeCallback = marketCallbaks[key];

if (activeCallback) {
    // Notify widget that the market is suspended
    activeCallback(undefined, {
        market: {
            id: "202",
            name: "Next Game Winner - Set 1"

#Example: Push Deactivation Update (Counts down but disables clicking)

If you wish to keep the flash bet Timer active but temporarily lock outcomes from being clicked, update outcome status parameters to "deactivated" or set the market status to "deactivated".

if (activeCallback) {
    activeCallback(undefined, {
        market: {
            id: "202",
            name: "Next Game Winner - Set 1",
            status: "deactivated", // Countdown stays active, outcomes disabled
            outcomes: [
                { id: "1", name: "Player A", status:

#Response Formatting Specifications

For reference, inspect the type definitions inside your Adapter API reference:

#MatchEventSuggestedSelectionResponse

{
  "selections": [
    {
      "event": "sr:match:12345",
      "market": "202",
      "specifiers": "setnr=1",
      "type": "uf"
    }
  ]
}

#Next Steps

• Check the Adapter API Types documentation for robust schema definitions
• Review the frontend configuration options in the Flash Bet Widget Guide to customize display duration timers