Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

Introduction


Genius Trading Services (GTS) is an operational service that Genius Services Group (GSG) offers to its customers (trading platforms or bookmakers). It is a combination of Outsourced Trading (OST) with Risk Management by GSG's operational staff. For the bookmaker, this means that we would be managing your trading content, managing trading and risk templates, profiling and limiting the players and other key tasks to ensure your sportsbook day-to-day tasks are taken care of.

...

Info

Bet Assessment and Bet Feed Receiver APIs needs to be set up on Genius Sports side for the specific customer and that could take up to 2 weeks from the time when the integration is agreed.


Overall GTS integration data flow:

  1. Player picks the selection(s), enters stake and makes the bet attempt.

  2. The bet attempt is now sent to Bet Assessment API, that is responsible for accepting or rejecting the bet.
    Recommended option is to use our Bet Assessment API together with Ably: If there is a bet delay applied then the Bet Assessment API returns the bet status delayed and the assessment result is returned via Ably messaging after the configured bet delay value (see Appendix D for how to receive Ably messages).

  3. a. If Bet Assessment API rejects the bet attempt, it would be returning the reason behind the rejection in the message - which you can then present on the betslip for the player, and new bet attempt can be done.
    b. if Bet Assessment API accepts the ticket, then the bet attempt is successful and player should receive immediate confirmation on that.

  4. All the accepted bets should immediately be sent to Bet Feed Receiver API - these bets would then count towards liability calculation and GTS team would also have visibility of these tickets in the Bet Ticker/Bet Scroller.

  5. Whenever the bet is settled, an update is required to be sent into Bet Feed Receiver API. Generally this happens after receiving settlement message from us into your back-end, but we also expect to receive updates for example, if player cashes the ticket out or you decide to void/cancel a ticker for a particular reason.
    After Bet Feed Receiver API has received the settlement, our reporting environment in Power BI, will be updating the numbers accordingly. You would also be granted access to BI, where you can track all the results, KPIs, player data and much more.

...

Property 

Type 

Required 

Explanation 

Comments 

price

decimal 

Required 

The odds for the selection. 

gameState 

string (10)

Required 

Whether the leg is for an InPlay or PreMatch market, supported values: [“PreMatch“/”InPlay”]. 

Markets could have different liability limits for PreMatch and InPlay, so we need to know what was the game state at the time of bet placement.

status 

string (50)

Required 

Current status of the bet leg, supported values: ["Open"/"Settled"/"Cancelled"].

Represents the status of the current leg.  

“Open” - the bet was placed, the result of the leg’s market is still unknown.

“Settled“ - the result of the leg’s market is known and the bet was settled.

“Cancelled“ - the bet was cancelled for any reason and does not bear any risk for a bookmaker, thus should be excluded from liability calculations.

betgeniusContent

BetGeniusContent (see below)

Required

Betgenius content ids and names.

The betgeniusContent field is only required when the content for that leg was provided by Genius Sports.

bookmakerContent

BookmakerContent (see below)

Required

Bookmaker’s content ids and names.

Always required.

payoutPrice 

decimal 

Optional Required

The payout price for this leg.

A required field for settled legs.

This value should be set only once the status of the leg is known, in other words, once the leg has been settled (resulted) and is no longer active.

If the leg wins, payoutPrice will be the same as the Price the leg was struck at. However, there may be cases such as dead heat, refund, partial push, etc. where payoutPrice is less than the maximum amount. Additionally, if the Leg loses, payoutPrice must be set to 0.

In this example, payoutPrice was 50% of the Struck Price - it may have been a 2-way dead heat, for example.

If payoutPrice is absent or NULL, it means the leg is still active. Any actual amount in the Leg's payoutPrice property means the leg is no longer active.

Although this value is optional. if supplied it will enable advanced liability features such as Progressive Multis, which help us better manage your risk.

...

Bets on non-Genius Sports content are supported in GTS, for the case of OPTION 1 2 - Bet delay handled by customer, only HTTP REST API Integration.

...