Introduction

The BetLink backend controls the BetLink experience. Bets are placed, resulted and also, if necessary, voided by the BetLink backend. The BetLink backend does this by sending RESTful requests to the operator's wallet.

Before the bet placement route can occur, the authorisation pathway must be completed. This can be viewed as a login/handshake proving that the user is indeed genuine and logged into the operator's platform before any bet placement activity can take place. Voiding and resulting can take place without authorisation because they can theoretically occur a long time after bet placement.

The backend integration with the BetLink platform requires the operator to expose a RESTful API to IMGA according to IMGA's technical documentation herein.

BetLink requires 5 simple endpoints to be exposed, as detailed in the 'endpoint' sections below.

We expect the operator to generate and provide us with an API key per environment that controls access to the defined wallet API.