...
Although Multibet is an independent product, the back-end requests follow the same pattern and re-use the same data contracts with the Genius Sports Sportsbook Integration (V3). Therefore, this document should be read in conjunction with Integration Schema, which describes the price feed in detail.
...
| Lucidchart | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Football - all fixtures with InPlay feeds trading coverage
American Football - InPlay NFLNFL, NCAA
Basketball - All FIBA rules fixtures with trading coverage, NBA, NCAA
Fixture data will be delivered via Fixture messages as outlined in “Genius Sports Integration Schema”.
Market Creation/Update
The number of possible combinations for a Multibet market is practically unlimited and therefore the list of available markets cannot be pre-defined as it is typically done for single In Play InPlay selections. Instead, the markets will be dynamically generated in the platform’s back-end, every time a new unique combination of legs is requested from a punter. The name of the market will be the description of the ‘built’ multibet while the MarketType -> Id and MarketType -> Name will remain the same as shown in the example below:
|
The following market types are available for Multibet product:
Sport | MarketType Name | MarketTypeId |
|---|---|---|
Football (10) | Multibet Football | 15316 |
American Football (17) | Multibet American Football | 15317 |
Basketball (4) | Multibet Basketball | 16105 |
Sportsbook Trading Platform Response to Multibet Market Messages
...
Below is an example of platform response when using option 2:
| Code Block | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
<UpdategramResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.sportsdataservices.com/integrationService/v3/response">
<Header>
<!--As received in the original Genius Sports message-->
<MessageGuid>fe2ef81c-8c6d-4f63-9fb4-290bc7f15f1e</MessageGuid>
<!--Timestamp generated when dispatching response -->
<TimeStampUtc>2022-08-10T13:20:04.3634Z</TimeStampUtc>
<!--The Genius Sports Bookmaker Id-->
<BookmakerId>1234</BookmakerId>
<!--The Genius Sports Fixture Id-->
<FixtureId>12312334</FixtureId>
<!--(int)The corresponding platform Fixture Id-->
<PlatformFixtureId>2456789</PlatformFixtureId>
<!--(int) indicates success/failure-->
<StatusCode>0</StatusCode>
<!--(string) describes success/failure-->
<StatusMessage>Success</StatusMessage>
</Header>
<MarketSet>
<Markets>
<Market>
<!--Genius Sports MarketId-->
<Id>104517634</Id>
<!--(string) The corresponding Platform MarketId-->
<PlatformId>123abc</PlatformId>
<!--(string) data required to populate the Betslip in the frontend-->
<PlatformData>
CP$null$6768414.2$Lions%20v%20Jaguares$45592268.2$Anytime%20Tr
yscorer$E6768414.2|SCORE$$$$False$H$null$null$null$$$371565609.2$Coe
tzee,%20A$5$4$D,T,A,C1,C2,C3,C4,C5,C6,C7,C8,C9,C10,C11,C12,TX,P,Y,L1
5,C,L31,H,L63,SH,G,SSA,DSA,S$CP$50652$
</PlatformData>
</Market>
</Markets>
</Markets>
</MarketSet>
</UpdategramResponse></MarketSet>
</UpdategramResponse> |
Prebuilt Multibet
Prebuilt markets are Multibet markets that are pre-built based on a specific template format. They are sent directly to the customer’s trading platform via GS Integration Service and are not created by punters while building their bets. These markets are not visible in Dataservices UI and have different Market Type IDs from usual Multibet markets. Currently, this feature is available exclusively for PreMatch and certain competitions outlined below. Prebuilt markets can be generated from all market types listed here Multibet supported Market Types
Sport | Market Type ID | Name |
|---|---|---|
Football | 16102 | Prebuilt Football |
American Football | 16103 | Prebuilt American Football |
Basketball | 16104 | Prebuilt Basketball |
Example templates
Sport | Template 1 | Template 2 |
|---|---|---|
Football |
|
|
American Football |
|
|
Basketball |
|
|
Prebuilt markets are offered for the following competitions:
Sport | Competitions |
|---|---|
Football |
|
American Football |
|
Basketball |
|
Examples of Prebuilt Multibet markets
Sport | Market Name |
|---|---|
Football | “Anytime Goalscorer - Raheem Sterling; Match Result - Arsenal; Total Goals Over/Under - Over 1.5” |
American Football | "Anytime Touchdown Scorer - Isiah Pacheco; Money Line - Kansas City Chiefs; Total Points Over/Under - Over 42.5" |
Basketball | “Money Line - Los Angeles Lakers; Total Points Over / Under - Over 210.5; 1st Quarter Race to 20 Points - Los Angeles Lakers” |
Rules to generate Prebuilt Multibet markets
fixed leg market, e.g.
MatchResultmarket selection will always be the same, despite trading parameter fluctuations, e.g.
Match Result - Arsenal
most-competitive leg market, e.g.
TotalGoalsOverUnderorAnytimeGoalscorermarket selection will be taken based on the “most competitive” concept, and it might change depending on trading parameters updates:
TotalGoalsOverUnder- selection with the probability closest to 0.5, e.g.Total Goals Over/Under - Over 1.5AnytimeGoalscorer- selection with the highest probability, e.g.Anytime Goalscorer - Raheem Sterling
if “most competitive” selection has been changed (Over 1.5 → Over 2.5) then a new Prebuilt market is created and the current one is suspended
Alternative to Price Push Feed
...
Let’s consider the following scenario: there are 1000 punters creating a unique multibets in a short period of time for one fixture. This means that 1000 new markets will be created and price updates will be pushed for each of them for 1 minute. In In-Play InPlay price updates might happen very often (potentially every second) which means that for this scenario we might send up to 1000 price updates to Sportsbook trading platform.
Alternative approach is to disable the push feed and use prices endpoint provided by /wiki/spaces/MUL/pages/4275994729 Multibet API before accepting the bet.
...
Resulting will be delivered via V3 integration service to Sportsbook trading platform endpoint and the message data contract will remain the same as described under Integration Schema section (link). When Result is received, then market referenced by MarketId should be resulted within Sportsbook trading platform. SelectionResult includes a result value for single selection "Yes", which determines the global outcome of this market. Please find an example message below:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="utf-8"?>
<Updategram xmlns:i="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.sportsdataservices.com/integrationService/v3">
<Header>
<MessageGuid>1856d75e-efef-44e7-8eea-69ec4fa74c58</MessageGuid>
<TimeStampUtc>2022-08-15T10:56:01.672521Z</TimeStampUtc>
<Retry>0</Retry>
</Header>
<ResultSet>
<FixtureId>5553065</FixtureId>
<Results>
<MarketResult>
<MarketId>100032419</MarketId>
<Results>
<SelectionResult>
<SelectionId>300032419</SelectionId>
<ResultStatus>Loser</ResultStatus>
</SelectionResult>
</Results>
</MarketResult>
</Results>
</ResultSet>
</Updategram> |
...
In addition to the above, there is an option to enable a feature which would allow Genius Sports to deliver per-leg resulting information to Sportsbook trading platform. In order to do this, additional selections will be added to the existing MarketResult with additional name properties to identify the individual selections. Below is an example of a result message which includes per-leg resulting info:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="utf-8"?>
<Updategram xmlns:i="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.sportsdataservices.com/integrationService/v3">
<Header>
<MessageGuid>947c89cc-112a-4b81-82be-6184e5777811</MessageGuid>
<TimeStampUtc>2022-08-15T10:56:01.672521Z</TimeStampUtc>
<Retry>0</Retry>
</Header>
<ResultSet>
<FixtureId>5553065</FixtureId>
<Results>
<MarketResult>
<MarketId>100032419</MarketId>
<Results>
<SelectionResult>
<SelectionId>300032419</SelectionId>
<ResultStatus>Loser</ResultStatus>
<Name>Yes</Name>
</SelectionResult>
<SelectionResult>
<SelectionId>0</SelectionId>
<ResultStatus>Winner</ResultStatus>
<Name>Correct score - Perth Glory 2-0</Name>
</SelectionResult>
<SelectionResult>
<SelectionId>0</SelectionId>
<ResultStatus>Loser</ResultStatus>
<Name>Player cards - Scott Galloway carded</Name>
</SelectionResult>
<SelectionResult>
<SelectionId>0</SelectionId>
<ResultStatus>Loser</ResultStatus>
<Name>Player goals - Christopher Ikonomidis score anytime</Name>
</SelectionResult>
</Results>
</MarketResult>
</Results>
</ResultSet>
</Updategram> |
...
Below are key details to consider with the per-leg resulting:
...