📢 The Ask AI can now translate any part of the docs to your preferred language!
Read the guide
sportradar.comSportradar Support Portal

Ice Hockey

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
Special XML Attributes
player1
player2

30

Goal

Sent when the goal is confirmed.

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

Extrainfo: Possible values:

  • 0 = Unknown

  • -1 = Not specified

  • 1 = Penalty

  • 7 = Even strength

  • 8 = Power play

  • 9 = Short handed

  • 11 = Empty net

Please note that device iScout can only send extrainfo 7,8,9 and 11. Extrainfoicehockey is also not available from this device. Goal types are also not available for hardphone coverage - we only send extrainfo 0 "unknown" with every goal. Extrainfoicehockey: Second goal type, if available. Possible values:

  • 0 = Unknown

  • -1 = Not specified

  • 1 = Penalty

  • 7 = Even strength

  • 8 = Power play

  • 9 = Short handed

  • 11 = Empty net

Player who scored the goal

Id of the assisting player, if available.

40

Yellow card

A yellow card has been given.

This event is only used for International Short Hockey (ISH) matches.

iScout (BC)

Extrainfo: Possible values:

  • 1 = home

  • 2 = away

-

-

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)

Extrainfo: Number of minutes the player is suspended for. Extrainfoicehockey: Penalty type. Possible values:

  • -1 = Unknown

  • 1 = Minor

  • 2 = Major

  • 3 = Misconduct

Powerplay: Indicates if there is powerplay for a team

  • 0 = no powerplay,

  • 1 = home team powerplay,

  • 2 = away team powerplay.

Id of the penalized player. Only added if available.

45

YellowRed card

A red card has been given after two yellow cards.

This event is only used for International Short Hockey (ISH) matches.

iScout (BC)

Extrainfo: Possible values:

  • 1 = home

  • 2 = away

-

-

50

Red card

A red card has been given. This event is only used for International Short Hockey (ISH) matches.

iScout (BC)

Extrainfo: Possible values:

  • 1 = home

  • 2 = away

-

-

110

Possession

Puck possession. Puck possession indicates which team is currently in possession of the puck.

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

-

-

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 shooting player

-

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)

Extrainfo: Result of penalty. Possible values:

  • -1 = Not taken yet

  • 0 = Miss

  • 1 = Goal

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 direct communication between the scout and the match Supervisor, or in case of call disconnection.

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

-

-

-

1013

Matchstatus

Sent when the status of the match changes.

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

Extrainfo: 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)

Extrainfo: Possible values:

  • 0 = Unknown

  • -1 = Not specified

  • 2 = Foul

  • 3 = Incorrect entry

  • 5 = Play stopped

-

-

1024

Match about to start

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

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)

Extrainfo: Possible value:

  • 1 = Time started

  • 0 = Time stopped

-

-

1039

Manual time adjustment

Add or remove seconds from period time, used if current time is incorrect

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

Extrainfo: 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)

Extrainfo: 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)

Powerplay: Indicates if there is powerplay for a team

  • 0 = no powerplay,

  • 1 = home team powerplay,

  • 2 = away team powerplay.

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

Hardphone (BC)

iScout (BC + DC)

XSA (DC)

Extrainfo: Possible values:

  • 1 = Early betstart

  • 0 = Early betstart ended

-

-

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)

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

-

-

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.

iScout (BC + DC)

XSA (DC)

Extrainfo: Reason. Possible values:

  • 0 = Undefined reason

  • 1 = Weather conditions

  • 3 = Injury

  • 11 = Facility delay

-

-

1113

Stop match ended

Match resumes after being stopped.

iScout (BC + DC)

XSA (DC)

-

-

-

1126

Attack

Used when puck is in opponent's third of the rink

iScout (BC + DC)

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

iScout (BC + DC)

XSA (DC)

Extrainfoicehockey: Team in possession . Possible values:

  • 0 - unknown

  • 1 - home team

  • 2 - away team

-

-

1459

Video review over

Video review over

iScout (BC + DC)

XSA (DC)

Extrainfo: Outcome. Possible values:

  • 0 = Call stands

  • 1 = Call overturned

Extrainfoicehockey: Team in possession . Possible values:

  • 0 - unknown

  • 1 - home team

  • 2 - away team

-

-

1521

Delayed penalty

Delayed penalty

iScout (BC + DC)

XSA (DC)

-

-

-

1550

Score adjustment

Manual period score adjustment in RTS

External Feed (BC)

Extrainfo: Number of period being adjusted

Extrainfoicehockey: Updated period score (the one that was adjusted) and full score. Possible alues:

  • <home_period_score>:<away_period_score>

  • <home_full_score>:<away_full_score>

-

-

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

iScout (BC + DC)

XSA (DC)

Extrainfo: Ice conditions. Possible values:

  • 1 = Good

  • 2 = Medium

  • 3 = Poor

-

-

1770

Stoppage

Play is stopped during the game.

iScout (BC + DC)

XSA (DC)

Extrainfo: Stoppage reason. Possible values:

  • 1 = Ice/Rink Maintenance

  • 2 = Icing

  • 3 = Goalie Stopped

  • 4 = Official Review

  • 5 = Offside

  • 6 = Net off

  • 7 = High Stick

  • 8 = Hand Pass

  • 9 = Puck in Netting

  • 10 = Puck out of Play

  • 11 = Puck Frozen

  • 12 = Referee or Linseman

-

-

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.

iScout (BC + DC)

XSA (DC)

Extrainfo: Whether this faceoff is opening a period, and which period that is. Possible values:

  • 0 = Not opening faceoff

  • 1 = First period opening faceoff

  • 2 = Second period opening faceoff

  • 3 = Third period opening faceoff

  • 4 = Most recent overtime period opening faceoff

Extrainfoicehockey: Zone in which the faceoff takes place. Value: Integer between 0-8, enumerating the different faceoff zones on the rink as illustrated below:

Id of home team player in the faceoff.(available only for XSA (device=4))

Id of away team player in the faceoff.(available only for XSA (device=4))

1772

Puck safe

Used when an attack is over, i.e. the puck is not in opponent's third

iScout (BC + DC)

XSA (DC)

-

-

-

1885

Puck position

Position of the puck on the rink in x/y coordinates.

iScout (BC + DC)

XSA (DC)

-

-

-

2233

Players Time on Ice

Time spent on ice by each player. Event will be updated every 10 seconds and will only be available in NHL games with official PPT tracking data.

iScout (DC)

XSA (DC)

Hometimeonice: Time on ice spent by home team players. Format: "PID=ss;PID=ss;PID=ss" - List of key=value pairs separated by semicolon (";"), where key is player ID and value is time spent on ice in seconds

Awaytimeonice: Time on ice spent by away team players Format: "PID=ss;PID=ss;PID=ss" - List of key=value pairs separated by semicolon (";"), where key is player ID and value is time spent on ice in seconds

-

-

2234

Attacking players

List of all attacking players on ice (including goalie) is sent in case NHL Official Feed indicates that there is a high probability that a goal was scored. Please note: It can happen that Player ID's are corrected later based on NHL data validation processes.

iScout (DC)

XSA (DC)

Attackingplayers: list of player ids who have been on ice while they score a possible goal Format: "PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

-

-

2235

Premium Data Availability

Indicating if NHL official rich data (currently event 2233 and 2234) is available, incomplete or unavailable. Incomplete indicates situations where data is not available for one or some players.

iScout (DC)

XSA (DC)

Extrainfo:

  • 0 = unavailable

  • 1 = available

  • 2 = incomplete (ideally including information for which player ID its unavailable) => optional attribute player

Unavailableplayerhome: list of home team players for whom premium data is unavailable Format: "PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

Unavailableplayeraway: list of away team players for whom premium data is unavailable Format: "PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

-

-

2237

Players On Ice

Information about players being in an active lineup on ice.

External Feed (DC)

players

  • active players on ice

  • format: String

homeplayers=PlayersonIce awayplayers=PlayersonIce

PlayersonIce → "PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

-

-

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

XML example

<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
Description
Possible values

Match

extrainfo

Integer specifying special information for the match.

Integer. Possible values:

  • 0 = Default (5 minutes overtime length)

  • 12 = 10 minutes overtime length

  • 13 = 20 minutes overtime length

  • 32 = 7 minutes overtime length

  • 33 = No overtime

  • 56 = 3x10 min periods, 3vs3 + goalie, half-sized ice rink, penalty shots instead of suspensions)

  • 65 = 3 x 4 minutes

  • 67 = 3 x 3 minutes

timerunning

Whether the time is running.

Integer.

  • 1 = Time is running

  • 0 = Time is not running

Elements in the <match> element

XML example

<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" powerplay="2"/>
<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
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:

  • 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

t2

Amount of suspensions away team.

Integer

powerplay

Indicates if there is powerplay for a team.

  • 0 = no powerplay,

  • 1 = home team powerplay,

  • 2 = away team powerplay.

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:

  • "home"

  • "away"

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:

  • 0 = Unknown

  • 1 = Good

  • 2 = Medium

  • 3 = Poor

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:

  • 0 = Unknown

  • 1 = Home

  • 2 = Away

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:

  • 0 = Unknown

  • 1 = Home

  • 2 = Away

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:

  • 0 = Unknown

  • 1 = Home

  • 2 = Away

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:

  • 0 = Unknown

  • 1 = Home

  • 2 = Away

Attributes in the <event> element

XML example

<!-- 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
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

Hometimeonice

Time on ice spent by home team players.

"PID=ss;PID=ss;PID=ss" - List of key=value pairs separated by semicolon (";"), where key is player ID and value is time spent on ice in seconds

Awaytimeonice

Time on ice spent by away team players.

"PID=ss;PID=ss;PID=ss" - List of key=value pairs separated by semicolon (";"), where key is player ID and value is time spent on ice in seconds

Attackingplayers

List of player ids who have been on ice while they score a goal

"PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

Unavailableplayerhome

List of home team players for whom premium data is unavailable

"PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

Unavailableplayeraway

List of away team players for whom premium data is unavailable

"PID;PID;PID;PID;PID;PID" - List of player ids separated by semicolon (";")

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.

XML example

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

XML example

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

XML example

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

XML example

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

(ID: 154) Include time on ice in Ice Hockey

Enabling this setting will add XML event type 2233 <<Players Time on Ice>> to the Live Data XML Feed for NHL matches

XML example

<match matchid="10115268" ... >
... 
<event type="2233" stime="1633512996216" side="none" mtime="00:47" id="2164305422" uuid="9c0114bd-b094-4767-9040-fa82f95246d2" matchscore="0:0" remainingtimeperiod="19:13" periodnumber="1" matchstatus="FIRST_PERIOD" hometimeonice="8473507=26;8470595=26;8470642=39;8476469=26;8481540=2;8477476=39;8476441=26;8475848=39;8470621=26;8475279=39;8471679=65;8476479=39" awaytimeonice="8475233=26;8476624=26;8476883=65;8479410=26;8476453=39;8476292=39;8476826=26;8478010=39;8480172=39;8476399=26;8475167=39"/> 
</events>
</match>

(ID: 164) Include player positions in lineup hockey

Enabling this setting will add player positions to the Live Data XML Feed lineups for Ice Hockey matches if available

Attribute
Description
Possible values

position

Where the player is typically playing in the field based on the season.

  • G = Goaltender

  • D = Defenseman

  • C = Center

  • LW = Left Wing

  • RW = Right Wing

XML example

<lineups matchid="6856980">
<player id="215564" name="Crosby, Sidney" shirtnumber="5" substitute="false" position="G" team="1"/>
<player id="412234" name="Hull, Bobby" shirtnumber="7" substitute="false" position="C" team="1"/>
<!-- Remaining message truncated -->
</lineups>

PreviousHandballNextKabaddi

Last updated

Was this helpful?