Betradar Documentation

Betradar - the betting arm of Sportradar

Page tree

Versions Compared

Old Version 4

changes.mady.by.user Kevin Langner

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 eIce Hockey.

Table of Contents

Match statuses in eIce Hockey

Table Filter
inverse
sparkNameSparkline
limitHeight
separatorPoint (.)
labels
default
cell-width
datepatterndd M yy
globalFiltertrue
id1584430573099_-1274492040
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
IdMatch statusDescriptionAdditional information
0NOT_STARTEDNot started yet-
1FIRST_PERIOD1st period-
301FIRST_PAUSEFirst intermissionThe value of the info attribute of the 1013 event reads as FIRST INTERMISSION
2SECOND_PERIOD2nd period-
302SECOND_PAUSESecond intermissionThe value of the info attribute of the 1013 event reads as SECOND INTERMISSION
3THIRD_PERIOD3rd period-
100ENDEDMatch has ended-
32AWAITING_OTWaiting for overtime to start

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

40OVERTIMEOvertime (in case the match goes to extra time)-
110AFTER_OTMatch finished after overtime

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

34AWAITING_PENALTIESWaiting for penalty shoot-out to start

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

50PENALTY_SHOOTINGPenalty shoot-out-
120AFTER_PENALTIESMatch finished after penalty shoot-out

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

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 eIce Hockey

Table Filter
inversefalse
sparkNameSparkline
limitHeight
sortID ⇧
separatorPoint (.)
labels
default
isFirstTimeEntertrue
cell-width
datepatterndd M yy
globalFiltertrue
id1592283786572_166993910
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
IDEventDescriptionCoverageextrainfoextrainfoicehockey
30GoalSent when the goal is confirmed.

iScout (BC)

Possible values:

  • 0 = Unknown
  • 7 = Even strength
  • 8 = Power play
  • 9 = Short handed
  • 11 = Empty net

43SuspensionTemporary player suspension (called "penalty" in ice hockey) .Triggered whenever a player is sent off due to a foul.iScout (BC)

Number of minutes the player is suspended for.

Penalty type. Possible
values:

  • -1 = Unknown
  • 1 = Minor
  • 2 = Major
  • 3 = Misconduct
110PossessionPuck possession. Puck possession indicates which team is currently in possession of the puck.iScout (BC)--
161Penalty shot awardedPenalty shot has been awardediScout (BC)--
666Penalty shot missedPenalty shot has been missediScout (BC)--
1002 Penalty Shoot-out EventPenalty to be taken. Updated with result of penalty after it is taken.

iScout (BC)

Result of penalty. Possible
values:

  • -1 = Not taken yet
  • 0 = Miss
  • 1 = Goal
-
1010Betstart

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

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.

iScout (BC)--
1013Matchstatus

Sent when the status of the match changes.

iScout (BC)See the above table for all available match statuses in eIce Hockey.-
1015Free textFree text message. Free comment is used for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..iScout (BC)--
1018 Possible goalPossible goal. Is sent either at the moment when the goal is scored, or before when probability for goal is high.iScout (BC)--
1019 Canceled goal

Possible goal is not confirmed.

iScout (BC)

Possible values:

  • 0 = Unknown
  • -1 = Not specified
  • 2 = Foul
  • 3 = Incorrect entry
  • 5 = Play stopped
-
1024Match about to start

This event is sent when
both captains, together with the referee, are selecting which team will start the game.

iScout (BC)--
1035Timeout

A team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too.

iScout (BC)

--
1036Time start/stopTime is stopped or startediScout (BC)

Possible value:

  • 1 = Time started
  • 0 = Time stopped
-
1039Manual time adjustmentAdd or remove seconds from period time, used if current time is incorrectiScout (BC)

Number of seconds adjusted. Either a positive or a negative integer.

-
1042 Possible penalty shotPossible penalty shot. Used when there is a strong possibility of a penalty shot.iScout (BC)--
1043Canceled penalty shotPossible penalty shot was not confirmed. Can potentially come after "Possible penalty" (1042).iScout (BC)--
1044Delete alertEvent has been deleted. Manual removal of an event.iScout (BC)

Id of event that was deleted.

-
1047Timeout overTimeout overiScout (BC)--
1049

Suspension over

Temporary player suspension (called "penalty" in ice hockey) over. Sent when suspended player returns on ice.iScout (BC)--
1050 Possible empty net situation

Sent one team chooses to play without a goal keeper and instead have 1 extra player attacking.

iScout (BC)--
1051Empty net situationEmpty net situation confirmed. Used whenever a possible empty net situations is being confirmed.iScout (BC)--
1052Empty net situation overEmpty net situation resolved. Used whenever an empty net situation has been resolved and goal keeper is back on ice.iScout (BC)--
1053 Empty net situation canceledPossible empty net turns out to not be an empty net. Used whenever a possible empty net is not being confirmed.iScout (BC)--
1064Play resumes after goalPlay resumes after goal. This is used to confirm that game has resumed after the scored goal.iScout (BC)--
1091 Early betstatus

Similar to normal betstart
and betstop, but instead of waiting until the next kick off, the early betstarts already starts right after the goal was confirmed. This event needs to be enabled before it gets sent out.

iScout (BC)

Possible values:

  • 1 = Early betstart
  • 0 = Early betstart ended
-
1102Coverage statusScout match coverage status. Coverage abandoned status means that coverage is stopped after it had already been started. Match will not be covered status means that match was supposed to be covered but coverage has been cancelled before.iScout (BC)

Possible values:
0 = Covered
1 = Coverage abandoned
2 = Match will not be covered

-
1104 Penalty shootout starting teamSet which team that starts the penalty shootoutiScout (BC)--
1416Possible suspensionTriggered when the possibility of a suspension ("Possible Penalty" in Ice Hockey) is high.iScout (BC)--
1418Canceled penaltyHappens after possible suspension event if the suspension is not confirmediScout (BC)--
1437 TV timeoutTV timeout

iScout (BC)

--
1438 TV timeout overTV timeout overiScout (BC)--
1521 Delayed penaltyDelayed penaltyiScout (BC)--
1885Puck positionPosition of the puck on the rink in x/y coordinates.iScout (BC)--

Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for eIce Hockey 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 t2name="JELTY / GABOREVER" t2id="12548382" t1name="IFARIS / DJ VAN" t1id="12548386" start="1607947860000" matchid="24699457" feedtype="full" extrainfo="0" betstatus="BETSTOP" connectionstatus="0" device="4" coveredfrom="venue" timerunning="0">
...
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
Matchextrainfo

Integer specifying special information for the match.

Integer. Possible values:

Match formatID until 01 February 2021ID from 01 February 2021 onwards
3 x 4 minutes

65

0
3 x 3 minutes6776
timerunningWhether the time is running.

Integer.

  • 1 = Time is running
  • 0 = Time is not running

Elements in the <match> element

Code Block
languagexml
titleXML example
<match t2name="TEAM HOCKEY 2" t2id="16188772" t1name="TEAM HOCKEY 1" t1id="16188770" start="1607934840000" matchid="24887124" feedtype="full" extrainfo="76" betstatus="BETSTOP" connectionstatus="0" device="4" coveredfrom="venue" timerunning="0" st1id="759382" st2id="759384" matchtime="00:00" sportid="195" stime="1607949202456">
<status start="0" name="NOT_STARTED" id="0"/>
<score type="current" t2="0" t1="0"/>
<suspensions t2="0" t1="0"/>
<iceconditions name="UNKNOWN" id="0"/>
<events/>
<tournament name="eHockey Test" id="97624"/>
<category name="Other" id="2270"/>
<sport name="eIce Hockey" id="195"/>
</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:

Score change (30)

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:

  • current
  • period1
  • period2
  • period3
  • overtime
  • penalties
suspensions

This element always gets included in full feed, and in the delta feed for the following events: Suspension (43), Suspension over (1049)

t1

Amount of suspensions home team.

Integer
t2Amount of suspensions away team.Integer
possession

This element always gets included in full feed (DC matches only), and in the delta feed (DC matches only) for the following events: Possession (110)

teamWhich team has possession.

String. Possible values:

  • "home"
  • "away"
iceconditions

This element always gets included in full feed, and in the delta feed for the following events: Ice conditions (1769)

idIdentifier for the surface types.Integer
name

Textual representation of the surface types. Note that this elements needs to be enabled in the XML configuration section.

String. Possible combinations of id name are:

  • 0 = Unknown
  • 1 = Good
  • 2 = Medium
  • 3 = Poor

Attributes in the <event> element

Code Block
languagexml
titleXML example
<match matchid="24699457" feedtype="delta" betstatus="BETSTOP" connectionstatus="1" timerunning="0">
<possession team="home"/>
<events>
<event type="30" stime="1607949322669" side="home" mtime="02:05" info="Goal [T1] (even strength)" id="2166032724" uuid="c6a62084-7ae2-439b-af29-2eec15fea4b8" extrainfo="7" matchscore="1:0" remainingtimeperiod="17:55" periodnumber="1" matchstatus="FIRST_PERIOD"/>
</events>
</match>

<match matchid="24699457" feedtype="delta" betstatus="STARTED" connectionstatus="1" timerunning="0">
<possession team="away"/>
<events>
<event type="43" stime="1607949373625" side="home" mtime="02:15" info="[T1] got a 2 minute minor penalty" id="2166032734" uuid="c2ce3260-5847-4833-93a7-4344c25f1af6" extrainfo="2" matchscore="1:0" remainingtimeperiod="17:45" periodnumber="1" matchstatus="FIRST_PERIOD"/>
</events>
<suspensions t2="0" t1="1"/>
</match>

XML attributes definition

ElementAttributes

AttributeDescriptionPossible values
eventextrainfo

Attribute containing additional information about the event.

Long
posx

Horizontal position on pitch, posx being a number from 0 to 100. The reference point 0 is at home teams goal.

Number
posy

Vertical position on pitch , posy being a number from 0 to 100. The reference point 0 is on top of pitch when home teams goal is on the left hand side.

Number
matchscoreScore for current match.

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

remainingtimeperiodRemaning time of the period.String. Format: "MM:SS"
periodnumberNumber of current period in match.Integer
extrainfoicehockey

Attribute containing additional information about the event.

String

XML configurations

Please note that eIce Hockey uses the same Live Data XML Feed Configs as specified in LD - Ice hockey (not all will have an effect on eIce Hockey data output).

Back to top