Badminton
Sport specific information for badminton
Match statuses in badminton
0
NOT_STARTED
Not started yet
-
8
FIRST_SET
1st set
-
301
FIRST_PAUSE
1st pause
-
9
SECOND_SET
2nd set
-
302
SECOND_PAUSE
2nd pause
-
10
THIRD_SET
3rd set
-
303
THIRD_PAUSE
3rd pause
-
11
FOURTH_SET
4th set
-
304
FOURTH_PAUSE
4th pause
-
12
FIFTH_SET
5th set
-
100
ENDED
The match has ended
-
93
WALKOVER1
The home team won the match by walkover
-
94
WALKOVER2
The away team won the match by walkover
-
95
RETIRED1
The away team won because the home team retired
-
96
RETIRED2
The home team won because the away team retired
-
97
DEFAULTED1
The away team won because the home team defaulted
-
98
DEFAULTED2
The home team won because the away team defaulted
-
61
DELAYED
The match start is delayed
-
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 badminton
40
Yellow card
Used when the yellow card is confirmed.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Player who got the card
-
50
Red card
Used when the red card is confirmed.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Player who got the card
-
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)
External Feed (BC)
-
-
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)
External Feed (BC)
-
-
1013
Match status
Sent when the status of the match changes.
Hardphone (BC)
iScout (BC)
External Feed (BC)
See table above for match statuses
-
-
1015
Free comment
Used for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..
Hardphone (BC)
iScout (BC)
External Feed (BC)
-
-
1022
Which team serves first
Information about the player who will start to serve.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Possible values:
1 = Home team serves first
2 = Away team serves first
-
-
1024
Match about to start
Sent shortly before serving player takes the first serve.
Hardphone (BC)
iScout (BC)
External Feed (BC)
-
-
1031
Ball in play
Hardphone and iScout: Used when the service has been taken and the ball is in play.
External Feed: Send when player serves the ball
Hardphone (BC)
iScout (BC)
External Feed (BC)
-
-
1044
Deleted event alert
Manual removal of an event.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Id of event that was deleted.
-
-
1102
Coverage status
Sent when the coverage status for the match changes
Hardphone (BC)
iScout (BC)
External Feed (BC)
Possible values:
0 = Covered
1 = Coverage abandoned
2 = Match will not be covered
-
-
1112
Match stop / suspension
Sent when a match needs to be stopped.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Possible values:
0 = Not specified
1 = Weather conditions
2 = Darkness
3 = Injury
4 = Floodlight failure
5 = Person entering the field
6 = Crowd control issue
7 = Water break
8 = Disciplinary issue
9 = Gone to TMO
10 = Replacing ball
11 = Facility delay
12 = Tactical time-out 13 = Drinks
-
-
1113
Match stop / suspension over
The match resumes after being stopped.
Hardphone (BC)
iScout (BC)
External Feed (BC)
-
-
1127
Let
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)
External Feed (BC)
-
-
1141
Score change
Information about the match score updated point by point.
Hardphone (BC)
iScout (BC)
External Feed (BC)
Possible values:
0 = Standard
1 = Ace (not provided in External Feed coverage)
2 = Service error (not provided in External Feed coverage)
3 = Red card
-
-
1142
Black card
Black card status is used whenever a player is being disqualified. Common reasons are persistent or flagrant offence.
-
Player who got the card
-
2388
Possible End of Period
Sent before the deciding point in a game/set/match for multiple sports If the deciding point is confirmed, then an applicable score change event will follow.
iScout (BC)
-
-
-
2389
End of period not confirmed
Sent when the deciding point in a game/set/match was not confirmed
iScout (BC)
-
-
-
Sport specific XML elements and attributes
This section explains what elements / attributes one can expect for badminton matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.
Attributes in <match> element
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" firstserve="away" matchid="10115484" matchtime
="2:23:04" numberofsets="3" setlimit="21" st1id="87528" start="1464858600000" t1id="5261571" t1name="MATSUTOMO M /
TAKAHASHI A" t2id="6862483" t2name="RAHAYU A / SUGIARTO J F">
...
</match>XML elements and attributes definition
Match
extrainfo
Integer specifying special information for the match.
Integer. Possible values:
0 = Default (BO3, first to 21)
28 = Best of 3 (first to 15)
30 = Best of 5 (first to 11)
40 = Best of 5 (first to 11, decider at 14-all)
41 = Best of 5 (first to 11, 3 pt challenge
at 10-all)
firstserve
Which player has first serve of match.
setlimit
Please note that this attribute needs to be enabled in the XML configuration options.
numberofsets
How many sets are being played in the match.
Elements in <match> element
<match betstatus="BETSTOP" connectionstatus="0" device="1" extrainfo="0" feedtype="full" firstserve="away" matchid="10115484" matchtime="
2:23:04" numberofsets="3" setlimit="21" st1id="87528" start="1464858600000" t1id="5261571" t1name="MATSUTOMO M / TAKAHASHI A"
t2id="6862483" t2name="RAHAYU A / SUGIARTO J F">
<status id="100" name="ENDED" start="1464860478511"/>
<score t1="2" t2="0" type="match"/>
<score t1="21" t2="12" type="set1"/>
<score t1="21" t2="14" type="set2"/>
<serve team="home"/>
<black t1="0" t2="0"/>
<red t1="0" t2="0"/>
<yellow t1="0" t2="0"/>
<tournament id="53068" name="Indonesia Open (SS) 2016, Women Doubles"/>
<category id="259" name="International"/>
<sport id="31" name="Badminton"/>
<events/>
</match>XML elements and attributes definition
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:
Badminton full score (1141)
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:
match
set1
set2
set3
set4
set5
serve
This element always gets included, in both the full feed and the delta feed.
team
Which team served.
String. Possible values: "home" "away"
black
This element always gets included, in both the full feed and the delta feed.
t1
Amount of black cards home team.
Integer
t2
Amount of black cards away team.
Integer
red
This element always gets included, in both the full feed and the delta feed.
t1
Amount of red cards home team.
Integer
t2
Amount of red cards away team.
Integer
yellow
This element always gets included, in both the full feed and the delta feed.
t1
Amount of yellow cards home team.
Integer
t2
Amount of yellow cards away team.
Integer
Attributes in <event> element
<match matchid="9577119" ... >
<events>
<event extrainfo="100" id="650847077" info="ENDED" matchscore="2:0" mtime="1:01:08" setnumber="2" setscore="21:17" side="none"
stime="1465704613813" type="1013"/>
</events>
</match>XML attributes definition
event
extrainfo
Attribute containing additional information about the event.
Long
setnumber
The number of the current set in the match.
Integer
setscore
Score for current set.
String. Format: "[home]:[away]" Example: "5:4"
matchscore
Score for current match.
String. Format: "[home]:[away]" Example: "1:0"
XML configurations for badminton
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: 29) Badminton set limit
If this setting is enabled, <match> elements for badminton matches will contain a setlimit attribute.
XML example
<match betstatus="BETSTOP" connectionstatus="0" extrainfo="0" feedtype="full" matchid="7519874" numberofsets="3" setlimit="21" start="
1435452000000" t1id="1276433" t1name="ARENDS J / PIEK S" t2id="6444419" t2name="LEE C H R / CHAU H W">
<!-- Message truncated -->
</match>
(ID: 118) Use match statuses DEFAULTED
Enabling this setting will allow the system to send match statuses DEFAULTED1 and DEFAULTED2 for badminton.
Last updated
Was this helpful?