LD - Tennis

Sport specific information for tennis.

Match statuses in tennis

Id	Match status	Description	Additional information
0	NOT_STARTED	Not started yet	-
8	FIRST_SET	1st set	-
9	SECOND_SET	2nd set	-
10	THIRD_SET	3rd set	-
11	FOURTH_SET	4th set	-
12	FIFTH_SET	5th set	-
100	ENDED	The match has ended	-
93	WALKOVER1	The home team won the matchby 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	This match status is only sent if the corresponding XML configuration is enabled.
98	DEFAULTED2	The home team won because the away team defaulted	This match status is only sent if the corresponding XML configuration is enabled.
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 tennis

ID	Event	Description	Coverage	extrainfo	player1	player2
164	Weather conditions	Condition of the weather for the match. This event can be changed during the match if needed.	XSA (DC) iScout (DC)	Possible values: 0 = Unknown 1 = Good 2 = Medium 3 = Bad 4 = Indoor 5 = Extreme	-	-
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) XSA (DC) iScout (DC) ITF Scorer (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) XSA (DC) iScout (DC) ITF Scorer (BC) External feed (BC)	-	-	-
1013	Match status	Sent when the status of the match changes.	Hardphone (BC) XSA (DC) iScout (DC) ITF Scorer (BC) External feed (BC)	See the above table for match statuses in tennis.	-	-
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) XSA (DC) iScout (DC) External feed (BC)	-	-	-
1020	Surface type	Used to indicate which surface type the match is played on	Hardphone (BC) ITF Scorer (BC) XSA (DC) iScout (DC)	Possible values: 0 = Unknown 1 =Clay 2 = Hardcourt 3 = Grass 4 = Carpet	-	-
1021	Number of sets	Used to indicate how many sets the match consists of	ITF Scorer External feed (BC)	-	-	-
1022	Who serves first	Who serves first.	Hardphone (BC) XSA (DC) iScout (DC) ITF Scorer (BC) External feed (BC)	-	-	-
1023	Tiebreak in last set	Used to indicate if the match has a tiebreak in the last set	ITF Scorer (BC)	-	-	-
1024	Match about to start	Indicates that match will start soon	Hardphone (BC) ITF Scorer (BC) XSA (DC) iScout (DC) External feed (BC)	-	-	-
1025	Tennis score change	Sent when the score changes.	Hardphone (BC) XSA (DC) iScout (DC) ITF Scorer (BC) External feed (BC)	Possible values: 0 = Standard 1 = Ace 2 = Double fault opponent 3 = None 4 = Code violation point penalty 5 = Code violation game penalty 6 = Time violation point penalty 7 = Forfeit	-	-
1031	Ball in play	Used when ball is in play.	Hardphone (BC) iScout (DC) ITF Scorer (BC) XSA (DC)	-	-	-
1032	Tennis service fault	Sent when there was a fault in the service.	Hardphone (BC) XSA (DC) iScout (DC) ITF Scorer (BC) External feed (BC)	Possible values: 0 = Not specified 1 = Foot fault 2 = Net	-	-
1044	Deleted event alert	Manual removal of an event.	Hardphone (BC) XSA (DC) ITF Scorer (BC) External feed (BC)	Id of event that was deleted.	-	-
1061	Service taken	Info about the current server	XSA (DC) iScout (DC) External feed (BC AO)	-	-	-
1062	Ball position	Information about where the ball hits on the field, sent out when the ball bounces. This event does not get sent by default, and needs to be enabled in the XML configuration.	XSA (DC)	Position. Possible values: 0 = Out home 1 = Out away 2 = Alley top home 3 = Alley bottom home 4 = Alley top away 5 = Alley bottom away 6 = Back court home 7 = Back court away 8 = Left service home 9 = Right service home 10 = Left service away 11 = Right service away 12 = Net	-	-
1102	Coverage status	Sent when the coverage status for the match changes.	Hardphone (BC) iScout (DC) ITF Scorer (BC) External feed (BC)	Possible values: 0 = Covered 1 = Coverage abandoned 2 = Match will not be covered	-	-
1106	Ball change frequency	Frequency change of the ball during a match.	ITF Scorer (BC)	Possible values: 0 = Not specified 1 = Change final set 2 = Change 11 13 3 = Change 9 11 4 = Change 7 9 5 = No ball change	-	-
1108	Break due to extreme weather conditions	When a break is needed because of extreme weather, e.g. "too hot"	ITF Scorer (BC)	-	-	-
1109	Break due to extreme weather conditions over	Break because of extreme weather is over	ITF Scorer (BC)	-	-	-
1110	Toilet break / change of attire	Toilet break / change of attire	ITF Scorer (BC) External feed (BC)	Possible values: 0 = Toilet break 1 = Change of attire	-	-
1111	Toilet break / change of attire over	Toilet break / change of attire over	ITF Scorer (BC) External feed (BC)	Possible values: 0 = Toilet break finished 1 = Change of attire finished	-	-
1112	Match stop / suspension	Sent when a match needs to be stopped	ITF Scorer (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 14 = captains are being warned 15 = unscheduled break 16 = late innings break	-	-
1113	Match stop / suspension over	The match resumes after being stopped	ITF Scorer (BC) External feed (BC)	-	-	-
1115	Code violation	A code violation occurs during a match	ITF Scorer (BC) External feed (BC)	Code violation values: 0 = Not specified 1 = Delay of game 2 = Audible obscenity 3 = Visible obscenity 4 = Verbal abuse 5 = Physical abuse 6 = Ball abuse 7 = Racket equipment abuse 8 = Coaching 9 = Unsportsmanlike conduct 10 = Partisan crowd 11 = Captain behaviour 12 = Failure to complete match 13 = Best efforts 14 = Leaving the court	-	-
1116	Time violation	Time violation occurs during a match	ITF Scorer (BC) External feed (BC)	Penalty id values: 0 = Warning 1 = Point penalty code 2 = Point penalty time 3 = Game penalty 4 = Default 5 = Immediate default 6 = Service fault	-	-
1118	Trainer called	Used when a player needs medical attention.	ITF Scorer (BC) External feed (BC)	Possible values: 0 = Not specified 1 = Medical 2 = Cramping 3 = No treatment 4 = Start evaluating 5 = Medical time-out 6 = Cramping treatment 7 = Immediate cramping treatment 8 = Change over treatment 9 = Retaping 10 = Bleeding	-	-
1119	Trainer called finished	Used when a trainer called is over.	ITF Scorer (BC) External feed (BC)	-	-	-
1120	Who won coin toss	Info about who won the coin toss.	ITF Scorer (BC)	-	-	-
1121	Who made first server decision	Winner of the coin toss can decide who serves first.	ITF Scorer (BC)	-	-	-
1122	Which player serves first within doubles team	Which player receives first within doubles team	ITF Scorer (BC) External feed (BC)	Subteam id	-	-
1124	Match called	Umpire has called the match	iScout (DC) ITF Scorer (BC) External feed (BC)	-	-	-
1125	Which player receives first within doubles team	Which player receives first within doubles team.	ITF Scorer (BC)	Subteam id	-	-
1127	Replay point	Used when a point is played again.	ITF Scorer (BC)	-	-	-
1128	Which team starts serving on the left side of umpire	Which team starts serving on the left side of umpire.	ITF Scorer (BC)	-	-	-
1656	Challenge decision	Umpire has reached a decision on an official review Note: DavisCup, FedCup	ITF Scorer (BC) XSA (DC) External feed (BC)	Possible values: 1 = Won 0 = Lost	-	-
1657	Use challenges (Official reviews)	Venue has Hawk-Eye technology available. Note: DavisCup, FedCup	ITF Scorer (BC) XSA (DC) iScout (DC) External feed (BC)	Possible values: 1 = Official reviews are available 0 = Official reviews are not available	-	-
1658	Overrule	Overrule - replay point Note: DavisCup, FedCup	ITF Scorer (BC)	Possible values: 1 = Point will be replayed 0 = Point will not be replayed	-	-
1659	Challenge	Team calls an official review Note: DavisCup, FedCup	ITF Scorer (BC) XSA (DC) External feed (BC)	-	-	-
1660	Challenge not confirmed	Challenge (official review) not confirmed Note: DavisCup, FedCup	ITF Scorer (BC) External feed (BC)	-	-	-
2137	Service tie-break deciding point	Event representing who will serve deciding point in a tie-break.	XSA (DC)	-	-	-

Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for tennis matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.

Attributes in the <match> element

XML example

<match betstatus="BETSTOP" connectionstatus="0" device="-1" extrainfo="0" feedtype="full" matchid="10115533" matchtime="0:00:00"
numberofsets="3" sex="0" st1id="58091" st2id="126422" start="1464866220000" t1id="5827001" t1name="AGAR, RYAN" t2id="6028802"
t2name="AIRHUNMWUNDE, OSARIEMEN" tiebreaklastset="1">
...
</match>

XML elements and attributes definition

Element	Attributes
	Attribute	Description	Possible values
Match	extrainfo	Integer specifying special information for the match.	Integer. Possible values: 0 = Default 2= No advantage rule, super tiebreak to 10 points 3 = No advantage rule, super tiebreak to 7 points 4 = No advantage rule, no super tiebreak 5 = Advantage rule, super tiebreak to 10 points 6 = Advantage rule, super tiebreak to 7 points 48 = 4 games to set, no advantage rule, no super tiebreak 52 = 4 games to set, tiebreak at 3-3, first to 5 points in tiebreak, no advantage rule, no tiebreak 53 = Advantage rule, no super tiebreak, first to 10 points tiebreak in last set 54 = Advantage rule, no super tiebreak, tiebreak at 12-12 in last set
	sex	Whether the match is played by male or female.	Integer
	tiebreaklastset	Whether the last set in the match is a "tie-break" set or an "advantage set".	Integer. Possible values: 0 = no tie-break in last set 1 = tie-break in last set
	firstserve	Which player has first serve of match.	Integer
	numberofsets	How many sets are being played in the match.	Integer

Elements in the <match> element

XML example

<match betstatus="BETSTOP" connectionstatus="0" device="-1" extrainfo="0" feedtype="full" matchid="10115533" matchtime="0:00:00"
numberofsets="3" sex="0" st1id="58091" st2id="126422" start="1464866220000" t1id="5827001" t1name="AGAR, RYAN" t2id="6028802"
t2name="AIRHUNMWUNDE, OSARIEMEN" tiebreaklastset="1">
<status id="0" name="NOT_STARTED" start="0"/>
<surfacetype id="0" name="UNKNOWN"/>
<court id="0" name="Unknown"/>
<tiebreak value="0"/>
<serve team="home"/>
<score t1="0" t2="0" type="match"/>
<score t1="0" t2="0" type="game"/>
<score t1="0" t2="0" type="set1"/>
<tournament id="11639" name="Challenge Dummy"/>
<category id="72" name="Challenger"/>
<sport id="5" name="Tennis"/>
<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: Tennis full score (1025) and Delete event alert (1044)
	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 game set1 set2 set3 set4 set5 tiebreak
surfacetype	This element always gets included in full feed, and in the delta feed for the following events: Surface type (1020)
	id	Identifier for the surface types.
	name	Textual representation of the surface types.	String. Possible combinations of idname are: 0 = Unknown 1 = Clay 2 = Hardcourt 3 = Grass 4 = Carpet
court	This element only gets included in full feed. Please note that this element needs to be enabled in the XML configuration options.
	id	The id of the court.	Integer
	name	The name of the court.	String
	courtseqnum	Which match of the tournament is played on this court. Note that this attribute needs to be enabled in the XML configuration options.	Integer
tiebreak	This element always gets included, in both the full feed and the delta feed.
tiebreak	value	Whether the match is in tiebreak or not.	Integer. Possible values: 0 = Match is not in tiebreak 1 = Match is in tiebreak
serve	This element always gets included, in both the full feed and the delta feed.
serve	team		String. Possible values: "home" "away"

Note
If the set score is tied at six-all during a tie-break set, a tie-break game is played. On these occasions the <score type="setX" ...> element will contain a child score element with type "tiebreak".

<score type="setX" ...>
 <score type="tiebreak" ... >
</score>

Attributes in the <event> element

XML example

<match matchid="9571249" ... >
<events>
<event extrainfo="10" gamenumber="10" gamescore="40:30" id="649438025" info="Ball: left service court" matchscore="1:0" mtime="1
:32:17" posx="65" posy="67" setnumber="2" setscore="5:4" side="none" stime="1465560620029" type="1062"/>
</events>
</match>

XML attributes definition

Element	Attributes
	Attribute	Description	Possible values
event	extrainfo	Attribute containing additional information about the event.	Long
	posx	Horizontal position on pitch, posx being a number from 0 to 100.	Number
	posy	Vertical position on pitch , posy being a number from 0 to 100.	Number
	gamenumber	The number of the current game in the set.	Integer
	setnumber	The number of the current set in the match.	Integer
	gamescore	Score for current game.	String. Format: "[home]:[away]" Example: "40:30"
	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

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: 1) Deep coverage tennis

This setting will enable the following deeper coverage events for tennis matches:

Weather conditions (164)
Service taken (1061)
Ball position (1062)

Additionally, enabling this setting will enable coordinates for deeper coverage tennis matches.

(ID: 22) Send court information for tennis matches

If this setting is enabled, an element <court> gets added to the <match> element in the full feed.

XML example

<match matchid="7502420" ...>
<court id="36796" name="Court 4"/>
<!-- Remaining message truncated -->
</match>

(ID: 79) Include court sequence number in tennis

Enabling this setting will include the court sequence number for tennis matches, if available. The court sequence number is added in the attribute courtseqnum to the <court>-element for tennis matches. Please note that this setting will only have effect if the setting "Send court information for tennis matches" is enabled.

XML example

<match matchid="7502420" ...>
<court courtseqnum="1" id="36796" name="Court 4"/>
<!-- Remaining message truncated -->
</match>

(ID: 51) Send scout user id for ITF matches

If this setting is enabled, an element <scout> gets added to the <match> element in the full feed. Note that this only gets added for ITF matches.

XML example

<match matchid="7502420" ...>
<scout id="117335"/>
<!-- Remaining message truncated -->
</match>

(ID: 124) Include match status defaulted in Tennis

Enabling this setting will allow the system to send match statuses DEFAULTED1 and DEFAULTED2.

Page tree

LD - Tennis

Match statuses in tennis

Events in tennis

Sport specific XML elements and attributes

XML configurations

(ID: 1) Deep coverage tennis

(ID: 22) Send court information for tennis matches

(ID: 79) Include court sequence number in tennis

(ID: 51) Send scout user id for ITF matches

(ID: 124) Include match status defaulted in Tennis