LMT Golf & Combat

Golf and Combat (MMA) are supported on Live Match Tracker (match.lmtPlus) through dedicated layouts. These variants use entityId instead of matchId and only support a subset of standard LMT properties.

For standard match-based integration, see LMT.

#API Reference

#Required Parameters

• widget-name: match.lmtPlus
• entityId: Required. Full entity string — sr:stage:<id> or golf:stage:<id> for golf, sr:tournament:<id> or mma:event:<id> for combat (MMA). Use golf:stage / mma:event prefixes for IMGA IDs.

Environment Requirements

Technical Requirements:

• JavaScript enabled
• XMLHttpRequest support for data fetching
• CSS3 support for styling and animations

#Properties

Properties below apply to one or both variants as noted.

#Theming

Theming is more limited than on standard LMT. Tab branding uses the same branding object as regular LMT — see Tabs Branding for display options (iconText, icon, text) and Customizing Widgets for the full schema. The main widget area only respects the CSS below. Existing global LMT theming (font, background-color) applies automatically — light/dark mode follows background-color.

#Streaming

When streaming is enabled, the streaming option is shown if the currently displayed hole (Golf) or currently selected fight (Combat) has streaming available. For Golf, when streams are available, the hole selection UI is also shown on the Live tab and at the top level of the Courses tab.

To enable streaming:

1. Pass a jwt prop with "av" scope. See JWT Authentication.
2. Pass a streamToggle prop, e.g. onPitchButton.
3. Ensure stream availability is not suppressed by streamNotAvailableMessage or streamNotAvailableBgImage.

#Integration Examples

#Property Name Transformations

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"

HTML/Declarative Integration

• Convert camelCase to lowercase with dashes, e.g. cardVariant becomes card-variant
• Add data-sr- prefix
• Example: cardVariant → data-sr-card-variant

/* MAIN BACKGROUND COLOR */
.sr-bb {
    background-color: #fff;
}

/* DEFAULT TEXT COLOR */
.sr-bb .srt-base-1 {
    color: #333;
}

/* PRIMARY TEXT COLOR */
.sr-bb .srt-base-1-primary {
    color: red;
}

/* SURFACE BACKGROUND COLOR (golf only) */
.sr-bb .srt-golf-surface {
    background-color: gray;
}

SIR('addWidget', '#sr-widget', 'match.lmtPlus', {
    entityId: 'sr:stage:12345',
    jwt: 'your-jwt-token',
    streamToggle: 'onPitchButton',
    streamMuteVideo: true
});

JavaScript (Programmatic)

Initialize the widget programmatically using the JavaScript API. The widget renders in the specified container element.

(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/sportradar/widgetloader","SIR", {
    language: 'en'
});

SIR('addWidget', '#sr-widget', 'match.lmtPlus', {
    entityId: 'sr:stage:123'
});

<div id="sr-widget"></div>

HTML (Declarative)

Insert the following HTML code at the target widget location. Complex object properties must be passed as JSON-encoded strings.

<div id="sr-widget"
        data-sr-widget="match.lmtPlus"
        data-sr-entity-id="sr:stage:123">
</div>
<script type="application/javascript"
        src="https://widgets.sir.sportradar.com/sportradar/widgetloader"
        async>
</script>