Implementing the Tickets Adapter Endpoint

#Intended Audience

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

#Goals

By completing this tutorial, you will:

• Understand the structure and requirements of the tickets adapter endpoint
• Implement a working tickets endpoint that retrieves and transforms user bet data
• Format bet responses according to the BetShareResponse type specification
• Apply filtering logic to return only relevant tickets to the widget

#Prerequisites

Before implementing the tickets endpoint, ensure you have:

• A backend API or database that stores user bet data
• Familiarity with callback-based request handlers
• Access to the Adapter Types documentation for endpoint specifications

#Overview

The tickets endpoint retrieves a user's bet history and returns it in the BetShareResponse format. This endpoint enables features like bet sharing and bet copying in Virtual Stadium widgets.

The endpoint receives request arguments including the customer ID, optional event filters, and pagination data. Your implementation should:

1. Fetch user bets from your backend system
2. Filter bets based on provided criteria
3. Transform data into the required BetSlip format
4. Return the formatted response via callback

#Tutorial Steps

#Step 1: Register Your Adapter

First, register your adapter with the SIR global function before adding any widgets. Ensure only one adapter is registered per page load.

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

SIR('registerAdapter', adapter);

#Step 2: Implement the Tickets Endpoint

Add the tickets endpoint handler to your adapter. This function receives request arguments and a callback to return results.

const adapter = {
    endpoints: {
        // NOTE: The `tickets` endpoint is one of several adapter endpoints.
        // Implement additional endpoints (event, eventMarkets, availableMarketsForEvent, etc.)
        // as documented in the Adapter Types documentation based on your widget requirements.
        tickets: (args, callback) => {
            // Implementation continues below
        }
    }
};

Request Parameters (args):

• endCustomerId (string) — The user's unique identifier
• events (SelectionEvent[], optional) — Events to filter tickets by
• page (number, optional) — Page number for pagination
• useCashOut (boolean, optional) — Include cash out information

#Step 3: Fetch and Filter Bet Data

Retrieve user bets from your backend system and apply filtering based on request arguments.

tickets: (args, callback) => {
    // Fetch user's bets from your backend API or tickets system
    fetchUserBets(args.endCustomerId, (error, allBets) => {
        if (error) {
            return callback(error);
        }

#Step 4: Transform Data and Return Response

Transform your bet data into the BetSlip format (part of BetShareResponse) and invoke the callback with the formatted response.

tickets: (args, callback) => {
    fetchUserBets(args.endCustomerId, (

#BetSlip Response Format

The response must conform to the BetShareResponse type: { bets: BetSlip[] }

#Next Steps

• Review the Adapter Types documentation for detailed endpoint specifications
• See Getting Started to complete the full adapter integration
• For frontend implementation, see the Copy Bet Button guide to enable users to interact with and copy bets in the UI