Tournament Bet Insights widget displays AI-powered betting insights and recommendations across multiple matches within a tournament, league, or season. The widget analyzes betting patterns, historical data, and statistical trends to highlight valuable betting opportunities from upcoming matches in the specified competition. It aggregates insights from multiple events to help users identify the most promising betting opportunities across an entire tournament or league, making it ideal for overview pages, tournament hubs, and league standings sections. The widget offers the same flexible integration modes and card layout variants as the match-level Bet Insights widget, including inline display for dedicated sections or button-triggered modal for compact placements.
Unified odds feed (UOF) mapping required
This widget requires Sportradar Unified Odds Feed (UOF) identifiers to correctly match insights to your offering and odds. If your platform does not use UOF IDs you will need to map UOF identifiers to your own market/outcome IDs. Mapping UOF to proprietary identifiers is complex and is difficult to achieve full coverage across all markets and specifier variants — expect limited support.
Warning — this widget isn't suited with declarative integration
This widget requires the onItemClick callback to communicate user interactions with your application. Because HTML declarative integration cannot provide callback functions, the declarative method is not suited for this widget — use the JavaScript/programmatic integration shown in the examples below.
For implementation guidance, example adapter implementations, and the adapter endpoint contract required by this widget, see the Adapter overview. It explains how to choose between Generic-Sportradar, custom-mapping, or self-hosted adapters and includes sample payloads you can adapt.
warning
Betting insights rely on Sportradar's Unified Odds Feed (UOF) market and outcome identifiers. You must map those identifiers to your application's market/outcome IDs. While simple market mapping can be achieved for common markets, achieving complete coverage across all markets and variants is difficult.
All of the following parameters from Bet Insights are also supported:
Expanded Table
note
minOdds, maxOdds, and testMarkets are available on only and are supported by Tournament Bet Insights.
Integration Process
This section outlines the process required to integrate the Bet Insights widget into your platform.
Communication Channel Setup
Your sales contact person will initiate a shared communication channel via Slack invite to facilitate real-time collaboration between teams. This channel serves as the primary medium for answering questions, exchanging required information, and providing ongoing integration support.
Technical Kickoff Meeting
Your sales contact person will organize a kickoff meeting with your technical team and Sportradar's integration team. This meeting serves as the formal start of the technical integration process and ensures both teams are aligned on requirements, timelines, and next steps. During the kickoff the teams will decide the adapter implementation type — this is important because Sportradar needs to confirm whether we have access to your odds and you can use generic adapter or if your platform uses Unified Odds Feed (UOF) identifiers. If your platform does not use UOF IDs, you may need to implement a custom adapter on your side; that decision can affect timeline, required effort, and the level of market coverage achievable.
Properties do not always transfer from the above table directly into integration code. Properties must be transformed differently for each integration method:
JavaScript/Programmatic Integration
Property names remain unchanged in camelCase
Properties become members of the 4th parameter object in SIR() call
Example: cardVariant: "compact"
info
In javascript integration, the properties go into an object which is passed as the 4th argument of the call ti SIR() function. Please see Global SIR API
HTML/Declarative Integration
Convert camelCase to lowercase with dashes, e.g. cardVariant becomes card-variant
Add data-sr- prefix
Example: cardVariant →
To run this widget you must provision an adapter that supplies match and market data. The best adapter type depends on how your data is structured and delivered. During onboarding our team will review your data, recommend the optimal adapter, and assist with configuration.
Replace <CLIENT_ID> and <DATA_SOURCE> with the values provided during onboarding (for example client id: client1, data source: spider). In code use adapterDataSource: 'spider' and https://widgets.sir.sportradar.com/client1/widgetloader.
The examples in this section demonstrate the bet slip integration pattern using the Bet Insights widget. The pattern is identical for Tournament Bet Insights — adapt the identifier prop (uniqueTournamentId, seasonId, tournamentId, or matchId) and widget key (betInsights.tournament) in your integration.
Handling user selections
The following example shows how to respond when a user clicks an insight card. The onItemClick callback receives the click target and the outcome data, which you can use to build a selection object and push it into your bet slip. Walk through the highlighted sections to understand each part of the flow.
The following snippet brings together the widgetloader, the adapter's betSlipSelection endpoint, and the onItemClick handler specifically for Tournament Bet Insights.
Important
Replace <CLIENT_ID> and <DATA_SOURCE> with the values provided during onboarding (for example client id: client1, data source: spider). In code use adapterDataSource: 'spider' and https://widgets.sir.sportradar.com/client1/widgetloader.
html
<script> (function(a,b
Widget Behavior
The following describes how the Bet Insights widget reacts to data, market and outcome state
changes, and user interactions. It covers visibility rules, how selections and bet-slip events
are handled, and how adapter updates or error states affect the widget UI and available actions.
Flow Diagram
The diagram above illustrates the complete data lifecycle for the Bet Insights widget, which runs in the end user's browser and coordinates data between Sportradar and your systems:
Insights Generation (1): AI/ML models in the Sportradar API produce market insights and deliver them to the widget.
Market Data Resolution (2–4): The widget requests available markets and odds from your Client API via the Adapter; the Adapter transforms and returns matching available market data.
User Interaction (5–7): The end user clicks an outcome (5); the widget invokes the configured onItemClick handler (6) so your app can add the selection to the bet slip (7).
State Synchronization (8–9): Your Adapter exposes a betSlipSelection subscription/callback that the widget registers; when your bet slip changes the Adapter invokes the callback (8–9) and the widget updates its UI to reflect current selections.
Market status
When market status is set to suspended, the widget disables that market's outcomes and displays the label "temporary unavailable" in place of odds, indicating the market is temporarily not available for betting.
Widget comes with pre-existing styling but can be customized by applying custom CSS properties to its different HTML elements. The widget's custom class selectors and supported CSS properties are listed below. Note that all custom classes must be nested within the .sr-bb.sr-<WIDGET_NAME> selector class. This ensures that the custom styles only apply to that widget and not to other elements on the page.
Choose the right identifier based on your page context:
javascript
// League overview page — use uniqueTournamentId for all seasons{ uniqueTournamentId: 135 }// Specific season page — use seasonId{ seasonId: 132030 }// Tournament page — use tournamentId for a specific instance{ tournamentId: 30 }// Match detail page — use matchId to show insights from other matches in the same tournament{ matchId: 61591316 }
Use numberOfCards and numberOfEvents to balance coverage and focus:
javascript
// Focused: many insights from few matches{ uniqueTournamentId: 135, numberOfEvents: 3, // Only next 3 matches numberOfCards: 12 // Up to 12 insights total}// Broad: fewer insights spread across more matches{ uniqueTournamentId: 135, numberOfEvents: 10, // Up to 10 matches numberOfCards: 10 // Only top 10 insights}
Sportradar match identifier. Shows insights for matches in the same tournament as this match. At least one of matchId, tournamentId, uniqueTournamentId, or seasonId is required. See Getting Identifiers
tournamentId
number
Conditional
-
Sportradar tournament identifier. Shows insights from all matches in this specific tournament. At least one of the four ID props is required
uniqueTournamentId
number
Conditional
-
Sportradar unique tournament identifier. Shows insights from matches across all seasons of this tournament. At least one of the four ID props is required
seasonId
number
Conditional
-
Sportradar season identifier. Shows insights from all matches in this specific season. At least one of the four ID props is required
numberOfCards
number
No
15
Maximum number of insight cards to display. Must be between 1 and 20
numberOfEvents
number
No
-
Maximum number of distinct matches to include insights from. Must be between 1 and 20. When unset, insights from all available matches are included
Property
Type
Default
Description
integration
string
"inline"
Widget integration mode: "inline" or "button"
cardsLayout
string
"vertical"
Layout direction for insight cards: "vertical" or "horizontal"
Position of outcome name relative to odds: "top", "bottom". Only applicable with cardVariant='compact', cardVariant='button', and cardVariant='buttonFooter'
outcomeButtonPosition
string
"bottom"
Position of call-to-action button in card: "top", "bottom". Not applicable with cardVariant='button' and cardVariant='buttonFooter'
widgetTitle
string|false
"Tournament Bet Insights"
Title displayed in widget header or button label. Set to false to hide
widgetIcon
string|false
Default icon
URL of custom icon image. Set to false to hide
disableWidgetHeader
boolean
false
When true, hides widget header in inline mode
enableCollapse
boolean
true
When true, allows collapsing widget content in inline mode. Only applicable when disableWidgetHeader=false
startCollapsed
boolean
false
When true and enableCollapse is true, widget starts collapsed
modalPosition
string
"left"
Direction modal opens in button integration: "left", "right", "bottom"
modalMaxHeight
number|string
-
Maximum height of modal content. Allowed units: %, px, vh. Only applicable with integration='button' and cardsLayout='vertical'
isMobile
boolean
false
When true, opens pop-up at viewport bottom edge, full width (only with integration='button')
ignoreAdapterValues
boolean
false
When true, uses Sportradar standard names instead of adapter-provided translations
capitalizeMarketNameAndOutput
boolean
false
When true, capitalizes first letter of market and outcome names
onItemClick
function
-
Callback triggered when insight card or outcome is clicked. Receives event and outcome data for bet slip integration
<script> (function(a,b,c,d,e,f,g,h,i){a[e]||(i=a[e]=function(){(a[e].q=a[e].q||[]).push(arguments)},i.l=1*new Date,i.o=f, g=b.createElement(c),h=b.getElementsByTagName(c)[0],g.async=1,g.src=d,g.setAttribute("n",e),h.parentNode.insertBefore(g,h) )})(window,document,"script","https://widgets.sir.sportradar.com/<CLIENT_ID>/widgetloader","SIR", { language: 'en', adapterDataSource: '<DATA_SOURCE>' }); const widgetProps = { // Required identifiers — provide at least one uniqueTournamentId: 135, // tournamentId: 30, // seasonId: 132030, // matchId: 61591316, // Configuration integration: "button", modalPosition: "right", numberOfCards: 15, // ... Optional: Additional customization props (see API Reference) }; SIR('addWidget', '#tournament-bet-insights', 'betInsights.tournament', widgetProps);</script><div id="tournament-bet-insights"></div>
javascript
let betSlipChangeCallback = undefined; let betSlipState = { // Simplified bet slip integration for demonstration purposes selection: [], }; // Called on user interactions function onItemClick(target, data) { if (target === 'externalOutcome') { // When user clicks an outcome on an insight card // Construct a selection object in the shape your bet slip integration expects. // The widget provides external IDs via data.externalEvent, data.externalMarket, // and data.externalOutcome — map them to your own format below. const bet = { type: 'uf', event: `${data.externalEvent.id}`, market: `${data.externalMarket.id}`, outcome: `${data.externalOutcome.id}` }; if (data.externalMarket.specifier && data.externalMarket.specifier.value) { bet.specifiers = `${data.externalMarket.specifier.value}`; } // Add the new selection betSlipState = { selection: [...betSlipState.selection, bet] }; // Notify the adapter so the widget reflects the updated bet slip state betSlipChangeCallback && betSlipChangeCallback(betSlipState); } } const widgetProps = { matchId: 61591316, onItemClick: onItemClick, // ... Additional customization props (see API Reference) }; SIR('addWidget', '#bet-insights', 'betInsights', widgetProps);
Bet Slip Integration
The following example shows how to connect the widget to your bet slip so it always reflects the punter's current selections. The adapter's betSlipSelection endpoint keeps the widget in sync, and onItemClick lets you act when the user clicks an outcome card. Walk through the highlighted sections to understand each part of the flow.
We recommend revalidating each selection and refreshing odds when adding them to the bet slip — or at minimum revalidating selections and odds immediately before accepting a bet — to ensure markets are still available and the odds presented to the user are up to date.
The following example brings together the widgetloader, the adapter's betSlipSelection endpoint, and the onItemClick handler into a single ready-to-use snippet. Replace the placeholder values.
Important
Replace <CLIENT_ID> and <DATA_SOURCE> with the values provided during onboarding (for example client id: client1, data source: spider). In code use adapterDataSource: 'spider' and https://widgets.sir.sportradar.com/client1/widgetloader.
html
<script> (function(a,b,c,d,e,f,g,h,i){a[e]||(i=a[e]=function(){(a[e].q=a[e].q||[]).push(arguments)},i.l=1*new Date,i.o=f, g=b.createElement(c),h=b.getElementsByTagName(c)[0],g.async=1,g.src=d,g.setAttribute("n",e),h.parentNode.insertBefore(g,h) )})(window,document,"script","https://widgets.sir.sportradar.com/<CLIENT_ID>/widgetloader","SIR", { language: 'en', adapterDataSource: '<DATA_SOURCE>' }); // Tracks the current bet slip selections in the format the widget expects. // In production, replace this with your own bet slip store / state manager. let betSlipState = { selection: [] }; let notifyWidget = null; const adapter = { endpoints: { betSlipSelection: (args, callback) => { // Store the callback so we can notify the widget whenever selections change. notifyWidget = callback; // Push the current state immediately so the widget is in sync on load. callback(undefined, betSlipState); return () => { notifyWidget = null; }; }, }, }; // Register the adapter once on page load — USE ONLY ONE APPROPRIATE TO YOUR ADAPTER TYPE SIR('registerAdapter', adapter); // Generic-Sportradar & Self-hosted // SIR('registerAdapter', '<HOSTED_ADAPTER_NAME>', adapter); // Custom-mapping function onItemClick(args) { if (args.type === 'addSelectionsToBetSlip') { // Map the widget's selections to the format the betSlipSelection endpoint expects. const newSelections = args.data.selections.map((sel) => ({ type: 'uf', event: sel.eventId, // e.g., "sr:match:12345" market: sel.marketId, // e.g., "38" specifiers: sel.specifiers, // e.g., "goalNr=1" (optional) outcome: sel.outcomeId, // e.g., "sr:player:1050245" odds: { type: 'eu', value: sel.odds }, })); betSlipState = { selection: [...betSlipState.selection, ...newSelections], }; // Notify the widget so it immediately highlights the newly selected outcomes. notifyWidget && notifyWidget(undefined, betSlipState); } } const widgetProps = { matchId: 61591316, onItemClick: onItemClick, // ... Additional customization props (see API Reference) }; SIR('addWidget', '#bet-insights', 'betInsights', widgetProps);</script><div id="bet-insights"></div>
If a market or outcome has any status other than active (for example: suspended or cancelled), the widget will hide that market to avoid showing stale or unavailable betting options.
