emBET Quick Start Guide

emBET provides a seamless “watch and bet” experience, helping to generate more revenue from your live streams while enhancing viewer retention

Introduction

This Quick Start Guide is the primary starting point for integrating the emBET SDK into your application or website.

This guide...

• …explains how to get started with the emBET integration

• …outlines the key decisions and responsibilities on your side

• …helps you understand the available integration options

• …prepares you for deeper technical implementation using the SDK documentation

SDK Integration

Depending on your LCO integration, the emBET SDK integration process varies.

• Option A: If you have integrated LCO via AV-API = you must follow the following two steps for the emBET SDK integration

• Option B: If you have integrated LCO via LMT = the emBET SDK is pre-integrated, so proceed to Step 3, "Odds Delivery"

Enable the emBET overlay

The emBET SDK is the technical foundation of the integration. It is required to render the emBET overlay and to enable all interactive functionalities within your application or website.

The SDK must be added to your project and initialized as part of your application lifecycle. Once integrated, the SDK allows emBET to display overlays, receive data, and react to user interactions.

The SDK can be integrated using standard distribution methods:

• Package Manager (recommended) or

• CDN

Platform‑specific setup steps, initialization details, and configuration options are covered in the emBET SDK documentation.

Show the overlay

The emBET overlay is rendered inside a predefined UI container or component that is provided by your application.

You are responsible for adding this container to your UI at the location where the overlay should be placed. The emBET SDK is already aware of the supported container or component on each platform and will automatically render the overlay content inside it.

In most integrations, the overlay is placed on top of a live video stream.

Recommendation: The emBET overlay is optimized for a full-screen live streaming experience on mobile, but it is not limited to this use case.

Odds Delivery

emBET supports three integration models for odds delivery. The model determines ownership of market selection, data flow, and integration effort.

• Option A: Sportradar delivers Sportradar odds (UOF) directly to the emBET SDK

• Option B: Sportradar integrates your odds feed (via API) and delivers it to the emBET SDK

• Option C: You, the Client, deliver your odds feed directly to the emBET SDK

Option A: Sportradar delivers Sportradar odds (UOF) directly to the emBET SDK

In this model, Sportradar delivers the odds (via UOF) automatically to the emBET SDK.

• The effort of delivering UOF to your emBET SDK is fully supported by Sportradar

  • Requires 1 day on our end

Option B: Sportradar integrates your odds feed (via API) and delivers it to the emBET SDK

In this model, you are responsible for providing us with API access to your own odds feed. Sportradar will ingest the data and deliver it to the emBET SDK.

For this model, we will provide you with guidelines and requirements for the Client's API integration process.

• The effort of providing your odds API falls on you, the Client.

  • Requires an estimated 1-2 days on your end

• The effort of integrating the API feed and delivering it to emBET falls on Sportradar.

  • Requires 8 weeks on our end

Option C: You, the Client, deliver your odds feed directly to the emBET SDK

In this model, you are responsible for delivering odds data directly to the emBET SDK.

You select the markets and send odds updates in the required format.

The emBET SDK provides functionality for passing data to the SDK. You are fully in charge of providing and updating odds, betting markets, outcomes, etc.

• The effort of delivering your odds directly to the emBET SDK falls on you, the Client.

  • Requires an estimated 3-5 days on your end

Betslip Integration

The SDK supports two betslip integration models to fit different platform architectures and product strategies.

• Option A: Use your own betslip

• Option B: Use our embedded betslip

⚠️ Even if you use our betslip (option B), bet placement remains fully your responsibility and must be handled by your bet/ticket engine. emBET only acts as a UI layer, communicating user interactions to you and providing bet settlement feedback.

Option A: Use your own betslip

In this model, your application manages the full bet placement experience through your own betslip.

When a user initiates a bet from the emBET overlay, the emBET SDK notifies your application. You then take over by displaying your own betslip and handling the bet placement flow.

When using your own betslip, bet placement events (markets, stakes, outcomes) must be shared with us to enable product analytics and performance tracking.

Recommendation: For a smooth "watch and bet" user experience, we recommend that you place your betslip strictly on top of the emBET overlay. The emBET overlay is designed to match your branding guidelines, so moving from the emBET overlay to your betslip should be a seamless experience for the punter.

• The effort of integrating and slightly adapting your own betslip falls on you, the Client.

  • Requires an estimated 3-4 days on your end, with our support for testing

Option B: Use our embedded betslip

In this model, emBET provides an embedded betslip UI.

When a user places a bet, the emBET SDK forwards the bet request to your bet/ticket engine. You remain responsible for validating the bet, accepting or rejecting it, and providing us with bet settlement feedback (placed or rejected) so we can inform the end user within our betslip UI.

• The effort of responding to bet requests from the emBET SDK to your ticket engine falls on you, the Client, and Sportradar.

  • Requires an estimated 2-3 days with coordination between both parties.

Go Live

Once the SDK is integrated, the overlay is placed, and odds and betslip flows are defined, emBET is ready to go live!

At this stage, emBET can be activated in your production environment and made available on live streams.

Going live typically includes internal testing and a final validation with Sportradar.

From this point on, you’re set to launch—start engaging users and driving new betting opportunities with emBET!