Volleyball
Sport specific information for volleyball.
Match statuses in volleyball
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
-
305
FIFTH_PAUSE
5th pause
-
441
SIXTH_SET
6th set
-
306
SIXTH_PAUSE
6th pause
-
442
SEVENTH_SET
7th set
-
100
ENDED
The match has ended
-
17
GOLDEN_SET
Golden set
-
37
AWAITING_GOLDEN_SET
Waiting for the golden set to begin
-
130
AFTER_GOLDEN_SET
Golden set 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 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 volleyball
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 the above table for all available match statuses for Volleyball
-
1015
Free text
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
Who serves first.
Hardphone (BC)
iScout (BC)
-
-
1024
Match about to start
This event is sent when both captains, together with the referee, are selecting which team will start the match.
Hardphone (BC)
iScout (BC)
-
-
1031
Ball in play
Used when service has been taken and ball is in play.
Hardphone (BC)
iScout (BC)
-
-
1035
Timeout
A team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too.
Hardphone (BC)
iScout (BC)
-
-
1044
Deleted event alert
Manual removal of an event.
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:
0 = Standard
1 = Ace
2 = Service error
-
1047
Timeout over
Timeout is over
Hardphone (BC)
iScout (BC)
-
-
1058
Who serves first in tie break set
Team that serves first in tiebreak set.
Hardphone (BC)
iScout (BC)
-
-
1081
Current serve volleyball
Contains information about what team 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:
0 = Covered
1 = Coverage abandoned
2 = Match will not be covered
-
1550
Manual score adjustment
Manual period score adjustment
Hardphone (BC)
iScout (BC)
Set (numeric value)
Updated period score and full score. Possible Values:
values: "x,y" where x = periodscore and y = fullscore
1773
First serve golden set
Team that serves first in tiebreak a golden set.
iScout (BC)
-
-
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 Volleyball matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.
Attributes in the <event> element
XML example
<match betstatus="BETSTOP" connectionstatus="1" device="5" extrainfo="0" feedtype="full" matchid="10114593" matchtime="0:00:00"
numberofsets="5" start="1464768000000" t1id="7026026" t1name="TEST 1" t2id="7026025" t2name="TEST 2">
...
</match>XML elements and attributes definition
Match
extrainfo
Integer specifying special information for the match.
Integer. Possible values:
0 = Default (best of five sets)
8 = Best of 3 sets
15 = 21 points set limit
34 = 25 point set limit, tech-timout on 12
44 = Best of 7 sets 15 point limit
firstservegoldenset
Which player has first serve in the golden set. Please note that this attribute needs to be enabled in the XML configuration options first.
Integer
firstservetiebreak
Which player has first serve in the tiebreak.
Integer
firstserve
Which player has first serve of match.
Integer
numberofsets
How many sets are being played in the match.
Integer
Elements in <match> element
XML example
<match betstatus="BETSTOP" connectionstatus="1" device="5" extrainfo="0" feedtype="full" matchid="10114593" matchtime="0:00:00"
numberofsets="5" start="1464768000000" t1id="7026026" t1name="TEST 1" t2id="7026025" t2name="TEST 2">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0" t2="0" type="match"/>
<score t1="0" t2="0" type="set1"/>
<serve team="home"/>
<tournament id="1" name="Premier League"/>
<category id="1" name="England"/>
<sport id="23" name="Volleyball"/>
<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: Volleyball full score (1046)
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
goldenset
goldensetmatch
serve
This element always gets included, in both the full feed and the delta feed.
team
Which team served.
String. Possible values:
"home"
"away"
Attributes in the <event> element
XML example
<match matchid="9559079" ... >
<events>
<event extrainfo="0" id="650908581" info="24:16 [T1]" matchscore="2:0" mtime="1:32:14" setnumber="3" setscore="24:16" side="home"
stime="1465716682281" type="1046"/>
</events>
</match>XML attributes definition
event
extrainfo
Attribute containing additional information about the event.
Integer
matchscore
Score for current match.
String. Format: "[home]:[away]" Example: "1:0"
setnumber
The number of the current set in the match.
Integer
setscore
Score for current set.
String. Format: "[home]:[away]" Example: "5:4"
extrainfovolleyball
Attribute containing additional information about the event.
String
XML configurations
This section explains what elements / attributes one can expect for volleyball matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.
(ID: 48) Deep coverage volleyball
Enabling this setting will add a new attribute firstservegoldenset to the <match>-element for volleyball matches. This attribute contains information about what team served first in the golden set.
XML example
<match betstatus="BETSTOP" connectionstatus="1" feedtype="delta" firstserve="home" firstservegoldenset="home" matchid="1103190216"
numberofsets="3">
<!-- Other match info and events truncated -->
</match>(ID: 34) Include attribute extrainfovolleyball
Enabling this configuration will include the attribute "extrainfovolleyball" (values found in the event table above) in the feed.
Last updated
Was this helpful?