Page History

Panel

Sport specific information for futsal.

Table of Contents

Sport specific XML elements and attributes

This section explains what elements/attributes one can expect for futsal matches in addition to the standard elements and attributes.

Code Block

language	xml
title	XML example

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1287056116518">
<Match active="1" betstatus="stopped" clock_stopped="1" earlybetstatus="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	clock_stopped	Whether the clock is running or the clock is stopped. This attribute needs to be enabled in the XML configuration.	Integer 1 = Clock is stopped 0 = Clock is running
	suspendHome	The amount of suspensions for the home team. This attribute needs to be enabled in the XML configuration.	Number >= 0
	suspendAway	The amount of suspensions for the away team. This attribute needs to be enabled in the XML configuration.	Number >= 0
	setscores	Period_1 - Period_2 (aggregated score of all overtime sequences - score of penalty shooutout) So maximum up to 5 scores while 3 and 4 are optional in case of overtime and/or penalty shootout.	String For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

XML configuration

Sport specific XML configurations for futsal.

(ID:51) Multiple bets of same type active at once for futsal matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and 3.5 would be sent as well.

(ID: 58) Early bet status in futsal

Enabling this setting will trigger an early betstart if a betstop has been set because a goal was scored.

Right before one of the teams scores a goal, the match status will be set to betstop. Normally, the match will be on betstop until the match continues, which is after the next kick off.

As bookmakers have different requirements in terms of reoffering markets after goals, Betradar allows clients to enable early betstart. Enabling this setting will send information related to early betstart in addition to the normal betstart information. This information gets passed through an attribute earlybetstatus in the Match element, in addition to the regular betstatus attribute.

The behaviour of early betstart is quite similar to the normal betstart, but instead of waiting until the next kick off, early betstart already starts right after the goal was confirmed.

If one or both of the betstatus and earlybetstatus are set to "started" the match can be treated as betstart. It is up to the bookmaker to decide whether to receive the new prices right after the score change or after the match continues.

Code Block

language	xml
title	XML example - During the match

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1395839620340" type="scoutmatch">
<Match active="1" betstatus="started" earlybetstatus="stopped" matchid="1271072" matchtime="1" msgnr="10755" score="1:0" setscore1
="1:0" status="1p" />
</BetradarLiveOdds>

(ID: 136) Add new attribute with extended matchtime info for Futsal

When this is activated a new attribute matchetime_extended will be included in the match element, showing more detailed matchtime information.

Code Block

language	xml
title	XML examples

<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1199777649605">
<Match betstatus="started" matchid="4761252" matchtime="41" matchtime_extended="40:48" active="1" msgnr="88" score="0:0" setscores=
"0:0" status="1p">
</BetradarLiveOdds>


<BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1199777659034">
<Match betstatus="started" matchid="4761252" matchtime="45" matchtime_extended="45:00 +02:30" active="1" msgnr="88" score="0:0"
setscores="0:0" status="1p">
</BetradarLiveOdds>

Match statuses

ID	Status	Status description	Additional information
0	not_started	Not started yet	-
6	1p	1st period of the match	-
31	paused	Match pause	-
7	2p	2nd period of the match	-
100	ended	The match has ended	-
32	awaiting_ot	Waiting for overtime to start	Status controlled by XML configuration.
41	1p_ot	1st overtime period	-
33	ot_ht 1p_ot	Pause between 1st and 2nd overtime period	Status controlled by XML configuration.
42	2p_ot	2nd overtime period	-
110	after_ot	Match finished after overtime	Status controlled by XML configuration.
34	awaiting_pen	Waiting for penalty shoot-out to start	Status controlled by XML configuration.
50	pen	Penalty shoot-out	-
120	ended	The match has ended after penalties	-
80	interrupted	The match has been interrupted	-
90	abandoned	The match has been abandoned	Status controlled by XML configuration.

Page tree

Versions Compared

Old Version 5

New Version Current

Key

Sport specific XML elements and attributes

XML configuration

(ID:51) Multiple bets of same type active at once for futsal matches

(ID: 58) Early bet status in futsal

(ID: 136) Add new attribute with extended matchtime info for Futsal

Match statuses