LO - XML configuration

When new features are released they will not automatically be included in the feed. Clients need to enable the features on the Live Odds XML configuration page before they will start receiving them. Please note that, due to caching, after enabling or disabling any of the features it may take up to several hours before the change takes effect. This also applies to activation and deactivation of markets/tournament/category/sport. If you see no changes you made within a day, then there is something wrong and you should contact support.

The specific code which is generating canceled goals is behaving exactly the same way as for adding a score, with the exception that for canceled goals we set a canceled flag to "true". The difference is that with the card element we will always set the canceled flag to either "true" or "false", but for cards it is only set if the goal is canceled.

Additionally, the new features are added to the test server a few weeks before the actual release, so they can be tested.

The following section covers the XML configuration options which apply to all sports. For more detailed information about the XML configurations per sport, see each sport's dedicated section.

Include Live Odds probabilities

Whether to add probabilities to the Live Odds xml feed or not. If this setting is not enabled, only odds values are included in the Live Odds xml feed. If this setting is enabled, probabilities based on an odds key of 100 % (no margin) are added to the Live Odds xml feed, in addition to the regular odds values.

XML example - setting disabled

<Match active="1" betstatus="started" matchid="10028941" matchtime="43" msgnr="53" score="0:1" status="1p">
<Odds active="1" changed="true" combination="0" freetext="1st Half - Exact number of goals" ... >
<OddsField active="0" type="0" typeid="418"/>
<OddsField active="0" type="1" typeid="419"/>
<OddsField active="1" type="2" typeid="420">4.43</OddsField>
<OddsField active="1" type="3" typeid="421">71.34</OddsField>
<OddsField active="1" type="4+" typeid="422">100.0</OddsField>
</Odds>
</Match>

XML example - setting enabled

<Match active="1" betstatus="started" matchid="10028941" matchtime="43" msgnr="53" score="0:1" status="1p">
<Odds active="1" changed="true" combination="0" freetext="1st Half - Exact number of goals" ... >
<OddsField active="0" type="0" typeid="418"/>
<OddsField active="0" type="1" typeid="419" probability="0.898"/>
<OddsField active="1" type="2" typeid="420" probability="0.0966">4.43</OddsField>
<OddsField active="1" type="3" typeid="421" probability="0.0052">71.34</OddsField>
<OddsField active="1" type="4+" typeid="422" probability="2.0E-4">100.0</OddsField>
</Odds>
</Match>

If the value of the probability attribute is very low, the scientific notation (for example 2.0E-4) can be used to display the number, rather than a normal double. The probability attribute can be added to the OddsField even if the outcome is inactive (active = 0).

Note
If no probabilities are available for the current OddsField, the probability attribute will not be set, even if the option is enabled.

Live Odds probability precision

Number of decimals (1 - 10) for the value of the probability attribute in the Live Odds XML feed. This setting is only used if the Live Odds probabilities setting is enabled.

(ID: 4) Include response reply number for error, current and scoreandcardsummary messages

This setting will help client systems getting a clear overview of the response messages which are recieved after error, current and scoreandcardsummary requests. It will become visible when the response starts and ends, and it will be easy to group the responses together. Enabling this setting will add a new attribute replynr to the <BetradarLiveOdds> element and use two new values in the status attribute.

XML example

<!-- Request -->
<BookmakerStatus timestamp="0" type="error" bookmakerid="12345">
<Match matchid="935448" active="1" />
</BookmakerStatus>
<!-- Response -->
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="3" replytype="error" status="replystart" timestamp="
1260866252519"/>
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="3" replytype="current" status="betstart" time="0" timestamp="
1260866108600">
<Match active="1" betstatus="started" matchid="935448" matchtime="12" score="0:0" status="1p"/>
</BetradarLiveOdds>
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="3" replytype="current" status="clearbet" time="517" timestamp
="1260866108600">
<Match active="1" betstatus="stopped" clearedscore="0:0" matchid="935448" matchtime="1" status="1p">
<!-- Odds overview -->
</Match>
</BetradarLiveOdds>
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="3" replytype="error" status="replyend" timestamp="
1260866252767"/>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BetradarLiveOdds	status	The error/current/scoreandcardsummary response messages are surrounded by two messages with status replystart and replyend.	String replystart replyend
BetradarLiveOdds	replynr	The id of the response to the error/ current/scoreandcardsummary request. All messages which are a response to the error/current/scoreandcardsummary request do have the same replynr.	Integer If the attribute requestnr was set in the error/current/scoreandcardsummary request, the replynr in the response message will take this value.

(ID: 84) Include response reply number in meta messages

If this setting is enabled, an attribute replynr will be added to the BetradarLiveOdds element in match meta messages.

XML example

<!-- Meta request -->
<BookmakerStatus type="meta" bookmakerid="12345"/>
<!-- Meta response -->
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="2" status="meta" timestamp="1400146666680">

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BetradarLiveOdds	replynr	The id of the response to the meta request. All messages which are a response to the meta request do have the same replynr.	Integer If the attribute requestnr was set in the meta request, the replynr in the response message will take this value.

Reply number specified by client

The client system can specify the reply through the request, in case you want to keep your own counter for the reply number.

XML example

<!-- Meta request with requestnr -->
<BookmakerStatus type="meta" bookmakerid="12345" requestnr="1234"/>
<!-- Meta response -->
<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replynr="1234" status="meta" timestamp="14006666680">

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BookmakerStatus	requestnr	The id of the meta request as specified by the client. If this attribute is added to the request, the response will contain the replynr attribute regardless of the value of this setting.	Integer If the attribute requestnr was set in the request, the replynr in the response will take this value.

(ID: 8) Enable response on register and unregister requests

It is possible to register or unregister for a match, odds, or oddsfields through the feed. Normally the Betradar system does not send a response to this. If this setting is enabled the client system will receive a match meta information message. The active fields will indicate the status of the (un)registration.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replytype="register" status="meta" timestamp="1275050982039">
<Match active="1" matchid="935448" status="1p">
<MatchInfo>
<!-- Match info goes here -->
</MatchInfo>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BetradarLiveOdds	replytype	The source of the message, the type of request or setting the message is a reply to.	String register unregister
Match	active	The registration status. This attribute can also occur in the elements Odds or OddsField.	Integer 1 = registered 0 = unregistered / match unavailable

(ID: 88) Include autotraded attribute in meta messages

If this setting is enabled, an attribute autotraded will be added to the Match element in match meta messages. The attribute will only be added if the match is an Auto-traded Live Odds match.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1405677142338">
<Match status="not_started" matchid="956" booked="1" autotraded="1" active="1">
<MatchInfo>
<DateOfMatch>1415016577000</DateOfMatch>
<Sport id="5">Tennis</Sport>
<Category id="3">ATP</Category>
<Tournament id="568">Paris TMS, France</Tournament>
<HomeTeam uniqueid="14321" id="11403">AGASSI, ANDRE</HomeTeam>
<AwayTeam uniqueid="14329" id="11749">GAUDIO, GASTON</AwayTeam>
</MatchInfo>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Match	autotraded	Whether the match is Auto-traded or not.	Integer 1 = Auto-traded

(ID: 24) Include extra sport info in meta messages

If this setting is enabled, sport specific information (like period length, number of sets) for the match will be added to the match meta messages.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1405677142338">
<Match active="1" booked="1" matchid="4972075" status="not_started">
<MatchInfo>
<DateOfMatch>1405677600000</DateOfMatch>
<Sport id="1">Soccer</Sport>
<Category id="5">Norway</Category>
<Tournament id="5">Eliteserien</Tournament>
<HomeTeam id="5020" uniqueid="1161">ROSENBORG BK</HomeTeam>
<AwayTeam id="5293699" uniqueid="678">HØNEFOSS BK</AwayTeam>
<TvChannels/>
<ExtraInfo>
<Info type="PeriodLength">45</Info>
<Info type="OvertimeLength">15</Info>
</ExtraInfo>
<Streaming/>
</MatchInfo>
</Match>
</BetradarLiveOdds>

The value of the attribute type for each Info element is depending on the sport of the match. See the overview of all the sports and their info types below:

Sport	Possible values type attribute
Soccer	PeriodLength, OvertimeLength
Tennis	NumberOfSets, AdvantageRule, MatchTieBreakSet
Basketball	PeriodLength, OvertimeLength
Ice hockey	PeriodLength, OvertimeLength
Handball	PeriodLength, OvertimeLength
Volleyball	NumberOfSets, SetLimit, Format
Beach volleyball	NumberOfSets, SetLimit, Format
Badminton	NumberOfSets, SetLimit, Format
Table tennis	NumberOfSets
American football	PeriodLength, OvertimeLength
Snooker	BestOfFrames
Darts	DrawPossible, BestOfXSets, BestOfXLegs
Futsal	PeriodLength, OvertimeLength
Bowls	BestOfSets, EndsPerSet, SetPlaythrough, EndsInTiebreak, TiebreakScoringIsEnds
Squash	NumberOfGames, GameLimit, Format
Dota2	Best of maps
CS:GO	Best of maps, Rounds per map, Best of rounds in OT
League of legends	Best of maps

(ID: 82) Include streaming info in meta messages

If this setting is enabled, streaming information for the match will be added to the match meta messages.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1405677142338">
<Match active="1" booked="1" matchid="4972075" status="not_started">
<MatchInfo>
<DateOfMatch>1405677600000</DateOfMatch>
<Sport id="1">Soccer</Sport>
<Category id="5">Norway</Category>
<Tournament id="5">Eliteserien</Tournament>
<HomeTeam id="5020" uniqueid="1161">ROSENBORG BK</HomeTeam>
<AwayTeam id="5293699" uniqueid="678">HØNEFOSS BK</AwayTeam>
<TvChannels/>
<Streaming>
<Channel id="1">Live Channel Retail LIVE Match</Channel>
<Channel id="2">Live Channel Retail LIVE Visualisation</Channel>
<Channel id="3">Live Channel Online LIVE Match</Channel>
<Channel id="4">Live Channel Online LIVE Visualisation</Channel>
</Streaming>
</MatchInfo>
</Match>
</BetradarLiveOdds>

The following streaming channels are available:

Channel ID	Channel description
1	Live Channel Retail LIVE Match
2	Live Channel Retail LIVE Visualisation
3	Live Channel Online LIVE Match
4	Live Channel Online LIVE Visualisation

(ID: 90) Include coverage info in meta messages

If this setting is enabled, coverage information for the match will be added to the match meta messages. The type of markets that are available will depend on what type of coverage (deeper or basic) is available for the match. If the type element displays "Extended markets" it indicates that deeper coverage is available.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1405677142338">
<Match active="1" booked="1" matchid="4972075" status="not_started">
<MatchInfo>
<DateOfMatch>1405677600000</DateOfMatch>
<Sport id="1">Soccer</Sport>
<Category id="5">Norway</Category>
<Tournament id="5">Eliteserien</Tournament>
<HomeTeam id="5020" uniqueid="1161">ROSENBORG BK</HomeTeam>
<AwayTeam id="5293699" uniqueid="678">HØNEFOSS BK</AwayTeam>
<TvChannels/>
<CoverageInfo>
<Type id="1">Extended markets</Type>
</CoverageInfo>
</MatchInfo>
</Match>
</BetradarLiveOdds>

The following coverage information types are available:

Type ID	Coverage description
1	Extended markets

(ID: 126) Include covered from in meta messages

Enabling this setting will add the element <CoverageInfo> to <MatchInfo>, and add <CoveredFrom> as a child. The possible values for the <CoveredFrom>-element are either venue or tv.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1405677142338">
<Match matchid="4972075" ...>
<MatchInfo>
...
<CoverageInfo>
...
<CoveredFrom>venue</CoveredFrom>
</CoverageInfo>
</MatchInfo>
</Match>
</BetradarLiveOdds>

Note
If the XML configuration in chapter 5.1.1.7 is enabled, the <CoverageInfo> element is already added and will be reused, meaning that the <CoveredFrom> element will become an additional child to the already existing <CoverageInfo> element. However, if the corresponding XML configuration in is not enabled, enabling the current setting will add the <CoverageInfo> element.

(ID: 12) Include non-booked matches in meta messages

When a client system sends out a meta request the response messages usually includes all the booked matches. Clients who want to include matches that are available for booking, but not booked, should enable this setting. If this setting is enabled the attribute booked is added to the Match elements to indicate whether the match is booked or not.

XML example

<BetradarLiveOdds status="meta" timestamp="1184145290125" xmlns="http://www.betradar.com/BetradarLiveOdds">
<Match active="1" booked="0" matchid="500581" status="not_started">
<MatchInfo>
<!-- Match info -->
</MatchInfo>
</Match>
<Match active="1" booked="1" matchid="505484" status="not_started">
<MatchInfo>
<!-- Match info -->
</MatchInfo>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element

Attributes

Attribute

Description

Possible values

Match

booked

Whether the match is booked or not.

Integer

1 = booked

0 = not booked

Note
The behaviour for this setting is the same as when the client sets includeavailable="true" in the meta request. However, if a meta request contains this attribute it will override the value of this setting.

(ID: 13) Include clock stopped information for sports that supports this

The following sports support that the clock stops during a match: basketball, ice hockey, handball, futsal. Enabling this setting will add an attribute clock_stopped to the Match element for all those sports.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1287056116518">
<Match active="1" betstatus="stopped" clock_stopped="1" matchid="6414605" matchtime="8" msgnr="37" score="0:0"/>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Match	clock_stopped	Whether the clock is running or the clock is stopped.	Integer 1 = Clock is stopped 0 = Clock is running

(ID: 14) Send irrelevant change message for changes that aren’t of interest

Sometimes changes happen which are not interesting for the client system. This could for example be bet clearing of a bet type which the client unsubscribed from. In this situation the Betradar system sends out an odds change message, which can be quite comprehensive. If the change which happened is not interesting for the client system it’s needless to parse the change message.

This setting allows the client system to ignore change messages which are not interesting for them. If this setting is enabled, instead of the not interesting change message a message with status="irrelevantchange" is sent.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="irrelevantchange" timestamp="1287060653120">
<Match active="1" betstatus="stopped" matchid="1467300" msgnr="37" status="pause1"/>
</BetradarLiveOdds>

Element	Attributes
	Attribute	Description	Possible values
BetradarLiveOdds	status	The type of the message.	String "irrelevantchange" (for irrelevantchange messages)
Match	msgnr	The number of the message. Important here is that, even though the original change message was not sent, the message number of the irrelevant change message did still increasy by 1. This ensures that the sequence of message numbers will remain sustained.	Integer

(ID: 21) Don’t send updates for inactive bettypes except the deactivation

Change messages containing all the bet types, both active and inactive ones. Depending on what sport or match, the number of inactive markets can increase rapidly. Enabling this setting will make sure that only active oddstypes or oddstypes which just changed are in the change messages. Updates for inactive bet types are no longer sent out, only when they get deactivated in order to keep the messages compact.

This setting only applies to bet types that are inactive, for example because it is no longer offered for this match. It does NOT apply to bet types that are unregistered by the client (markets deactivated by clients). However, the odds element will still be included for clients, but with the active attribute set to active="0", and no odds fields.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1526252416174">
<Match active="1" betstatus="started" earlybetstatus="stopped" matchid="13497237" matchtime="43" msgnr="485" score="0:2" status="1p">
<!-- ...shortened... -->
<Odds active="0" changed="true" combination="0" freetext="Anytime Goal scorer" id="963225658" specialoddsvalue="-1" subtype="146" type="
ftnw" typeid="8"/>
<!-- ...shortened... -->
<Odds active="0" changed="true" combination="0" freetext="Next Goal scorer" id="963246016" specialoddsvalue="0:2" subtype="147" type="
ftnw" typeid="8"/>
<!-- ...shortened... -->
</Match>
</BetradarLiveOdds>

(ID: 22) Send bet clearings even if match is not active

If this setting is enabled, bet clearings and bet cancellations will get sent even if the match has been deactivated. Please note that after enabling this option there might be gaps in the value of msgnr for inactive matches, as only bet clearings and bet cancellation matches get sent out.

(ID: 16) Use additional match statuses for overtime

Additional match statuses during overtime and penalty shoot-outs are available for the following sports:

American Football
Aussie Rules
Futsal
Handball
Rugby
Soccer

If this setting is enabled and the match has overtime (and possibly a penalty shoot-out) the match will get the following statuses in the same order as specified below:

ID	Status	Status description	Additional information
7/6	2p/4q	Last normal period/quarter of the match	This is a regular match status which already exists. After this match status the overtime related match statuses begin.
32	awaiting_ot	Waiting for overtime to start	Match gets this status if the match has overtime.
41	1p_ot	1st overtime period	Match gets this status if the match has overtime.
33	ot_ht	Pause between 1st and 2nd overtime period	Match gets this status if the match has overtime.
42	2p_ot	2nd overtime period	Match gets this status if the match has overtime.
110	after_ot	Match finished after overtime	Match gets this status if the match has overtime.
34	awaiting_pen	Wating for penalty shoot-out to start	Match only gets this status if the match has a penalty shoot-out
50	pen	Penalty shoot-out	Match only gets this status if the match has a penalty shoot-out.
100	ended	The match has ended	This is a regular match status which already exists.

(ID: 23) Use additional match statuses for walkover / retired

There are two regular match statuses, "retired" and "walkover". Enabling this setting will replace those match statuses by new ones, specifying which player won by walkover or which player retired. The new matchstatuses are:

ID	Status	Status description	Additional information
93	walkover1	The home team won the match by walkover	If this setting is enabled, this match status will replace the regular "walkover" match status
94	walkover2	The away team won the match by walkover	If this setting is enabled, this match status will replace the regular "walkover" match status
95	retired1	The away team won because the home team retired	If this setting is enabled, this match status will replace the regular "retired" match status.
96	retired2	The home team won because the away team retired	If this setting is enabled, this match status will replace the regular "retired" match status.

(ID: 48) Use match status abandoned

By enabling this setting, the client system receives match status Abandoned if the match gets set to abandoned. If this setting is not enabled, match status Interrupted will be used instead.

ID	Status	Status description	Additional information
80	interrupted	The match has been interrupted
90	abandoned	The match has been abandoned	If this setting is enabled, this match status will replace the "interrupted" match status on abandoned matches

(ID: 11) Send manual odds changes immediately

Manual odds changes made in the configuration interface are called risk adjustments. Usually those risk adjustments will be included in the next normal odds change message. Enabling this setting will send out a new change message immediately after the risk adjustment was made. The message will look like a normal change message, but will additionally have the attribute replytype set to "riskadjustment_update".

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replytype="riskadjustment_update" status="change" timestamp="
1297685983108">
<Match active="1" betstatus="stopped" matchid="935448" score="-:-" status="not_started">
<!-- Different odds go here -->
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BetradarLiveOdds	status	The type of the message.	String "change" (for odds change messages)
BetradarLiveOdds	replytype	The source of the message, the type of request or setting the message is a reply to.	String "riskadjustment_update" (for risk adjustment updates)

(ID: 18) Show current period score during period

The attribute setscores contains the scores of all the periods which have ended. For the following sports the current period is not included:

American Football
Aussie Rules
Baseball
Basketball
Cricket
Futsal
Handball
Ice Hockey
Rugby
Soccer

Enabling this setting will include the score of the current period for the sports mentioned above in the setscores attribute. Other sports, which are not mentioned in the list above, do always have the current period included in the setscores attribute.

In the following XML examples you will see a soccer match which is in the second period, and what difference this XML setting makes:

XML example - setting disabled

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1297687408708">
<Match active="1" betstatus="stopped" matchid="935448" score="1:1" setscores="0:1" status="2p" matchtime="65" msgnr="26" />
</BetradarLiveOdds>

XML example - setting enabled

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1297687408708">
<Match active="1" betstatus="stopped" matchid="935448" score="1:1" setscores="0:1 - 1:0" status="2p" matchtime="65" msgnr="26" />
</BetradarLiveOdds>

(ID: 30) Split set scores

All the setscores are gathered in one attribute in the match element, setscores="X1:Y1 - X2:Y2 -...". Enabling this setting will split the setscores in different attributes, setscore1="X1:Y1", setscore2="X2:Y2", etc.

XML example - setting disabled

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="alive" timestamp="1308561825332">
<Match active="1" betstatus="started" gamescore="0:0" matchid="935457" msgnr="58" setscores="6:3 - 1:3" score="1:0" server="1" status="
2set" tiebreak="false"/>
</BetradarLiveOdds>

XML example - setting enabled

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="alive" timestamp="1308561825332">
<Match active="1" betstatus="started" gamescore="0:0" matchid="935457" msgnr="58" score="1:0" server="1" setscore1="6:3"
setscore2="1:3" status="2set" tiebreak="false"/>
</BetradarLiveOdds>

(ID: 44) Include suspension counters in feed

The Betradar system counts the suspensions of both the home and away team for the following sports:

Handball
Futsal
Ice hockey

Those counters are not included in the feed by default. Enabling this setting will add two attributes to the Match element.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1287056116518">
<Match active="1" betstatus="stopped" matchid="6414605" matchtime="8" msgnr="37" score="0:0" setscores="0:0" status="1p"
suspendAway="0" suspendHome="0" />
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Match	suspendHome	The amount of suspensions for the home team.	Number >= 0
Match	suspendAway	The amount of suspensions for the away team.	Number >= 0

(ID: 29) Mark most balanced odds

If this setting is enabled, the Betradar system will mark the most balanced odds by adding an attribute mostbalanced to the Odds elements.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1199777659034">
<Match active="1" betstatus="started" matchid="5984472" matchtime="38" msgnr="155" score="1:0" setscores="1:0" status="1p" >
<Odds active="1" changed="true" combination="0" freetext="Total Corners" id="57178832" mostbalanced="0" specialoddsvalue="7.5"
subtype="126" type="ftnw" typeid="8">
<OddsField active="1" type="under" typeid="373">2.6</OddsField>
<OddsField active="1" type="over" typeid="374">1.45</OddsField>
</Odds>
<Odds active="1" changed="false" combination="0" freetext="Asian handicap first half" ftr ="-0.25" id="57178580" mostbalanced="1"
specialoddsvalue="-1.25" subtype="36" type="ft2w" typeid="7">
<OddsField active="1" type="1" typeid="17">2.8</OddsField>
<OddsField active="1" type="2" typeid="18">1.4</OddsField>
</Odds>
<Odds active="0" changed="false" combination="0" freetext="1st Half - Corner Handicap" id="57173070" mostbalanced="0"
specialoddsvalue="-1.5" subtype="123" type="ft2w" typeid="7"/>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Odds	mostbalanced	Whether the odds are the most balanced odds or not.	Integer 1 = most balanced odds 0 = not most balanced odds

Note
If this setting is enabled the mostbalanced attribute will be added to all the odds. Even if only one odds is present the mostbalanced attribute will still be added, and the value will be 1.

(ID: 55) Include typeid in oddsfield tag

Enabling this setting will add an extra attribute typeid to OddsField elements.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1199777659034">
<Match active="1" betstatus="started" matchid="5984472" matchtime="3" msgnr="15" score="1:0" setscores="1:0" status="1p" >
<Odds active="1" changed="true" combination="0" freetext="Total Corners" id="57178832" specialoddsvalue="7.5" subtype="126" type="ftnw
" typeid="8">
<OddsField active="1" type="under" typeid="373">2.6</OddsField>
<OddsField active="1" type="over" typeid="374">1.45</OddsField>
</Odds>
<Odds active="1" changed="false" combination="0" freetext="Asian handicap first half" ftr ="-0.25" id="57178580" specialoddsvalue="
-1.25" subtype="36" type="ft2w" typeid="7">
<OddsField active="1" type="1" typeid="17">2.8</OddsField>
<OddsField active="1" type="2" typeid="18">1.4</OddsField>
</Odds>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
OddsField	typeid	Contains a numeric identifier of the odds field.	Integer

(ID: 63) Include playerid in oddsfield tag

Enabling this setting will add an extra attribute playerid to OddsField elements which represent player-markets.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1199777659034">
<Match active="1" betstatus="started" matchid="5984472" matchtime="3" msgnr="15" score="1:0" setscores="1:0" status="1p" >
<Odds active="1" changed="true" combination="0" freetext="Next Goal scorer" id="67934496" specialoddsvalue="0:0" subtype="147" type="
ftnw" typeid="8">
<OddsField active="1" playerid="2363" type="Hilbert, Roberto" typeid="469">24.0</OddsField>
<OddsField active="1" playerid="11179" type="Spahic, Emir" typeid="470">47.0</OddsField>
<OddsField active="1" playerid="15800" type="Bender, Lars" typeid="471">24.0</OddsField>
<OddsField active="1" playerid="29791" type="Papadopoulos, Kyriakos" typeid="472">33.0</OddsField>
</Odds>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
OddsField	playerid	Contains a numeric identifier of the player.	Integer

(ID: 93) Include playerid in score and card event

Enabling this setting will add an extra attribute playerid to Card and Score elements.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" replytype="scoreandcardsummary" status="score" timestamp="
1277801191793">
<Match active="1" betstatus="stopped" matchid="1355389" score="3:0" status="ended">
<Card id="105609" player="Docherty" playerid="115622" team="home" time="1" type="red"/>
<Score away="0" home="1" id="105611" player="S.Lowry" playerid="77988" scoringteam="home" time="3" type="score"/>
<Score away="1" home="1" id="105619" player="R.Glendinning" playerid="115631" scoringteam "away" time="21" type="score"/>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Score, Card	playerid	Contains a numeric identifier of the player.	Integer

(ID: 15) Include after overtime and after penalty score in score summary

The score and card summary contains the score on half time and score on full time in two separate Score elements. Enabling this setting will add two more Score elements which indicate the score after overtime and the score after penalties. Each of those Score elements gets added only if the match reaches the stage the element represents.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="score" timestamp="1423432823792">
<Match active="1" betstatus="stopped" cornershome="6" cornersaway="6" earlybetstatus="stopped" matchid="6652509" msgnr="564"
redcardsaway="0" redcardshome="0" score="4:5" setscores="0:0 - 0:0 - 0:0 - 4:5" status="ended" yellowcardsaway="0"
yellowcardshome="4" yellowredcardsaway="0" yellowredcardshome="0">
<Score away="3" home="3" id="8802822" player="Y.Toure" scoringteam="home" time="-1" type="score"/>
<Card id="8802250" player="S.Tiene" team="home" time="57" type="yellow"/>
<Card id="8802568" player="E.Bertrand" team="home" time="105" type="yellow"/>
<Card id="8801682" player="S.Die" team="home" time="14" type="yellow"/>
<Score away="0" home="0" time="45" type="ht"/>
<Score away="4" home="3" id="8802842" player="J.Mensah" scoringteam="away" time="-1" type="score"/>
<Score away="2" home="1" id="8802776" player="S.Aurier" scoringteam="home" time="-1" type="score"/>
<Score away="4" home="4" id="8802854" player="S.Kalou" scoringteam="home" time="-1" type="score"/>
<Score away="0" home="0" time="120" type="ot"/>
<Score away="1" home="0" id="8802732" player="M.Wakaso" scoringteam="away" time="-1" type="score"/>
<Score away="2" home="2" id="8802792" player="S.Doumbia" scoringteam="home" time="-1" type="score"/>
<Score away="4" home="2" id="8802842" player="J.Mensah" scoringteam="away" time="-1" type="score"/>
<Score away="0" home="0" time="90" type="ft"/>
<Score away="5" home="4" id="8802868" player="E.Badu" scoringteam="away" time="-1" type="score"/>
<Score away="2" home="0" id="8802750" player="J.Ayew" scoringteam="away" time="-1" type="score"/>
<Score away="3" home="2" id="8802814" player="Dede" scoringteam="away" time="-1" type="score"/>
<Score away="5" home="4" time="120" type="pen"/>
<Card id="8802428" player="W.Kanon" team="home" time="87" type="yellow"/>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Score	type	The type of the score. The values "ot" and "pen" are only included if this setting is enabled and if the match reaches those stages.	String. Values which get added when enabling this setting: "ot" = score after overtime "pen" = score after penalties

(ID: 94) Send error message on failed bookmatch requests

If this setting is enabled an error message will be sent in response when a bookmatch request is sent for a match that isn’t possible to book, or already available.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="error" timestamp="1408607816955">
<Match active="0" booked="0" matchid="1171785" status="not_started"/>
<Message>Cannot book matchid: 1171785. This match is not offered within our live betting services, only LCoO services</Message>
</BetradarLiveOdds>

(ID: 72) Include betstop reason

When a match is a scout match and the scout changes the match to bestop, it is possible that a reason for this betstop was included by the scout. Clients which have this setting enabled will receive two additional attributes in the Match element, betstopreason and betstopreasonid.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="betstop" time="0" timestamp="1395803868428">
<Match active="1" betstatus="stopped" betstopreason="DANGEROUS_FREE_KICK_HOME" betstopreasonid="18" matchid="4885080"
matchtime="55" msgnr="169" score="1:1" setscores="1:1" status="2p" />
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
Match	betstopreason	Contains a textual representation of the betstop reason.	String For possible values see table below.
Match	betstopreasonid	Contains a numeric identifier of the betstop reason.	Integer For possible values see table below.

ID	Betstop reason	ID	Betstop reason	ID	Betstop reason
1	Possible goal	31	Possible fieldgoal [T1]	61	Possible challenge
2	Possible red card	32	Possible fieldgoal [T2]	62	Possible card
3	Scout lost	33	Possible safety [T1]	63	Delayed penalty
4	Possible goal [T1]	34	Possible safety [T2]	64	Shoot-out begins
5	Possible goal [T2]	35	Possible turnover [T1]	65	Empty net
6	Possible red card [T1]	36	Possible turnover [T2]	66	Possible try home
7	Possible red card [T2]	37	Video review	67	Possible try away
8	Possible penalty	38	Redzone [T1]	68	Possible drop goal home
9	Possible penalty awarded to [T1]	39	Redzone [T2]	69	Possible drop goal away
10	Possible penalty awarded to [T2]	40	Possible Boundary	70	Possible card home
11	Connected to supervisor	41	Possible Wicket	71	Possible card away
12	Match ended	42	Possible Challenge [T1]	72	Possible penalty [T1]
13	Gamepoint	43	Possible Challenge [T2]	73	Possible penalty [T2]
14	Tie	44	Possible Turnover	74	Delayed penalty [T1]
15	Possible direct foul [T1]	45	Unknown operator	75	Delayed penalty [T2]
16	Possible direct foul [T2]	46	Freeball	76	Two man advantage home
17	Possible direct foul	47	Deep Ball	77	Two man advantage away
18	Dangerous free kick [T1]	48	Possible Run	78	Possible field goal
19	Dangerous free kick [T2]	49	Maintenance	79	Rollback event
20	Dangerous goal position [T1]	50	Base Hit Deleted	80	Possible drop kick home
21	Dangerous goal position [T2]	51	Match delayed	81	Possible drop kick away
22	Goal under review	52	Match postponed	82	Possible drop kick
23	Score under review	53	Scout disconnection tv signal	83	Possible Video Assistant Referee
24	Disconnection	54	Possible Penalty Offsetting	84	Feed Interruption
25	Possible checkout	55	Not in use/Depricated
26	Multiple suspensions	56	Not in use/Depricated
27	Possible dangerous free kick	57	Possible fourth down attempt home
28	Possible dangerous goal position	58	Possible fourth down attempt away
29	Possible touch down [T1]	59	Possible onside kick home
30	Possible touch down [T2 ]	60	Possible onside kick away

(ID: 102) Send empty meta response

If this setting activated a meta request will always respond with an XML message back, even if no matches are included.

(ID: 20) Show period scores in all sports

If this setting is activated, for all sports the half time, full time, overtime and period scores are included in the setscores attribute.

(ID: 123) Send clearbet message for any draw no bet, home no bet and away no bet market in case
of a refund

When this is activated a clearbet message with refund will be sent when a draw no bet market ends in a draw, and not a
cancelbet message.

(ID: 125) Include BetPal info in meta messages

Enabling this setting will add an element <Betpal> as a parent of the <MatchInfo>-element.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="meta" timestamp="1474366617343">
<Match active="1" booked="1" matchid="1103193438" status="paused">
...
<Betpal>
<MatchInfo>
.......
<type id="1"/>
</MatchInfo>
<Betpal>
</Match>
</BetradarLiveOdds>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
BetPal/Type	Id	This ID represents what type of BetPal information that is made available.	Int: 1= "followTrading" 2= "followEvents" 3= "manual trading"

BR LiveOdds/followTrading: With this setting you will get both events and odds control from Betradar Live Odds. If you don’t adjust any odds control input (e.g. slider), the odds will be identical to Live Odds. Adjust slider in the BetPal applications to take a position in the market.
BR event data/followEvents: This setting only gets events from Live Odds or Live Data, no odds control with the exception of betstart and betstop. This means you will have to manually set starting odds, settle markets, etc.
Manual trading: Both odds control and entering events have to be done manually.

(ID: 131) Include statusid attribute in Match element

The match status is sent as a string in the status attribute. In order to make it more machine-readable a statusid is included when enabled.

XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" timestamp="1495003850487" status="change">
<Match matchid="11360959" status="not_started" statusid="0" active="1" betstatus="stopped" clock_stopped="0" score="-:-" msgnr="1" />
</BetradarLiveOdds>

Page tree

LO - XML configuration

Include Live Odds probabilities

Live Odds probability precision

(ID: 4) Include response reply number for error, current and scoreandcardsummary messages

(ID: 84) Include response reply number in meta messages

(ID: 8) Enable response on register and unregister requests

(ID: 88) Include autotraded attribute in meta messages

(ID: 24) Include extra sport info in meta messages

(ID: 82) Include streaming info in meta messages

(ID: 90) Include coverage info in meta messages

(ID: 126) Include covered from in meta messages

(ID: 12) Include non-booked matches in meta messages

(ID: 13) Include clock stopped information for sports that supports this

(ID: 14) Send irrelevant change message for changes that aren’t of interest

(ID: 21) Don’t send updates for inactive bettypes except the deactivation

(ID: 22) Send bet clearings even if match is not active

(ID: 16) Use additional match statuses for overtime

(ID: 23) Use additional match statuses for walkover / retired

(ID: 48) Use match status abandoned

(ID: 11) Send manual odds changes immediately

(ID: 18) Show current period score during period

(ID: 30) Split set scores

(ID: 44) Include suspension counters in feed

(ID: 29) Mark most balanced odds

(ID: 55) Include typeid in oddsfield tag

(ID: 63) Include playerid in oddsfield tag

(ID: 93) Include playerid in score and card event

(ID: 15) Include after overtime and after penalty score in score summary

(ID: 94) Send error message on failed bookmatch requests

(ID: 72) Include betstop reason

(ID: 102) Send empty meta response

(ID: 20) Show period scores in all sports

(ID: 123) Send clearbet message for any draw no bet, home no bet and away no bet market in caseof a refund

(ID: 125) Include BetPal info in meta messages

(ID: 131) Include statusid attribute in Match element

(ID: 123) Send clearbet message for any draw no bet, home no bet and away no bet market in case
of a refund