Betradar Documentation

Betradar - the betting arm of Sportradar

Page tree

Versions Compared

Old Version 8

changes.mady.by.user Espen Grinde

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Langner

Saved on

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 table tennis.

Table of Contents

Match statuses in table tennis

Table Filter
inverse
sparkNameSparkline
limitHeight
separatorPoint (.)
labels
default
cell-width
datepatterndd M yy
globalFiltertrue
id1584430959577_-1274492040
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-
305FIFTH_PAUSE5th pause-
441SIXTH_SET6th set-
306SIXTH_PAUSE6th pause-
442SEVENTH_SET7th 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

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

98DEFAULTED2

The home team won because the away team defaulted

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

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 table tennis

Table Filter
inversefalse
sparkNameSparkline
limitHeight
sortID ⇧
separatorPoint (.)
labels
default
isFirstTimeEntertrue
cell-width
datepatterndd M yy
globalFiltertrue
id1592284765133_-1555191189
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 the above table for available match statuses for table tennis--
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)

---
 1022Who serves first Information about the player who will start to serve.

Hardphone (BC)

iScout (BC)

---
 1024Match about to startIndicates that the match will start soon

Hardphone (BC)

iScout (BC)

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

Hardphone (BC)

iScout (BC)

---
1035Time outA team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too.

Hardphone (BC)

iScout (BC)

---
1040Possible red cardUsed when there is a strong possibility of a red card. Entries are assigned to teams. Note that the possible red card could also be a possible yellow/red card. 

Hardphone (BC)

iScout (BC)

---
1041Red card not confirmedUsed when possible red card is not being confirmed. Note that the cancelled red card could also be a cancelled yellow/red card.

Hardphone (BC)

iScout (BC)

---
1044Deleted event alert

Manual removal of an event.

Hardphone (BC)

iScout (BC)

Id of event that was deleted.--
1047Time out over

Time out is over

iScout (BC)---
1084Possible yellow cardUsed when there is a strong possibility of a red card. Entries are assigned to teams.

Hardphone (BC)

iScout (BC)

---
1085Yellow card not confirmedUsed when a possible yellow card is not being confirmed.

Hardphone (BC)

iScout (BC)

---
 1102 Coverage status Sent when the coverage status for the match changesHardphone (BC)

Possible values:

  • 0 = Covered
  • 1 = Coverage abandoned
  • 2 = Match will not be covered
--
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)

---
1161Score changeMatch and set score for table tennis.

Hardphone (BC)

iScout (BC)

Possible values:

  • 0 = Standard
  • 1 = Expedite 13 returns
  • 2 = Service error
  • 3 = Red card
  • 4 = 1 point penalty
  • 5 = 2 points penalty


1176Expedite modeUsed when the match goes into expedite mode.

Hardphone (BC)

iScout (BC)

---
1177Table tennis violationViolation which triggers a yellow, red or yellowred card

Hardphone (BC)

iScout (BC)

Possible values:

  • 0 = Illegal service
  • 2 = Yellow card/warning
  • 3 = Yellowred card/penalty
  • 4 = Red card/disqualification
--
2052Yellowred card same handYellowred card held in the same hand, result of a violation. Results in 1 or 2 pt penalty.

Hardphone (BC)

iScout (BC)

---


Sport specific XML element and attributes

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

Attributes in the <match> element

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" matchid="10115414" matchtime="0:00:00"
numberofsets="5" start="1464858900000" t1id="7873737" t1name="KOZUL, DENI" t2id="8777358" t2name="GIARDI, FEDERICO">
...
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
Matchfirstserve

Which player has first serve of match.

Integer
numberofsets

How many sets are being played in the match.

Integer

Elements in the <match> element

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" matchid="10115414" matchtime="0:00:00"
numberofsets="5" start="1464858900000" t1id="7873737" t1name="KOZUL, DENI" t2id="8777358" t2name="GIARDI, FEDERICO">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0" t2="0" type="match"/>
<score t1="0" t2="0" type="set1"/>
<serve team="home"/>
<red t1="0" t2="0"/>
<yellow t1="0" t2="0"/>
<tournament id="53162" name="World Tour, Slovenia Open (CS) 2016, Boys"/>
<category id="88" name="International"/>
<sport id="20" name="Table tennis"/>
<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:

Table tennis full score (1161)

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"
red

This element always gets included in full feed, and in the delta feed for the following events: Red card (50)

t1Amount of red cards home team.Integer
t2Amount of red cards away team.Integer
yellow

This element always gets included in full feed, and in the delta feed for the following events: Yellow card (40)

t1Amount of yellow cards home team.Integer
t2Amount of yellow cards away team.Integer
matchproperties

This element always gets included, in both the full feed and the delta feed.

Best of

Determines number of games.  

Integer. Possible values:

  • 5 (Default value)

  • 7

Sudden death in last game

Determines if sudden death leg is played in last set or not.  

Integer. Possible values:

  • 0 (Default value) = no sudden death

  • 1 = sudden death

Attributes in the <event> element

Code Block
languagexml
titleXML example
<match matchid="9580413" ... >
<events>
<event extrainfo="0" id="650860221" info="1:0 [T1]" matchscore="0:0" mtime="0:00:16" server="away" setnumber="1" setscore="1:0"
side="home" stime="1465707710666" type="1161"/>
</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"

server

Who will serve next. Added for the following events: Table tennis score change (1161) and Expedite mode (1176)

String. Possible values:

  • home
  • away
  • none

XML configurations in Table tennis

(ID: 123) Include match status defaulted in Table tennis

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

Back to top