Betradar - the betting arm of Sportradar
Betradar - the betting arm of Sportradar
Sport specific information for ice hockey.
Match statuses in ice hockey
Id | Match status | Description | Additional information |
---|---|---|---|
0 | NOT_STARTED | Not started yet | - |
1 | FIRST_PERIOD | 1st period | - |
301 | FIRST_PAUSE | First intermission | The value of the info attribute of the 1013 event reads as FIRST INTERMISSION |
2 | SECOND_PERIOD | 2nd period | - |
302 | SECOND_PAUSE | Second intermission | The value of the info attribute of the 1013 event reads as SECOND INTERMISSION |
3 | THIRD_PERIOD | 3rd period | - |
100 | ENDED | Match has ended | - |
32 | AWAITING_OT | Waiting for overtime to start | This match status is only sent if the corresponding XML configuration is enabled. |
40 | OVERTIME | Overtime (in case the match goes to extra time) | - |
110 | AFTER_OT | Match finished after overtime | This match status is only sent if the corresponding XML configuration is enabled. |
34 | AWAITING_PENALTIES | Waiting for penalty shoot-out to start | This match status is only sent if the corresponding XML configuration is enabled. |
50 | PENALTY_SHOOTING | Penalty shoot-out | - |
120 | AFTER_PENALTIES | Match finished after penalty shoot-out | This match status is only sent if the corresponding XML configuration is enabled. |
80 | INTERRUPTED | The match has been interrupted | - |
90 | ABANDONED | The match has been abandoned | This match status is only sent if the corresponding XML configuration is enabled. |
Events in ice hockey
ID | Event | Description | Coverage | extrainfo | extrainfoicehockey | player1 | player2 |
---|---|---|---|---|---|---|---|
30 | Goal | Sent when the goal is confirmed. | Hardphone (BC) iScout (BC + DC) XSA (DC) | Possible values:
Please note that device iScout can only send extrainfo 7,8,9 and 11. Extrainfoicehockey is | Second goal type, if
| Player who scored the goal | Id of the assisting player, if available. |
43 | Suspension | Temporary player suspension (called "penalty" in ice hockey) .Triggered whenever a player is sent off due to a foul. | Hardphone (BC) iScout (BC + DC) XSA (DC) | Number of minutes the | Penalty type. Possible
| Id of the penalized player. Only added if available. | |
110 | Possession | Puck possession. Puck possession indicates which team is currently in possession of the puck. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
155 | Shot on target | Happens whenever there is shot on a goal. Entries are assigned to teams. | XSA (DC) | - | - | Id of shooting player | - |
156 | Shot off target | Happens whenever there is a shot off a goal. Entries are assigned to teams. | XSA (DC) | - | - | Id of shooting player | - |
157 | Goalkeeper save | Goalkeeper has made a save | XSA (DC) | - | - | Id of goalkeeper | - |
161 | Penalty shot awarded | Penalty shot has been awarded | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | Id of the player taking the penalty shot. | Id of the offender. |
172 | Shot blocked | Shot towards goal gets blocked (not by the goalkeeper) | XSA (DC) | - | - | Id of shooting player | Id of blocking player |
666 | Penalty shot missed | Penalty shot has been missed | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | Id of the player taking the penalty shot. | - |
1002 | Penalty Shoot-out Event | Penalty to be taken. Updated with result of penalty after it is taken. | iScout (BC + DC) XSA (DC) | Result of penalty. Possible
| - | Id of player taking shooting the penalty. | - |
1010 | Betstart | 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 + DC) XSA (DC) | - | - | - | - |
1011 | Betstop | 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 | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1013 | Matchstatus | Sent when the status of the match changes. | Hardphone (BC) iScout (BC + DC) XSA (DC) | See the above table for all available match statuses in ice hockey. | - | - | - |
1015 | Free text | Free 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.. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1018 | Possible goal | Possible goal. Is sent either at the moment when the goal is scored, or before when probability for goal is high. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1019 | Canceled goal | Possible goal is not confirmed. | Hardphone (BC) iScout (BC + DC) XSA (DC) | Possible values:
| - | - | - |
1024 | Match about to start | This event is sent when | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1035 | Timeout | A team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too. | iScout (BC + DC) XSA (DC) | - | - | - | - |
1036 | Time start/stop | Time is stopped or started | Hardphone (BC) iScout (BC + DC) XSA (DC) | Possible value:
| - | - | - |
1039 | Manual time adjustment | Add or remove seconds from period time, used if current time is incorrect | Hardphone (BC) iScout (BC + DC) XSA (DC) | Number of seconds adjusted. Either a positive or a negative integer. | - | - | - |
1042 | Possible penalty shot | Possible penalty shot. Used when there is a strong possibility of a penalty shot. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1043 | Canceled penalty shot | Possible penalty shot was not confirmed. Can potentially come after "Possible penalty" (1042). | iScout (BC + DC) | - | - | - | - |
1044 | Delete alert | Event has been deleted. Manual removal of an event. | Hardphone (BC) iScout (BC + DC) XSA (DC) | Id of event that was deleted. | - | - | - |
1047 | Timeout over | Timeout over | iScout (BC + DC) XSA (DC) | - | - | - | - |
1049 | Suspension over | Temporary player suspension (called "penalty" in ice hockey) over. Sent when suspended player returns on ice. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | Id of the penalized player. Only added if available. | - |
1050 | Possible empty net situation | Sent one team chooses to play without a goal keeper and instead have 1 extra player attacking. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1051 | Empty net situation | Empty net situation confirmed. Used whenever a possible empty net situations is being confirmed. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1052 | Empty net situation over | Empty net situation resolved. Used whenever an empty net situation has been resolved and goal keeper is back on ice. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1053 | Empty net situation canceled | Possible empty net turns out to not be an empty net. Used whenever a possible empty net is not being confirmed. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1064 | Play resumes after goal | Play resumes after goal. This is used to confirm that game has resumed after the scored goal. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1091 | Early betstatus | Similar to normal betstart | Hardphone (BC) iScout (BC + DC) XSA (DC) | Possible values:
| - | - | - |
1102 | Coverage status | Scout 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. | Hardphone (BC) iScout (BC + DC) XSA (DC) | Possible values: | - | - | - |
1104 | Penalty shootout starting team | Set which team that starts the penalty shootout | Hardphone (BC) iScout (BC + DC) | - | - | - | - |
1112 | Stop match | Sent when the match is stopped. | XSA (DC) | Reason. Possible values:
| - | - | - |
1113 | Stop match ended | Match resumes after being stopped. | XSA (DC) | - | - | - | - |
1126 | Attack | Used when puck is in opponent's third of the rink | XSA (DC) | - | - | - | - |
1416 | Possible suspension | Triggered when the possibility of a suspension ("Possible Penalty" in Ice Hockey) is high. | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1418 | Canceled penalty | Happens after possible suspension event if the suspension is not confirmed | Hardphone (BC) iScout (BC + DC) XSA (DC) | - | - | - | - |
1437 | TV timeout | TV timeout | iScout (BC + DC) XSA (DC) | - | - | - | - |
1438 | TV timeout over | TV timeout over | iScout (BC + DC) XSA (DC) | - | - | - | - |
1458 | Video review | Video review | XSA (DC) | - | Current score (under | - | - |
1459 | Video review over | Video review over | XSA (DC) | Outcome. Possible values:
| Current score (under | - | - |
1521 | Delayed penalty | Delayed penalty | iScout (BC + DC) | - | - | - | - |
1768 | Hit | Player hits/body checks an opposing player. Hit is action event when a player from one team hits/body checks a player from the opposing team. The player initiating the contact is the player who gets credit for the hit. | XSA (DC) | - | - | Id of hitting player | Id of hit player |
1769 | Ice conditions | Conditions of the ice being played on | XSA (DC) | Ice conditions. Possible
| - | - | - |
1770 | Stoppage | Play is stopped during the game. | XSA (DC) | Stoppage reason. Possible
| - | - | - |
1771 | Faceoff | Faceoff for puck possession. The two teams line up in opposition to each other, and the opposing skaters attempt to gain control of the puck after it is dropped between their stick by an official. | XSA (DC) | Whether this faceoff is
| Zone in which the faceoff takes place. Value: Integer between 0-8, enumerating the different faceoff zones on the rink. Please note: An illustration of these values related to the location on the field is available at the end of this table. | Id of home team player in the faceoff. | Id of away team player in the faceoff. |
1772 | Puck safe | Used when an attack is over, i.e. the puck is not in opponent's third | XSA (DC) | - | - | - | - |
1885 | Puck position | Position of the puck on the rink in x/y coordinates. | iScout (BC + DC) XSA (DC) | - | - | - | - |
Illustration of event 1771 positions
Sport specific XML elements and attributes
This section explains what elements / attributes one can expect for ice 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
<match betstatus="BETSTOP" connectionstatus="0" dc="1" device="3" extrainfo="0" feedtype="full" matchid="10115268" matchtime="00:00" start="1464790020000" t1id="5577563" t1name="VSV II" t2id="5273264" t2name="EV AICALL ZELTWEG" timerunning="0"> ... </match>
XML elements and attributes definition
Element | Attributes | ||
---|---|---|---|
Attribute | Description | Possible values | |
Match | extrainfo | Integer specifying special information for the match. | Integer. Possible values:
|
timerunning | Whether the time is running. | Integer.
|
Elements in the <match> element
<match betstatus="BETSTOP" connectionstatus="0" dc="1" device="3" extrainfo="0" feedtype="full" matchid="10115268" matchtime="00:00" start="1464790020000" t1id="5577563" t1name="VSV II" t2id="5273264" t2name="EV AICALL ZELTWEG" timerunning="0"> <status id="90" name="ABANDONED" start="1464790489666"/> <score t1="0" t2="0" type="current"/> <suspensions t1="1" t2="0"/> <possession team="home"/> <iceconditions id="0" name="UNKNOWN"/> <openingfaceoff1stperiod team="home"/> <openingfaceoff2ndperiod team="away"/> <openingfaceoff3rdperiod team="home"/> <openingfaceoffovertime team="away"/> <tournament id="4037" name="Oberliga"/> <category id="65" name="Austria"/> <sport id="4" name="Ice Hockey"/> <events/> </match>
XML elements and attributes definition
Element | Attributes | ||
---|---|---|---|
Attribute | Description | Possible 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) | ||
t1 | Amount of points home team. | Integer | |
t2 | Amount of points away team. | Integer | |
type | For what period in the match the points were scored. | String. Possible values:
| |
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 | |
t2 | Amount 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) | ||
team | Which team has possession. | String. Possible values:
| |
iceconditions | This element always gets included in full feed, and in the delta feed for the following events: Ice conditions (1769) | ||
id | Identifier 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:
| |
openingfaceoff1stperiod | This element always gets included in full feed, and in the delta feed for the following events: Faceoff (1771) | ||
team | Which team opened in the first faceoff. Note that this elements needs to be enabled in the XML configuration section. | Integer. Possible values:
| |
openingfaceoff2ndperiod | This element always gets included in full feed, and in the delta feed for the following events: Faceoff (1771) | ||
team | Which team opened in the second faceoff. Note that this elements needs to be enabled in the XML configuration section. | Integer. Possible values:
| |
openingfaceoff3rdperiod | This element always gets included in full feed, and in the delta feed for the following events: Faceoff (1771) | ||
team | Which team opened in the third faceoff. Note that this elements needs to be enabled in the XML configuration section. | Integer. Possible values:
| |
openingfaceoffovertime | This element always gets included in full feed, and in the delta feed for the following events: Faceoff (1771) | ||
team | Which team opened in the OT faceoff. Note that this elements needs to be enabled in the XML configuration section. | Integer. Possible values:
|
Attributes in the <event> element
<!-- Example 1 --> <match matchid="9548197" ... > <events> <event extrainfo="7" id="649201877" info="Goal [T2] (even strength)" matchscore="2:3" mtime="14:45" periodnumber="1" remainingtimeperiod="05:15" side="away" stime="1465519931270" type="30"/> </events> </match> <!-- Example 2 --> <match matchid="9548197" ... > <events> <event id="649208863" info="Puck position" matchscore="2:3" mtime="20:45" periodnumber="2" posx="75" posy="40" remainingtimeperiod="19:15" side="home" stime="1465521702900" type="1885"/> </events> </match> <!-- Example 3 --> <match matchid="9548197" ... > <events> <event extrainfo="2" extrainfoicehockey="-1" id="649241223" info="[T2] got a 2 minute minor penalty" matchscore="2:4" mtime="59:55" periodnumber="3" remainingtimeperiod="00:05" side="away" stime="1465527618922" type="43"/> </events> </match>
XML attributes definition
Element | Attributes | ||
---|---|---|---|
Attribute | Description | Possible values | |
event | extrainfo | 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 | |
player1 | Sportradar player id for player 1 connected to this event. | Integer | |
player2 | Sportradar player id for player 2 connected to this event. | Integer | |
matchscore | Score for current match. | String. Format: "[home]:[away]" Example: "1:0" | |
remainingtimeperiod | Remaning time of the period. | String. Format: "MM:SS" | |
periodnumber | Number of current period in match. | Integer | |
extrainfoicehockey | Attribute containing additional information about the event. | String |
XML configurations
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: 6) Icehockey OT/Pen matchstatuses
Enabling this setting will add the following possible match statuses for ice hockey matches:
- AWAITING_OT
- AFTER_OT
- AWAITING_PENALTIES
- AFTER_PENALTIES
(ID: 44) Send lineups for ice hockey matches where this is available
If this setting is enabled, the element <lineups> gets enabled for ice hockey matches which have this configured. Lineups are sent when subscribing to a match, and when the lineup changes.
<lineups matchid="6856980"> <player id="215564" name="Crosby, Sidney" shirtnumber="5" substitute="false" team="1"/> <player id="412234" name="Hull, Bobby" shirtnumber="7" substitute="false" team="0"/> <!-- Remaining message truncated --> </lineups>
(ID: 40) Include attribute extrainfoicehockey
If this setting is enabled, an additional attribute extrainfoicehockey will be added to the <event> element for events which support this in ice hockey matches. The value of this attribute is explained in the event list.
<event extrainfo="2" extrainfoicehockey="2" id="469535552" info="[T1] got a 2 minute minor penalty" matchscore="0:0" mtime="60:38" periodnumber="4" player1="31502" remainingtimeperiod="04:22" side="home" stime="1447850531168" type="43"/>
(ID: 42) Include extra ice hockey match elements
Enabling this setting will add child elements to the <match> element in ice hockey, describing the ice conditions and opening faceoff winning teams for each period.
<match betstatus="BETSTOP" connectionstatus="1" dc="1" distance="0" extrainfo="0" feedtype="full" matchid="1103190023" matchtime="60:18" start="1447854123000" t1id="1427444" t1name="SILUTE" t2id="1505358" t2name="VILKAI" timerunning="1"> <status id="40" name="OVERTIME" start="1447853377509"/> <possession team="away"/> <score t1="0" t2="0" type="current"/> <suspensions t1="0" t2="0"/> <iceconditions id="1" name="GOOD"/> <openingfaceoff1stperiod team="1"/> <openingfaceoff2ndperiod team="2"/> <openingfaceoff3rdperiod team="1"/> <openingfaceoffovertime team="2"/> <tournament id="5" name="Eliteserien"/> <category id="5" name="Norway"/> <sport id="4" name="Ice Hockey"/> <events> <!-- events go here --> </events> </match>
(ID: 20) Include goals scored during penalty shootout in the "current" score for ice hockey
If activated the XML element score type="current" will include goals scored during penalty shootout for ice hockey.
(ID: 63) Send periodx score types for ice hockey
The attribute type in the <score> element (subelement from <match> element) has a set list of possible values. If this setting is enabled, the attribute type can have one of the following values, in addition to the regular values for ice hockey matches:
- period1
- period2
- period3
<match matchid="7440630" ... > <score t1="14" t2="20" type="period1"/> <!-- Remaining message truncated --> </match>
(ID: 77) Enable puck spotting ice hockey
Enabling this setting will include the puck position event (1885) in ice hockey matches.
(ID: 134) Include early betstatus in ice hockey
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 you to enable early betstart. If you have this setting enabled, information related to early betstart will be sent in addition to the normal betstart information.
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 the match is in either betstart or early betstart, 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.
(ID: 129) Include play resumes after goal in ice hockey
Enabling this setting will allow event 1064 (play resumes after goal) to be sent.
(ID: 87) Include players 3 and 4
Enabling this setting will include player3 and player4 attribute for events which have this available. A list of events currently supporting this can be found below. Please keep in mind that this list might expand, the client software should be able to handle that additional events might be added.
<match matchid="10115268" ... > ... <events> <event extrainfo="0" id="15984095" info="Goal [T1] -B.Maxwell" matchscore="2:0" mtime="00:54" periodnumber="1" player1="42390" player2="29525" player3="30509" side="home" stime="1474041000979" type="30"/> </events> </match>