Integration Process

Here we walk you through the important steps when getting started with Bettor Sense.

Preconditions:

• Commercials are agreed

• Operator or platform provider is ready to start technical integration

• Ticket stream has been set up

Ticket stream must be set up in order to benefit from Bettor Sense API. It can be set up either through MTS integration or independently from it.

Step-by-Step explanation

Step	Description
1. Kick-off Call	Once the commercial and legal details are finalized the kick-off call includes representatives from the operator, platform provider (if applicable) and Sportradar teams. During this call, several important topics will be discussed, such as the integration flow, the start date of integration, and the planned launch date. Additionally, the initial technical call scheduling with the client's developers and integration engineers will also be determined during this kick-off call.
2. Historical Data Sharing	A one-time historical data export needs to be shared so the AI model is trained on the operator's data. Instructions and sharing folder is set up and provided by the Sportradar team.
3. Technical Call	This call involves the integration team and technical representatives from the client side. It is the opportunity to discuss the integration flow, authentication and authorization. Dedicated communication channel is created. If the client still needs to set up a data ingress flow, that is discussed as well.
4. Integration Credentials	Encrypted credentials for access to Bettor Sense (or shared with Keeper or other secure way of sharing) are sent to the pre-agreed recipient.
5. Client Technical Integration Start	After the client receives credentials (client_id, client_secret and endpoints) the client proceeds with the technical integration phase. The client provides their IP ranges that are allowed to call the API endpoints. The integration process takes place in dedicated communication channels specifically set up for this purpose. The data ingress flow can either be handled in parallel or prior to the API integration.
6. API Integration	In this phase, after reviewing the documentation, the client starts with the integration with the support of the integration team.
7. User Interface Access	The client also provides the list of users they wish to grant access to the Insight Tech Services user interface where Bettor Sense UI is located. Clients can opt to leave the API integration into their own system for the later stages if they determine that the user interface satisfies their current needs. In any case, Insight Tech Services UI can be used to validate that the received API responses reflect the actual state in Bettor Sense databases.
8. Launch Preparation	After the successful completion of end-to-end testing, the launch preparation phase starts which includes: Review of end-to-end test results Making adjustments or corrections required to address potential issues found Contract finalization by the business development manager, assistant and Sportradar legal department Verification of bookmakerID configuration Client configuration on production environment
9. Launch Date	With end-to-end testing completed, and a signed contract, the launch date is agreed upon with the client.
10. Production Credentials	The launch confirmation email is followed by encrypted production credentials.
11. Switching to Production	After the agreed date and time, the Sportradar team assists the operator in switching to production.
12. Post Launch	For the first 48 hours after launch, Sportradar team supports and monitors the client closely.

Data ingress flow

The data ingress stream can be setup up either through MTS integration or independently from it.

More information about MTS integration can be found here.

The following data needs to be provided in order to benefit from Bettor Sense:

• Tickets - more information can be found here.

• Payment requests - more information can be found here.

• Responsible gaming requests - more information can be found here.

Historical data

To train the AI model on your data, we require a one-time historical data export. The extent of this export depends on the scope and history of data already shared with Sportradar. Generally, the same data is needed as in the data ingress flow.

We will set up a secure folder for sharing the file.

The files should preferably be in CSV format and follow the structure defined in the MTS integration documentation, covering an 18-month period.