Bet Share

The Bet Share module is a centralized hub for sharing and discovering bets within Virtual Stadium. It allows users to view all shared bets, contribute new ones, and revisit their previously shared bets. This feature enhances community engagement and provides social betting experiences.

#Overview

The Bet Share module enables:

• Bet Discovery - Browse bets shared by other community members
• Bet Sharing - Share your own bets with the community
• Bet History - Access your previously shared bets
• Social Interaction - Engage with other bettors around shared bets

This module requires adapter integration to function properly and provide betting data.

The bet-share picker loads the user's placed tickets via the adapter tickets endpoint. The same contract powers Central Hub share-betslip screens. The widget auto-detects the delivery mode from the first response:

• Non-paginated — you call callback with the full tickets array; everything renders immediately.
• Paginated — you call callback with the first batch (pageSize, hasMore); the widget fires onAction ticketsFetchMore when it needs the next page. Central Hub uses the same adapter contract.

See Adapter integration and Ticket pagination below.

#Adapter Integration

The Bet Share feature requires adapter integration to function properly. See the appropriate adapter type based on your integration needs:

• Custom Adapter Implementation
• Hosted Adapter Configuration

#Activating the Copy Bet Button

To enable the copy bet functionality in the shared bets, you must first integrate and configure the Copy Bet feature. For detailed implementation instructions, see the Copy Bet Feature Documentation.

#Ticket pagination

When your adapter signals paginated mode (pageSize or hasMore on the first tickets callback), the widget fires onAction with type ticketsFetchMore when it needs the next page. You load the next page from your backend and call the stored callback from the initial tickets() call with { newTickets, ... } — the widget does not invoke tickets() again and never calls callback itself.

For adapter implementation details and copy-pasteable examples, see:

• Tickets Function reference — flow diagrams for both options
• Adapter Tickets Endpoint Example — Track B — step-by-step paginated tutorial

Non-paginated integrations (full list in one callback) do not require ticketsFetchMore handling. See Track A.

#Tracking Actions

The Bet Share module triggers various actions that can be handled through the onAction callback function for analytics, pagination, and user behavior monitoring.

#BetslipShareListOpen

Triggered when a user opens the bet share list interface.

type string required

Action type: "BetslipShareListOpen".

data object required

Action data containing channel information.

data.channelId string required

Unique identifier of the chat channel.

#BetslipShareListClose

Triggered when a user closes the bet share list interface.

type string required

Action type: "BetslipShareListClose".

data object required

Action data with scope information.

data.channelId string required

Unique identifier of the chat channel.

data.scope string required

Scope identifier: "chat:betshare:list".

#BetslipShareListBack

Triggered when a user clicks the back button within the bet share interface.

type string required

Action type: "BetslipShareListBack".

data object required

Action data containing channel information.

data.channelId string required

Unique identifier of the chat channel.

#BetslipShareListDisabled

Triggered when a user attempts to open bet share but the feature is disabled.

type string required

Action type: "BetslipShareListDisabled".

data object required

Action data containing channel information.

data.channelId string required

Unique identifier of the chat channel.

#ticketsFetchMore

Triggered when the bet-share picker needs the next page of tickets. Only fired when your adapter returned pageSize or hasMore: true on the initial tickets callback (paginated mode).

type string required

Action type: "ticketsFetchMore".

data object optional

data.cursor string optional

Opaque cursor from the previous TicketResponseV2 nextCursor field. Pass it to your backend to fetch the next batch, then call the stored callback with { newTickets, hasMore?, nextCursor? }.

Handling Bet Share Actions:

// Configure onAction callback to handle bet share events
SIR('addWidget', '#virtual-stadium-container', 'virtualStadium', {

#Customization

shareNewBetButtonPosition 'top' | 'bottom' optional

Controls position of the "Share New Bet" button. Default is 'top'.

Share New Bet Button Position Configuration:

// Configure the position of the share new bet button
SIR('addWidget', '#virtual-stadium-container', 'virtualStadium', {
    jwt: 'your-jwt-token',
    channelId: 'your-channel-id',
    shareNewBetButtonPosition: 'bottom' // or 'top'
});