Betradar - the betting arm of Sportradar
Betradar - the betting arm of Sportradar
Sport specific information for badminton.
Match statuses in badminton
| ID | Match status | Description | Additional information |
|---|---|---|---|
| 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 | - |
| 94 | WALKOVER2 | The away team won the match | - |
| 95 | RETIRED1 | The away team won because | - |
| 96 | RETIRED2 | The home team won because | - |
| 97 | DEFAULTED1 | The away team won because | - |
| 98 | DEFAULTED2 | The home team won because | - |
| 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 |
Events in badminton
| ID | Event | Description | Coverage | extrainfo | player1 | player2 |
|---|---|---|---|---|---|---|
| 40 | Yellow card | Used when the yellow card is confirmed. | Hardphone (BC) iScout (BC) | Player who got the card | - | |
| 50 | Red card | Used when the red card is confirmed. | Hardphone (BC) iScout (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) | - | - | |
| 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) | - | - | |
| 1013 | Match status | Sent when the status of the match changes. | Hardphone (BC) iScout (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) | - | - | |
1022 | Which team serves first | Information about the player who will start to serve. | Hardphone (BC) iScout (BC) | Possible values:
| - | - |
| 1024 | Match about to start | Sent shortly before serving player takes the first serve. | Hardphone (BC) iScout (BC) | - | - | |
| 1031 | Ball in play | Used when the service has been taken and the ball is in play. | Hardphone (BC) iScout (BC) | - | - | |
| 1044 | Deleted event alert | Manual removal of an event. | Hardphone (BC) iScout (BC) | Id of event that was deleted. | - | - |
| 1102 | Coverage status | Sent when the coverage status for the match changes | Hardphone (BC) | - | - | |
| 1112 | Match stop / suspension | Sent when a match needs to be stopped. | Hardphone (BC) iScout (BC) | Possible values:
| - | - |
| 1113 | Match stop / suspension over | The match resumes after being stopped. | Hardphone (BC) iScout (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), | - | - | |
1141 | Score change | Information about the match score updated point by point. | Hardphone (BC) iScout (BC) | Possible values:
| - | - |
| 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 | - |
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
XML example
<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
| Elements | Attributes | ||
|---|---|---|---|
| Attribute | Description | Possible values | |
| Match | extrainfo | Integer specifying special information for the match. | Integer. Possible values:
|
| 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
XML example
<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
| 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:
| ||
| 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:
| |
| serve | This element always gets included, in both the full feed and the delta feed. | ||
| team | Which team served. | String. Possible values: | |
| 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
XML example
<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
| Element | Attributes | ||
|---|---|---|---|
| Attribute | Description | Possible values | |
| 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]" | |
| matchscore | Score for current match. | String. Format: "[home]:[away]" | |
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.
Overview
Content Tools