Skip to content

Getting started

Before you start, you need to retrieve an API authentication X.509 certificate. This certificate will be provided to you by your integration manager from Data.Bet.

Note

Read more info within the Authorization section.

Common integration with the DATA.BET Sportsbook can be described using the next diagram:

Typical sportsbook integration scheme

Connecting to API

Every request to our API must be fulfilled using the X.509 certificate.

For detailed information on how to authenticate and make requests using the X.509 certificate, including code examples for curl, Go, and Node.js, refer to the Authorization documentation.

Backend integration

Token and session management

The first step on your backend side is the ability to generate betting tokens for your users' sessions. You can Heartbeat Callback API to manage your sessions.

For more details about token generation, session lifecycle management, and typical session flow, refer to the Token documentation.

Bet Callback API

The Bet API is the core integration component that must be implemented on the client side. This component handles the critical betting callbacks and interactions.

For more details, refer to the Bet documentation.

Optional integrations

The following features are optional but commonly implemented by partners:

Free Bets and Bet Insurance are bonus mechanics. Partners usually integrate these into their gamification or bonus engine (e.g., welcome bonuses, achievement rewards, tournament prizes, etc.).

To create bonuses, you need access to dictionary entities (sports, leagues, markets, etc.) to specify your bonus conditions. For more details, refer to the Dictionary API.

Admin use cases: Bet Actions API

Partners may want to:

  • Fetch betting history for their admin panels.
  • Cancel or void specific bets manually.

For that purpose, the following Bet Actions is provided

Callback server requirements

Once you're ready to start receiving heartbeat/bet callbacks, provide your callback server URL.

Tip

You can find a simple example of how to develop your own callback server using Node.js in the GitHub repository databet-cloud/callback-server-example. It utilizes every type and callback described within the Bet Swagger specification page.

Frontend integration

Once you are able to create a valid betting token, you can embed the SPA directly into your website with the default view.

Quick start

For testing, you can even create a token using a simple curl command.

For production, your backend must generate and manage per-user tokens.

Adding the bootstrap script

To initialize the SPA, include the bootstrap script on your page.

For more details, refer to the Integration Bootstrap Script section.

This script loads the application and handles communication with the backend.

Add required DOM containers

You'll need to add specific DOM containers where different SPA components will be rendered.

For instructions, refer to the SPA Integration section.

After adding the containers and calling the bootstrap logic with the generated token, the SPA will be fully embedded and functional.

Customization of layout, routes, theme and widgets

For customization of layout, routes, theme and widgets, the Data.Bet team will be able to guide you through the process.

Integration testing before go-live

Before go-live, a mandatory integration testing phase will be run.