Splash Jackpot SDK provides two widgets:



The widgets are injected into the DOM as iframes. Widgets run inside isolated iframes hosted by Splash infrastructure. Communication between operator’ application and the widgets happens through the SDK using postMessage. The SDK handles iframe creation, lifecycle management, and message passing.
Install the Splash Jackpot SDK in operator’ application:
npm install @splash-tech/jackpot-sdk
Both widgets support the following parameters:
| Parameter | Type | Default | Description | Required |
|---|---|---|---|---|
| data | object | null | null | Widget data provided by Splash backend |
| container | string | document.body | CSS selector of container element where widget will be injected | Optional |
| mode | string | production | SDK environment (local, dev, staging, production) | Optional |
| jackpotId | string | undefined | Jackpot identifier | Optional |
| tag | string | undefined | Game tag | Optional |
| brand | string | undefined | Operator brand | Optional |
// launch footer widget example
splashJackpot.footerWidget.launch({
data: data,
container: '#game-container',
mode: 'production',
jackpotId: 'test-id',
tag: 'test-tag',
brand: 'test-brand'
});
Notes:
Default styles for the footer widget are:
position: fixed;
bottom: 0;
left: 0;
width: 100%;
max-width: 1300px;
height: 50px;
z-index: 999999 // 6
If container parameter is used, then the widget iframe is absolutely positioned, and the container’s position is set to relative
container supports any valid CSS selector (#id, .class, div[data-attr]) and will use the first matching element. If no container is found, the widget defaults to document.body