Betradar - the betting arm of Sportradar
Betradar - the betting arm of Sportradar
Sport specific information for beach volleyball.
Match statuses for beach volleyball
| 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 by walkover | - |
| 94 | WALKOVER2 | The away team won the match by walkover | - |
| 95 | RETIRED1 | The away team won because the away team retired | - |
| 96 | RETIRED2 | The home team won because the home team retired | - |
| 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 beach volleyball
| ID | Event | Description | Coverage | extrainfo | extrainfovolleyball |
|---|---|---|---|---|---|
| 1010 | Betstart | Shows 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 | Beststop status is used to indicate that betting market shall be closed. Common reasons are: Score under review, Scout lost connection. | Hardphone (BC) iScout (BC) | - | - |
| 1013 | Matchstatus | 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 | Hardphone (BC) iScout (BC) | - | - |
| 1022 | Which team serves first | Information about which team will start serving. | Hardphone (BC) iScout (BC) | - | - |
| 1024 | Match about to start | Match about to start status appears shortly before serving team takes the first serve. | Hardphone (BC) iScout (BC) | - | - |
| 1031 | Ball in play | Ball in play status is used when service has been taken and ball is in play. | Hardphone (BC) iScout (BC) | - | - |
| 1035 | Timeout | Timeout status is given whenever a team calls a timeout. Each team is entitled to a max. of 1 timeouts each set. | Hardphone (BC) iScout (BC) | - | - |
| 1044 | Deleted event alert | Manual removal of an event (e.g. last point). | Hardphone (BC) iScout (BC) | Id of event that was deleted. | - |
| 1046 | Score change | Information about the match score updated point by point. | Hardphone (BC) iScout (BC) | Volleyball point type. Possible values:
| - |
| 1047 | Timeout over | Timeout over status is given when timeout is over. | Hardphone (BC) iScout (BC) | - | - |
| 1058 | Who serves first in tie break set | Information about which team will start serving in tie break set. | Hardphone (BC) iScout (BC) | - | - |
| 1081 | Current serve volleyball | Contains information about what teams has the current serve | Hardphone (BC) iScout (BC) | - | - |
| 1102 | Coverage status | Sent when the coverage status for the match changes. | Hardphone (BC) iScout (BC) | Possible values:
|
Sport specific XML elements and attributes
This section explains what elements / attributes one can expect for beach volleyball 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" extrainfo="0" feedtype="full" matchid="9574475" matchtime="0:00:00" numberofsets="3" start="1465628400000" t1id="8069591" t1name="MALINOVA D / SLANCHEVA R" t2id="7220701" t2name="SHALAYEUSKAYA V / SIAKRETAVA V"> ... </match>
XML elements and attributes definition
| Element | Attributes | ||
|---|---|---|---|
| Attribute | Description | Possible values | |
| Match | extrainfo | Integer specifying special information for the match. | Integer. Possible values:
|
| numberofsets | How many sets are being played in the match. | Integer | |
Elements in <match> element
XML example
<match matchid="9574475" ... > <status id="94" name="WALKOVER2" start="1465630797879"/> <score t1="0" t2="0" type="match"/> ... </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: Volleyball full score (1046) | ||
| t1 | Amount of points home team. | ||
| t2 | Amount of points away team. | ||
| type | For what period in the match the points were scored. | String. Possible values:
| |
Attributes in <event> element
XML example
<match matchid="9574475" ... > <events> <event extrainfo="94" id="649995055" info="WALKOVER2" matchscore="0:0" mtime="0:00:00" setnumber="1" setscore="0:0" side="none" stime="1465630797879" type="1013"/> </events> </match>
XML attributes definition
| Element | Attributes | ||
|---|---|---|---|
| Attribute | Description | Possible values | |
| event | extrainfo | Attribute containing additional information about the event. | Long |
Overview
Content Tools