...
| 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:
Player picks the selection(s), enters stake and makes the bet attempt.
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).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.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.
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.
...