Betradar - the betting arm of Sportradar
Betradar - the betting arm of Sportradar
Sport specific information for Counter-strike.
Match statuses in Counter-strike
| ID | Match status | Description | Additional information |
|---|---|---|---|
| 0 | NOT_STARTED | Not started yet | - |
| 141 | FIRST_MAP | 1st map | - |
| 301 | FIRST_PAUSE | 1st pause | - |
| 142 | SECOND_MAP | 2nd map | - |
| 302 | SECOND_PAUSE | 2nd pause | - |
| 143 | THIRD_MAP | 3rd map | - |
| 303 | THIRD_PAUSE | 3rd pause | - |
| 144 | FOURTH_MAP | 4th map | - |
| 304 | FOURTH_PAUSE | 4th pause | - |
| 145 | FIFTH_MAP | 5th map | - |
| 305 | FIFTH_PAUSE | 5th pause | - |
| 146 | SIXTH_MAP | 6th map | - |
| 306 | SIXTH_PAUSE | 6th pause | - |
| 147 | SEVENTH_MAP | 7th map | - |
| 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 | - |
| 61 | DELAYED | The match start is delayed | - |
| 80 | INTERRUPTED | The match start 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 counter-strike
| ID | Event | Description | Coverage | extrainfo | extrainfocsgo | player1 | player2 |
|---|---|---|---|---|---|---|---|
| 60 | Substitution | A player has been substituted | External Feed (BC) | - | - | Player leaving the game = is substituted out. Information will be provided in a deltaupdate after the current round has ended. | Player entering the game = is substituted in. |
| 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. | 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. | External Feed (BC) | - | - | - | - |
| 1013 | Match status | Sent when the status of the match changes | External Feed (BC) | See the table above for allowed values | - | - | - |
| 1015 | Free comment | Sent when the status of the match changes | External Feed (BC) | - | - | - | - |
| 1044 | Deleted event alert | Manual removal of an event | External Feed (BC) | Id of event that was deleted | - | - | - |
| 1102 | Coverage status | Sent when the coverage status for the match changes | External Feed (BC) | Possible values:
| - | - | - |
1814 | CS map started | The map starts | External feed (BC) | Which order the map is played. E.g 1 for first or 2 for second. | Id of what map is played | - | - |
1816 | CS map ended | The map ends. One team gains a match point | External feed (BC) | Which order the map is played. E.g 1 for first or 2 for second. | - | - | - |
1818 | CS round started | The round starts. | External feed (BC) | Which round starts, numeric value. | - | - | - |
1820 | CS round ended | The round ends. One team gains a map point (set point) | External feed (BC) | Which round ends, numeric value. | Reason for ending. Integer, possible values:
| - | - |
1822 | CS kill | One of the team looses a member. Remark: if it was a self elimination then the side attribute is just the opposite of the victim team. The team that gains an advantage of the death. | External feed (BC) | Type of kill. Possible values:
| - | Playerid of the killer | Playerid of the victim |
1824 | CS assist | The assisting player does 60% of the damage to person that is eliminated by a different player. | External feed (BC) | - | - | Playerid of the assisting player | Playerid of the victim |
1826 | CS map picked | Gives who picked what map to be played. | External feed (BC) | Which order the map is played. E.g 1 for first or 2 for second. | Id of what map will be played | - | - |
1827 | CS round rollback | The map has been rolled back to an earlier round | External feed (BC) | Which round the map is rolled back to. Numeric value | - | - | - |
1828 | CS CT start | Who starts the match on the CT side. | External feed (BC) | Which order the map is played. E.g 1 for first or 2 for second. | Id of what map will be played | - | - |
1900 | CS bomb planted | When the bomb has been planted. | External feed (BC) | - | - | Id of player which planted the bomb | - |
1901 | CS bomb defuse begin | When an attempt to defuse the bomb has started. | External feed (BC) | - | - | Id of player which started defusing the bomb | - |
1902 | CS team economy | The money balance for a team. | External feed (BC) | Amount in dollars, numerical positive value. | - | - | - |
1903 | CS team kill | When a player is killed by a member from the same team. | External feed (BC) | Type of kill. Possible values:
| - | Playerid of the killer | Playerid of the victim |
1904 | CS suicide | When a player has committed suicide. | External feed (BC) | - | - | The id of the player who committed suicide | - |
2010 | CS map banned | Indicates which maps has been banned from that given game by what team. | External feed (BC) | Which order the map is played. E.g 1 for first or 2 for second. | - | - | - |
| 2222 | CS item change | Tells of any item being purchased or picked up during play (not during freeze time), primary and secondary weapons dropped (excluding grenades, knife and taser) besides bomb pickup+drop & grenades thrown. | External feed (BC) | - | Type of item action
| Player who changed the item | - |
| 2224 | CS damage done | Tells of any damaging event (bullet, grenade, flames etc) done by one player to another, how much damage the attacker inflicted and the remaining health of the victim. | External feed (BC) | - | - | Playerid of the killer | Playerid of the victim |
| 2225 | CS player inventory | Contains the current money and items for a player, sent when freeze time ends. | External feed (BC) | Current money in numerical value | - | Playerid | - |
Sport specific XML elements and attributes
This section explains what elements / attributes one can expect for Counter-Strike matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.
Elements in <match> element
XML example
<match betstatus="BETSTOP" connectionstatus="0" device="5" extrainfo="-1" feedtype="full" matchid="10111695" matchtime="0:00:00" st1id=" 190327" st2id="190326" start="1464808200000" t1id="8733856" t1name="TAGTEAM.GG" t2id="8733855" t2name="SLIGHTLY DIFFERENT GAMING"> <status id="100" name="ENDED" start="1464811518362"/> <score t1="1" t2="0" type="match"/> <score t1="16" t2="13" type="map1"/> <matchformat> <format type="maps" value="1"/> <format type="rounds" value="30"/> <format type="overtimerounds" value="6"/> </matchformat> <tournament id="52635" name="ESL Benelux Championship - Group Stage"/> <category id="1041" name="ESL CS:GO"/> <sport id="109" name="ESport Counter-Strike"/> <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: CS map ended (1816), CS round ended (1820) | ||
| 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:
| |
| matchformat | This element always gets included in full feed, and in the delta feed for the following events: This element consists of subelements which will be explained more into detail below. | ||
Elements and attributes in <matchformat> element
If extra attributes are needed to specify the match format, those will be added in the <matchformat>-element, which holds <format>-elements for each match format option. The actual formats are described in the type and value attributes.
XML example
<match betstatus="BETSTOP" connectionstatus="0" device="5" extrainfo="-1" feedtype="full" matchid="10111695" matchtime="0:00:00" st1id=" 190327" st2id="190326" start="1464808200000" t1id="8733856" t1name="TAGTEAM.GG" t2id="8733855" t2name="SLIGHTLY DIFFERENT GAMING"> <status id="100" name="ENDED" start="1464811518362"/> <matchformat> <format type="maps" value="1"/> <format type="rounds" value="30"/> <format type="overtimerounds" value="6"/> </matchformat> ... </match>
Possible values type and value attributes for Counter-Strike
| Type | Value |
|---|---|
| maps | Number of maps to be played. Integer, value from 1 - 7. |
| rounds | Maximum amount of rounds played in a normal round. Integer. |
| overtimerounds | How many rounds to be played when the normal round ends tied. Integer, always an even number. |
Attributes in <event> element
<!-- Example 1 --> <match matchid="9571597" ... > <events> <event extrainfo="1" id="649774011" info="Spiidi killed Slemmy" mapnumber="1" mapscore="12:15" matchscore="0:0" mtime="0:00:00" player1="929950" player2="986329" roundnumber="28" side="away" stime="1465586954831" type="1822" weaponid="42" weaponname="UMP-45"/> </events> </match> <!-- Example 2 --> <match matchid="9571597" ... > <events> <event extrainfo="28" extrainfocsgo="1" id="649774089" info="Round 28 won by [T2] (by terrorists eliminating all CTs)" mapnumber="1" mapscore="12:16" matchscore="0:0" mtime="0:00:00" roundnumber="28" side="away" stime="1465586960851" type="1820"/> </events> </match> <!-- Example 3 --> <match matchid="9571597" ... > <events> <event extrainfo="1" extrainfocsgo="-1" id="16032752" info="Started play on map 1 (unknown_map)" mapname="de_dust" mapnumber= "1" mapscore="0:0" matchscore="0:0" mtime="0:00" roundnumber="0" side="none" stime="1474404493903" type="1814"/> </events> </match>
XML attributes definition
| Element | Attributes | ||
|---|---|---|---|
| Attribute | Description | Possible values | |
| event | extrainfo | Attribute containing additional information about the event. | Long |
| extrainfocsgo | Attribute containing additional information about the event. | String | |
| player1 | Sportradar id of player 1 associated with the event. | Integer | |
| player2 | Sportradar id of player 2 associated with the event. | Integer | |
| matchscore | Score for current match. | String. Format: "[home]:[away]" | |
| mapnumber | Number of the current map. | Integer | |
| mapscore | Score for current map. | String. Format: "[home]:[away]" | |
| roundnumber | Number of the current round. | Integer | |
| weaponid | Id of the weapon used to perform the kill. This attribute only gets added for the CS kill event (1822). | Integer | |
| weaponname | Name of the weapon used to perform the kill. This attribute only gets added for the CS kill event (1822). | String | |
| mapname | Name of the map. This attribute only gets added for the CS map started (1814), CS map banned (2010) and CS map picked (1826) event. | String | |
| item & itemname | Two separate attributes. One containing the id and one containing the name of a Counter-Strike item. |
| |
| damage | numeric value of the damage value dealt | numeric value | |
| healthremaining | numeric value of the health value remaining for the victim after the damage is subtracted | numeric value | |
| inventory | A list of Counter-Strike item ids | Possible values are same as in attributes item & itemname and are separated with separated with ";" | |
XML configurations for counter-strike
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: 90) Send lineups for Counter-Strike matches
If this setting is enabled, the element <lineups> gets enabled for matches which have this configured. Lineups are sent when subscribing to a match, and when the lineup changes.
XML example
<lineups matchid="12345678"> <player id="1" name="Aaronson, Aaron" nickname="A.Aaronson" shirtnumber="0" substitute="false" team="1"/> <player id="2" name="Benito, Barry" nickname="B.Benito" shirtnumber="0" substitute="false" team="1"/> <player id="3" name="Cumberscratch, Cabertoss" nickname="C.Cumberscratch" shirtnumber="0" substitute="false" team="2"/> <player id="4" name="Dumpling, Danny" nickname="D.Dumpling" shirtnumber="0" substitute="false" team="2"/> </lineups>
(ID: 85) Include attribute mapname for Counter strike events
Enabling this setting will add the attribute mapname to the <event>-element when the CS map started (1814) or CS map picked (1826) event happens in Counter-Strike.
XML example
<match matchid="9571597" ... > <events> <event extrainfo="1" extrainfocsgo="-1" id="16032752" info="Started play on map 1 (unknown_map)" mapname="de_dust" mapnumber="1" mapscore="0:0" matchscore="0:0" mtime="0:00" roundnumber="0" side="none" stime="1474404493903" type="1814"/> </events> </match>
Overview
Content Tools