Sport specific information about futsal.

Match statuses in futsal

IDMatch statusDescriptionAdditional information
0NOT_STARTEDNot started yet-
6FIRST_HALF1st period of the match-
31HALFTIMEMatch pause-
7SECOND_HALF2nd period of the match-
100ENDEDThe match has ended-
32AWAITING_OTWaiting for overtime to start-
41FIRST_HALF_OT1st overtime period-
33OT_HALFTIME

Pause between 1st and 2nd overtime period

-
42SECOND_HALF_OT2nd overtime period-
110AFTER_OTMatch finished after overtime-
34AWAITING_PENALTIES

Waiting for penalty shoot-out to start

-
50PENALTY_SHOOTINGpenalty shoot-out-
120AFTER_PENALTIES

Match finished after penalty shoot-out

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

IDEventDescriptionCoverageextrainfoplayer1player2
30Goal

Sent when the goal is confirmed. 

Hardphone (BC)

Values:

  • 0 = Unknown
  • -100 = Shot
  • -200 = Free kick
  • -300 = After corner
  • 1 = Penalty
  • 2 = Own goal
  • 3 = Header
  • 4 = Fast break
  • 5 = Breakthrough
  • 6 = Direct free throw
  • 7 = Even strength
  • 8 = Power play
  • 9 = Short handed
  • 10 = Pivot
  • 11 = Empty net
--
40Yellow cardUsed when the yellow card is confirmed.




Hardphone (BC)-

ID of the player who got red card

-
43SuspensionTriggered whenever a player is sent off due to a foul.Hardphone (BC)

Number of minutes the player is suspended for

--
45Yellow/Red cardUsed when it is confirmed the player has been sent off due to two yellow cards.Hardphone (BC)-

ID of the player who got red card

-
50Red card Used when the red card is confirmed.Hardphone (BC)-

ID of the player who got red card

-
110PossessionPossession change to the given team.Hardphone (BC)---
154CornerUsed when the corner is confirmedHardphone (BC)-1 = Information not available

ID of the player
who took the corner

-
161Penalty awardedUsed when the penalty shot is confirmed.Hardphone (BC)-

ID of the player who was awarded the throw

ID of the player who cause the throw

666Penalty missedUsed when the penalty shot is missed.Hardphone (BC)-

ID of the player
who missed

-
 1010BetstartBetstart indicates that betting markets can be activated. Betstart is not only a pre match event but is also used during the match.Hardphone (BC)---
 1011BetstopBetstop 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)---
 1012Kickoff teamWhich team will have the kick off in the match.Hardphone (BC)---
 1013Match status

Sent when the status of the match changes.

QCI, Hardphone (BC)See the above table for match statuses for futsal.--
1015 Free commentUsed for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..Hardphone (BC)---
1016Possible cornerHappens at the exact moment there is a corner. Entries are assigned to teamsHardphone (BC)---
1017Canceled cornerUsed when possible corner is not confirmedHardphone (BC)---
1018Possible goal

Possible goal.

Hardphone (BC)---
1019Canceled goal

Canceled goal.

Hardphone (BC)

Values:

  • 0 = unknown
  • 1 = off side
  • 2 = foul
  • 3 = incorrect entry
  • 4 = out of bounds
  • 5 = play stopped
--
 1024Match is about to startThis event is sent when both captains, together with the referee, are selecting which team will start the match.Hardphone (BC)---
1035TimeoutA team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too.Hardphone (BC)---
1036Time start / stopTriggered when the clock is started or stopped.Hardphone (BC)

Possible values:

  • 1 = Time started
  • 0 = Time stopped
--
 1039Manual time adjustmentManual adjustment of timeHardphone (BC)

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

--
1040Possible red card

Used 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)---
1041Canceled red cardUsed when possible red card is not being con- firmed. Note that the cancelled red card could also be a cancelled yellow/red card.Hardphone (BC)---
1042Possible penaltyUsed when there is a strong possibility of a penalty shot.Hardphone (BC)---
1043Canceled penaltyUsed when a possible penalty is not confirmed.Hardphone (BC)---
1044Deleted event alertManual removal of an event.Hardphone (BC)Id of event that was deleted.--
1047Timeout overThe timeout is overHardphone (BC)---
1049Suspension overTriggered when suspended player returns on ice.Hardphone (BC)---
1050Possible empty net situationTriggered when one of the teams pulls out the goal keeperHardphone (BC)---
1051Empty net situation

Triggered when an empty net situation is confirmed.

Hardphone (BC)---
1052Empty net situation overTriggered when the empty net situation is resolved and goal keeper is back.


Hardphone (BC)---
1053Empty net situation canceledTriggered when an empty net situation is not confirmed.Hardphone (BC)---
1059Direct foulSent when a direct foul happens. Leads to a direct free kick for the opposing team.Hardphone (BC)---
1060Direct free kick

The amount of direct free kicks for home and/or away team

Hardphone (BC)

Possible values:

  • -1 = Not taken
  • 0 = Miss
  • 1 = Score
--
1064Play resumes after goal

Used when the play resumes after a goal, by a kick off.

Hardphone (BC)

---

1102

Coverage statusSent when the coverage status for the match changes.Hardphone (BC)

Possible values:

  • 0 = Covered
  • 1 = Coverage abandoned
  • 2 = Match will not be covered
--
1104Penalty shootout starting teamInformation about which team is going to begin with the shootout.Hardphone (BC)---


Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for futsal 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" device="1" extrainfo="0" feedtype="full" matchid="10113660" matchtime="20:00" st1id="
108451" st2id="44196" start="1464258360000" t1id="6730605" t1name="BAKU UNITED FC FUT" t2id="5540123" t2name="HELVECIA
FUTSAL LONDON" timerunning="1">
...
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
MatchextrainfoInteger specifying special information for the match

Integer. Possible values:

  • 0 = Default
  • 14 = 2 x 25 minutes
timerunningWhether the time is running.

Integer.

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

Elements in the <match> element

<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" matchid="10113660" matchtime="20:00" st1id="
108451" st2id="44196" start="1464258360000" t1id="6730605" t1name="BAKU UNITED FC FUT" t2id="5540123" t2name="HELVECIA
FUTSAL LONDON" timerunning="1">
<status id="6" name="FIRST_HALF" start="1464260659817"/>
<score t1="0" t2="0" type="current"/>
<possession team="away"/>
<red t1="0" t2="1"/>
<yellow t1="0" t2="1"/>
<corners t1="0" t2="1"/>
<penalties t1="0" t2="0"/>
<kickoffteam team="1"/>
<directfoulsperiod t1="0" t2="0"/>
<directfreekicks t1="0" t2="0"/>
<tournament id="13637" name="1st Division"/>
<category id="737" name="England"/>
<sport id="29" name="Futsal"/>
<events/>
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
score

Multiple occurrences possible, each occurrence describes the amount of goals 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 goals home team.Integer
t2Amount of goals away team.Integer
type

For what period in the match the goals were scored.

String. Possible values:

  • current
  • period1
  • period2
  • overtime1
  • overtime2
  • penalties
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)

t1

Possession percentage home team.

Integer
t2Possession percentage away team.Integer
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
corners

This element always gets included in full feed, and in the delta feed for the following events: Corner (154)

t1Amount of corners home team.Integer
t2Amount of corners away team.Integer
penalties

This element always gets included in full feed, and in the delta feed for the following events: Penalty awarded (161)

t1Amount of penalties home team.Integer
t2Amount of penalties away team.Integer
kickoffteam

This element always gets included in full feed, and in the delta feed for the following events: Kickoff team (1012)

teamWhich team kicked off.

Integer. Possible values:

  • 0 = Unknown
  • 1 = Home
  • 2 = Away
directfoulsperiod

This element always gets included in full feed, and in the delta feed for the following events: Direct Foul (1059)

t1Amount of direct fouls home team.Integer
t2Amount of direct fouls away team.Integer
directfreekicks

This element always gets included in full feed, and in the delta feed for the following events: Direct free kick (1060)

t1

Amount of direct free kicks home team.

Integer
t2

Amount of direct free kicks away team.

Integer

Attributes in the <event> element

<match matchid="9533085" ... >
 <events>
  <event extrainfo="0" id="653352533" info="Time stopped" matchscore="3:1" mtime="37:53" periodnumber="2" remainingtimeperiod="02
:07" side="none" stime="1466035608990" type="1036"/>
 </events>
</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
player1

Sportradar player id for player 1 connected to this event.

Integer
player2

Sportradar player id for player 2 connected to this event.

Integer
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

XML configurations for futsal

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: 59) Send periodx score types for futsal

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 futsal matches:

  • period1
  • period2


<match matchid="7440630" ... >
<score t1="14" t2="20" type="period1"/>
<!-- Remaining message truncated -->
</match>

(ID: 128) Include play resumes after goal

Enabling this setting will allow event 1064 (play resumes after goal) to be sent.

Back to top