Introduction

This document describes technologies available for customers wishing to integrate with Multibet API directly. It explains the overall architecture, integration points and requirements.

1 Introduction
2 Table of Contents
3 Conceptual Diagram
4 API Domain Names
5 Authentication
6 Resources
- 6.1 Fixture Coverage
  - 6.1.1 API Domain Names
  - 6.1.2 Authentication
    - 6.1.2.1 Getting an API key
    - 6.1.2.2 Calling the API
  - 6.1.3 Fixture Coverage Resources
    - 6.1.3.1 Multibet Pre-Match coverage by sport and date range
      - 6.1.3.1.1 Path
      - 6.1.3.1.2 Response Body
    - 6.1.3.2 Multibet Pre-Match coverage by fixture
      - 6.1.3.2.1 Path
      - 6.1.3.2.2 Response Body
    - 6.1.3.3 Multibet In-Play coverage by sport and date range
      - 6.1.3.3.1 Path
      - 6.1.3.3.2 Response Body
    - 6.1.3.4 Multibet In-Play coverage by fixture
      - 6.1.3.4.1 Path
      - 6.1.3.4.2 Response Body
7 Appendix A - End to End Example

Conceptual Diagram

API Domain Names

Environment	Base URL	Notes	Swagger

Environment

Base URL

Notes

Swagger

Production

https://multibet.api.geniussports.com/v2/

Production environment

https://multibet.api.geniussports.com/api-docs/index.html#/

UAT

https://uat.multibet.api.geniussports.com/v2/

User Acceptance Testing. Limited capacity.

https://uat.multibet.api.geniussports.com/api-docs/index.html#/

Authentication

Please refer to the Multibet API Swagger for details regarding authenticating with the API https://multibet.api.geniussports.com/api-docs/index.html

Resources

Genius Sports provides the following API endpoints:

Fixture Coverage - Returns sporting fixtures that are available to be used in Multibet
Market-types - Provides a list of markets and selections that are available to bet upon
Prices - The price of a particular multibet
Cashout - The cashout price of a particular multibet
Results - The result of a particular multibet
Markets - Valid only for customers who use Option 2. Multibet API + Sportsbook Integration. Calling this endpoint causes the Integration Service to create a market in the customer's Trading Platform and returns the market id from the Trading Platform along with any other available context.
- Note: It is expected to receive a response status 404 Not found until the market is successfully created.

For Market Types, Prices, Cashout, Results and Markets, please refer to the Multibet Swagger or the individual links above. For Fixture coverage, see below.

Fixture Coverage

Returns list of fixtures that are available to be used in Multibet. The Fixture Id is required to call the remaining three endpoints: Markets-types, Prices, Results

API Domain Names

Environment	Base URL	Notes

Environment	Base URL	Notes
Production	`https://public.coverage.api.geniussports.com`	Production environment
UAT	`https://uat.public.coverage.api.geniussports.com`	User Acceptance Testing. Limited capacity.

Authentication

You should go through all steps in “Get Cognito Token” and authenticate using the Coverage API <api-key>

Getting an API key

Your <api-key> for using Coverage API will be provided to you during the onboarding process.

Calling the API

Once you have an <access-token> and your <api-key> you can pass these as headers to the API:

curl --request GET \
  --url https://uat.public.coverage.api.geniussports.com/coverage/multibetprematch/fixtures/{fixtureId} \
  --header 'Authorization: Bearer <access-token> \'
  --header 'x-api-key: <api-key>'

Fixture Coverage Resources

Multibet Pre-Match coverage by sport and date range

Returns data about a particular fixture that will show this fixture is available for use in Multibet Pre-Match.

Path

GET /coverage/multibetprematch/sports/{sportId}/fixtures

{sportId} should be replaced by the relevant Genius Sports ids. Only fixtures starting after this date {from_time} and only fixtures starting before this {to_time} will be returned. Format: yyyy-MM-ddTHH:mm:ss E.g. 2023-05-15T20:00:00

Example: https://uat.public.coverage.api.geniussports.com/coverage/multibetprematch/sports/10/fixtures?from_time=2023-05-15T20%3A00%3A00&to_time=2023-05-17T22%3A00%3A00

Response Body

[
    {
        "betgeniusFixtureId": 123456,
        "sourceFixtureId": "123456",
        "source": "GeniusSportsMultibetPreMatch",
        "sportId": 10,
        "available": true,
        "coverageType": 4
    },
    {
        "betgeniusFixtureId": 1234567,
        "sourceFixtureId": "1234567",
        "source": "GeniusSportsMultibetPreMatch",
        "sportId": 10,
        "available": false,
        "coverageType": 4
    },
    {
        "betgeniusFixtureId": 12345678,
        "sourceFixtureId": "12345678",
        "source": "GeniusSportsMultibetPreMatch",
        "sportId": 10,
        "available": true,
        "coverageType": 4
    }
]

Multibet Pre-Match coverage by fixture

Returns data about a particular fixture that will show this fixture is available for use in Multibet Pre-Match.

Path

GET /coverage/multibetprematch/fixtures/{fixtureId}

{fixtureId} should be replaced by the relevant Genius Sports ids.

Example: https://uat.public.coverage.api.geniussports.com/coverage/multibetprematch/fixtures/12345

Response Body

[
    {
        "betgeniusFixtureId": 123456,
        "sourceFixtureId": "123456",
        "source": "GeniusSportsMultibetPreMatch",
        "sportId": 10,
        "available": true,
        "coverageType": 4
    }
]

Multibet In-Play coverage by sport and date range

Returns data about a particular fixture that will show this fixture is available for use in Multibet In-Play.

Path

GET /coverage/multibetinplay/sports/{sportId}/fixtures

{sportId} should be replaced by the relevant Genius Sports ids. Only fixtures starting after this date {from_time} and only fixtures starting before this {to_time} will be returned. Format: yyyy-MM-ddTHH:mm:ss E.g. 2023-05-15T20:00:00

Example: https://uat.public.coverage.api.geniussports.com/coverage/multibetinplay/sports/10/fixtures?from_time=2023-05-15T20%3A00%3A00&to_time=2023-05-17T20%3A00%3A00

Response Body

Multibet In-Play coverage by fixture

Returns data about a particular fixture that will show this fixture is available for use in Multibet In-Play.

Path

GET /coverage/multibetinplay/fixtures/{fixtureId}

{fixtureId} should be replaced by the relevant Genius Sports ids.

Example: https://uat.public.coverage.api.geniussports.com/coverage/multibetinplay/fixtures/12345

Response Body

Appendix A - End to End Example

This example demonstrates the flow of the Multibet API calls for a Football fixture 123456. For simplicity the available markets shown are limited to two (MatchResult and HomeTeamTotalGoalsOverUnder).

Step 1: Get the list of the available market types to show to the user

GET sports/10/fixtures/123456/market-types?limitTo=MatchResult,HomeTeamTotalGoalsOverUnder

Step 2: User adds a leg (Match Result - Home) to the bet

To get the price for the current bet: GET sports/10/fixtures/123456/prices?legs=MatchResult_Home

Step 3: Get the list of the compatible market types to show to the user after one leg is selected

The following request gets the list of available markets taking into account the already selected leg:

GET sports/10/fixtures/123456/market-types?legs=MatchResult_Home&limitTo=MatchResult,HomeTeamTotalGoalsOverUnder

The Match Result market will be included in the response as compatible:false because it is already used in one of the legs. The probabilities and prices take into account that the Match Result Home leg is included in the bet.

Step 3: User adds a second leg (`HomeTeamTotalGoalsOverUnder_Over_2.5`) to the bet

The following call gets the price for the current bet: GET sports/10/fixtures/123456/prices?legs=MatchResult_Home,HomeTeamTotalGoalsOverUnder_Over_2.5

Step 4: Request to create a market for the required bet

Valid only for customers who use Option 2. Multibet API + Sportsbook Integration

The following call creates a market in the customer's Trading Platform, if that bet was not requested previously. In case market has been already created it gets the market id from the Integration Service along with any other available context from Trading Platform

GET /sports/10/fixtures/123456/markets?legs=legs=MatchResult_Home,HomeTeamTotalGoalsOverUnder_Over_2.5

Step 5: Request a result for the bet

GET sports/10/fixtures/123456/results?legs=MatchResult_Home,HomeTeamTotalGoalsOverUnder_Over_2.5

Multibet API

Introduction

Table of Contents

Conceptual Diagram

API Domain Names

Authentication

Resources

Fixture Coverage

API Domain Names

Authentication

Getting an API key

Calling the API

Fixture Coverage Resources

Multibet Pre-Match coverage by sport and date range

Path

Response Body

Multibet Pre-Match coverage by fixture

Path

Response Body

Multibet In-Play coverage by sport and date range

Path

Response Body

Multibet In-Play coverage by fixture

Path

Response Body

Appendix A - End to End Example

Step 1: Get the list of the available market types to show to the user

Step 2: User adds a leg (Match Result - Home) to the bet

Step 3: Get the list of the compatible market types to show to the user after one leg is selected

Step 3: User adds a second leg (HomeTeamTotalGoalsOverUnder_Over_2.5) to the bet

Step 4: Request to create a market for the required bet

Step 5: Request a result for the bet

Step 3: User adds a second leg (`HomeTeamTotalGoalsOverUnder_Over_2.5`) to the bet