Stock Provider

The stock data provider loads Custom Bet offering and odds calculation from Sportradar and enriches market and outcome labels using the same match and translation data as other Sportradar widgets. You do not implement UOF proxy callbacks (getAvailableMarkets, calculate, and similar). The widget handles those calls internally.

Use this path when custom bet is enabled for your bookmaker and you want the smallest integration surface: a match id, a session jwt, and bet slip handling.

#Prerequisites

• Custom Bet widget licensed for your clientId with custom bet coverage for the events you display.
• JWT integration — your RSA public key submitted to Sportradar and published for validation before production tokens are used (prerequisites).
• jwt — short-lived JSON Web Token (RS256) for the logged-in user or session. You sign it on your backend; the widget sends Authorization: Bearer … on every offering and calculation request. See JWT authentication (Stock Provider) for signing and delivery to the page.
• matchId for an event that supports custom bet for your package.
• addToBetSlip in dataProviderConfig — required for every data provider. See addToBetSlip and Handling Selections and Odds.

Service endpoints are supplied through the widget loader client context (defaults are configured for production widgets). If you need non-standard endpoints, coordinate with Sportradar support.

#How It Works

1. On load, the widget requests available selections for the match using matchId and jwt.
2. The widget loads match info, squads where applicable, and translations so market and outcome labels match other Sportradar widgets.
3. When the user changes selections, the widget recalculates odds and updates selectable markets from the Sportradar custom bet service.
4. When the user confirms, addToBetSlip runs on your side for validation and bet slip integration.

#Integration Example

<script>
  (function (a, b, c, d, e, f, g, h, i) {
    a[e] ||
      ((i =

#Configuration Summary

All other widget props (API reference) work the same as with UOF Proxy (display mode, market filters, theming, and so on).

#Compared to UOF Proxy (Deprecated)

Use stock when custom bet is enabled for your bookmaker. If you still use UOF Proxy, see Migrating from UOF Proxy to Stock. Deprecated legacy paths — UOF Proxy (uofProxy) and Data Adapter (custom) — are documented only for existing integrations.

#Troubleshooting

See also Custom Bet troubleshooting.