Feed Integration

Introduction

This section details the feed integration capabilities available, designed to seamlessly embed the excitement of BETCORE games directly into your page element or the partner's page.

With feed integration, you can bring the dynamic, real-time action of our games to your users, enriching their experience and keeping them engaged. Imagine live game broadcasts appearing directly within a designated iframe or a specific container on your webpage.

A robust data transfer system lies at the heart of this integration. Specifically, we offer two primary methods for data delivery:

1. WebSocket (Powered by SignalR)

We utilize the SignalR mechanism within ASP.NET Core, ensuring a persistent, bidirectional connection for real-time data streaming. This means instant updates on game events, odds changes, and everything else your users need to stay on top of the action.

Explore the comprehensive documentation on ASP.NET Core SignalR for a deeper understanding of its capabilities.

2. REST API

For applications requiring a more traditional approach, our REST API provides a secure and reliable alternative. All communication is encrypted using HTTPS over TLS (Transport Layer Security), employing the latest versions 1.2 and 1.3, coupled with RSA-based asynchronous encryption methods. This ensures the confidentiality and integrity of data transmitted between your system and ours.

Quick Links

REST API

Websocket

Terms and definitions

Term	Definition
Partner	API integration service provided by a Partner.
Authentication token	A unique, alphanumeric identifier created on the Partner's side to represent each user. This token acts as a secure credential, enabling access to protected resources and functionalities. It is essential for verifying the user's identity when requesting authentication, retrieving personalized data, and acquiring interaction tokens.
Partner Client	Сlient-side application (such as a web interface or cash desk system) that enables users to place bets on BETCORE games. It's the interface through which your users interact with the BETCORE betting experience.
BETCORE	A robust hardware and software system that enables the real-time distribution of games to partner platforms.
User (player)	A person who bets on games.
WebFrame	The client software solution that provides an interface for betting on BETCORE games. WebFrame is an adaptive embeddable web element that can be added to a website or mobile application.

Integration Requirements

Before you can begin integrating BETCORE games into your platform, please ensure that the following prerequisites are met.

Connect the necessary client libraries.

JavaScript (JS): Npm: @microsoft/signalr

C#: Microsoft.AspNetCore.SignalR.Client 3.1.8

C#/Java: ASP.NET Core SignalR clients

Obtain the required authorization credentials.

PartnerClientId: This unique identifier identifies your specific integration within the BETCORE system.

Secret Key: This confidential key is used in conjunction with the PartnerClientId to generate secure authentication tokens.

Once you have completed these steps, you'll be well-equipped to begin integrating BETCORE games into your platform. Please refer to the subsequent sections of this document for detailed instructions on authentication, data retrieval, and other integration-related topics.

Architecture

PlantUML Code

@startuml
participant BETCORE as b
participant Partner as p
participant "Partner client" as pc


p -> pc : initialize
activate p

pc -> b : video stream connection requets
activate b
b --> pc : stream

group Getting auth token
p -> b : POST /auth/token 
b --> p : return: JWT
alt Incorrect authorization credentials
b --> p : error: 103752
end
end

group Getting game data

group Websocket
p -> b : сonnection to HUB service
b --> p : return
p -> b : creating a subscription connection
b --> p : return
end

opt REST 
p -> b : call API
b --> p : return
deactivate p
deactivate b
end

end

@enduml

Program Interfaces

REST

List of API which you can use.

API	Short Description
POST /auth/token	Authorization.
GET /games/info	Get the game result by ID.
GET /games/types/translations	Get types of translations.
GET /jackpots/accumulated	Get the accumulated jackpot amount.

Websocket

Connection to HUB service	URL: wss://backend.bcdprod.net/signalrhub-livefeed-service/hubs
Query param:	`access_token=JWT`
Query message:	`{ "protocol": "json", "version": 1 }`
Response messages:	`{ "type":6 }` - sign that the connection is established.

List of Subscriptions You Can Use

Subscription	Short Description
SubOnWholeGamesInfo	Getting game results.

Introduction#

1. WebSocket (Powered by SignalR)#

2. REST API#

Quick Links#

Terms and definitions#

Integration Requirements#

Architecture#

Program Interfaces#

REST#

Websocket#

List of Subscriptions You Can Use#

Introduction

1. WebSocket (Powered by SignalR)

2. REST API

Quick Links

Terms and definitions

Integration Requirements

Architecture

Program Interfaces

REST

Websocket

List of Subscriptions You Can Use