Betradar - the betting arm of Sportradar

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt Include
HideElements
HideElements
nopaneltrue
Anchor
topOfPage
topOfPage

Excerpt Include
BetradarLogo
BetradarLogo
nopaneltrue

Panel

Sport specific information for badminton.

Table of Contents

Match statuses in badminton

Table Filter
inverse
sparkNameSparkline
limitHeight
separatorPoint (.)
labels
default
cell-width
datepatterndd M yy
globalFiltertrue
id1584426746168_-1861531358
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
IDMatch statusDescriptionAdditional information
0NOT_STARTEDNot started yet-
8FIRST_SET1st set-
301FIRST_PAUSE1st pause-
9SECOND_SET2nd set-
302SECOND_PAUSE2nd pause-
10THIRD_SET3rd set-
303THIRD_PAUSE3rd pause-
11FOURTH_SET4th set-
304FOURTH_PAUSE4th pause-
12FIFTH_SET5th set-
100ENDEDThe match has ended-
93WALKOVER1

The home team won the match
by walkover

-
94WALKOVER2

The away team won the match
by walkover

-
95RETIRED1

The away team won because
the home team retired

-
96RETIRED2

The home team won because
the away team retired

-
97DEFAULTED1

The away team won because
the home team defaulted

-
98DEFAULTED2

The home team won because
the away team defaulted

-
61DELAYEDThe match start is delayed-
80INTERRUPTEDThe match has been interrupted-
90ABANDONEDThe match has been abandoned

This match status is only sent if the
corresponding XML configuration is
enabled.

Events in badminton

Table Filter
inversefalse
sparkNameSparkline
limitHeight
sortID ⇧
separatorPoint (.)
labels
default
isFirstTimeEntertrue
cell-width
datepatterndd M yy
globalFiltertrue
id1592282263115_-743545128
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
IDEventDescriptionCoverageextrainfoplayer1player2
40Yellow cardUsed when the yellow card is confirmed. 

Hardphone (BC)

iScout (BC)


Player who got the card-
50Red cardUsed when the red card is confirmed.

Hardphone (BC)

iScout (BC)


Player who got the card-
 1010Betstart

Betstart indicates that betting markets can be activated. Betstart is not only a pre match event but is also used during the match.

Hardphone (BC)

iScout (BC)


--
1011Betstop

Betstop indicates that all betting markets are closed due to strong possibility of a goal, penalty, red card, or there is any

unclear situation on the field. Betstop is also used whenever there is the need to establish direct communication between the scout and the match Supervisor, or in case of call disconnection.

Hardphone (BC)

iScout (BC)


--
 1013Match statusSent when the status of the match changes.


Hardphone (BC)

iScout (BC)

See table above for match statuses--
1015Free commentUsed for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..


Hardphone (BC)

iScout (BC)


--

 1022


Which team serves firstInformation about the player who will start to serve.


Hardphone (BC)

iScout (BC)

Possible values:

  • 0 = Covered
  • 1 = Coverage abandoned
  • 2 = Match will not be covered
--
1024Match about to startSent shortly before serving player takes the first serve.

Hardphone (BC)

iScout (BC)


--
1031Ball in playUsed when the service has been taken and the ball is in play.


Hardphone (BC)

iScout (BC)


--
1044Deleted event alertManual removal of an event.


Hardphone (BC)

iScout (BC)

Id of event that was deleted.--
 1102Coverage status

 Sent when the coverage status for the match changes


Hardphone (BC)
--
1112Match stop / suspensionSent when a match needs to be stopped.


Hardphone (BC)

iScout (BC)

Possible values:

  • 0 = Not specified
  • 1 = Weather conditions
  • 2 = Darkness
  • 3 = Injury
  • 4 = Floodlight failure
  • 5 = Person entering the field
  • 6 = Crowd control issue
  • 7 = Water break
  • 8 = Disciplinary issue 9 = Gone to TMO
  • 10 = Replacing ball 11 = Facility delay
  • 12 = Tactical time-out 13 = Drinks
--
1113Match stop / suspension overThe match resumes after being stopped.


Hardphone (BC)

iScout (BC)


--
1127Let Triggered whenever a play ends without awarding a point due to any unforeseen situation (e.g. serving player servers before receiving player is ready).

Hardphone (BC)

iScout (BC),


--

1141


Score changeInformation about the match score updated point by point.


Hardphone (BC)

iScout (BC)

Possible values:

  • 0 = Standard
  • 1 = Ace
  • 2 = Service error
  • 3 = Red card
--
1142Black cardBlack card status is used whenever a player is being disqualified. Common reasons are persistent or flagrant offence.-
Player who got the card-


Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for badminton matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.

Attributes in <match> element

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" firstserve="away" matchid="10115484" matchtime
="2:23:04" numberofsets="3" setlimit="21" st1id="87528" start="1464858600000" t1id="5261571" t1name="MATSUTOMO M /
TAKAHASHI A" t2id="6862483" t2name="RAHAYU A / SUGIARTO J F">
...
</match>

XML elements and attributes definition

Table Filter
id1584426739702_71814464
ElementsAttributes

AttributeDescriptionPossible values
Matchextrainfo

Integer specifying special information for the match.

Integer. Possible values:

  • 0 = Default
  • 28 = Best of 3 (first to 15)
  • 30 = Best of 5 (first to 11)
  • 40 = Best of 5 (first to 11, decider at 14-all)
  • 41 = Best of 5 (first to 11, 3 pt challenge
  • at 10-all)
firstserve

Which player has first serve of match.


setlimit

Please note that this attribute needs to be enabled in the XML configuration options.


numberofsets

How many sets are being played in the match.


Elements in <match> element

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" firstserve="away" matchid="10115484" matchtime="
2:23:04" numberofsets="3" setlimit="21" st1id="87528" start="1464858600000" t1id="5261571" t1name="MATSUTOMO M / TAKAHASHI A"
t2id="6862483" t2name="RAHAYU A / SUGIARTO J F">
<status id="100" name="ENDED" start="1464860478511"/>
<score t1="2" t2="0" type="match"/>
<score t1="21" t2="12" type="set1"/>
<score t1="21" t2="14" type="set2"/>
<serve team="home"/>
<black t1="0" t2="0"/>
<red t1="0" t2="0"/>
<yellow t1="0" t2="0"/>
<tournament id="53068" name="Indonesia Open (SS) 2016, Women Doubles"/>
<category id="259" name="International"/>
<sport id="31" name="Badminton"/>
<events/>
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
score

Multiple occurrences possible, each occurrence describes the amount of points for the specified period in the match. This element always gets included in full feed, and in the delta feed for the following events:

  • Badminton full score (1141)
t1Amount of points home team.Integer
t2Amount of points away team.Integer
type

For what period in the match the points were scored.

String. Possible values:

  • match
  • set1
  • set2
  • set3
  • set4
  • set5
serveThis element always gets included, in both the full feed and the delta feed.

teamWhich team served.

String. Possible values:
"home"
"away"

blackThis element always gets included, in both the full feed and the delta feed.
t1Amount of black cards home team.Integer
t2Amount of black cards away team.Integer
red

This element always gets included, in both the full feed and the delta feed.
t1Amount of red cards home team.Integer
t2Amount of red cards away team.Integer
yellow

This element always gets included, in both the full feed and the delta feed.
t1Amount of yellow cards home team.Integer
t2Amount of yellow cards away team.Integer

Attributes in <event> element

Code Block
languagexml
titleXML example
<match matchid="9577119" ... >
<events>
<event extrainfo="100" id="650847077" info="ENDED" matchscore="2:0" mtime="1:01:08" setnumber="2" setscore="21:17" side="none"
stime="1465704613813" type="1013"/>
</events>
</match>

XML attributes definition

ElementAttributes

AttributeDescriptionPossible values
eventextrainfo

Attribute containing additional information about the event.

Long
setnumber

The number of the current set in the match.

Integer
setscoreScore for current set.

String. Format: "[home]:[away]"
Example: "5:4"

matchscoreScore for current match.

String. Format: "[home]:[away]"
Example: "1:0"

XML configurations for badminton

This section explains what XML configurations one can expect for this sport in addition to the standard XML configurations, and what the meaning of these configurations is.

(ID: 29) Badminton set limit

If this setting is enabled, <match> elements for badminton matches will contain a setlimit attribute.

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" extrainfo="0" feedtype="full" matchid="7519874" numberofsets="3" setlimit="21" start="
1435452000000" t1id="1276433" t1name="ARENDS J / PIEK S" t2id="6444419" t2name="LEE C H R / CHAU H W">
<!-- Message truncated -->
</match>


(ID: 118) Use match statuses DEFAULTED

Enabling this setting will allow the system to send match statuses DEFAULTED1 and DEFAULTED2 for badminton.