Betradar - the betting arm of Sportradar

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt Include
HideElements
HideElements
nopaneltrue
Anchor
topOfPage
topOfPage

Excerpt Include
BetradarLogo
BetradarLogo
nopaneltrue

Panel

Sport specific information for squash.

Table of Contents

Match statuses in squash

Table Filter
inverse
sparkNameSparkline
limitHeight
separatorPoint (.)
labels
default
cell-width
datepatterndd M yy
globalFiltertrue
id1584430925417_-1274492040
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
IdMatch statusDescriptionAdditional information
0NOT_STARTEDNot started yet-
151FIRST_GAME1st game-
301FIRST_PAUSE1st pause-
152SECOND_GAME2nd game-
302SECOND_PAUSE2nd pause-
153THIRD_GAME3rd game-
303THIRD_PAUSE3rd pause-
154FOURTH_GAME4th game-
304FOURTH_PAUSE4th pause-
155FIFTH_GAME5th game-
100ENDEDThe match has ended-
93WALKOVER1The home team won the match by walkover-
94WALKOVER2

The away team won the match by walkover

-
95RETIRED1

The away team won because the home team retired

-
96RETIRED2

The home team won because the away team retired

-
94DEFAULTED1

The away team won because the home team defaulted

This match status is only sent if the corresponding XML configuration is enabled.

98DEFAULTED2

The home team won because the away team defaulted

This match status is only sent if the corresponding XML configuration is enabled.

200INJURY_BREAK

The match is in a break due to injury.

-
61DELAYEDThe match start is delayed.-
80INTERRUPTEDThe match has been interrupted.-
90ABANDONEDThe match has been abandoned.

This match status is only sent if the corresponding XML configuration is enabled.


Events in squash

Table Filter
inversefalse
sparkNameSparkline
limitHeight
sortID ⇧
separatorPoint (.)
labels
default
isFirstTimeEntertrue
cell-width
datepatterndd M yy
globalFiltertrue
id1592284664675_128792662
worklog365|5|8|y w d h m|y w d h m
isORAND
order0
 IDEvent

Description

Coverageextrainfoplayer1player2

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 Liveodds betstop. Beststop status is used to indicate that betting market shall be closed. Common reasons are: possible goal, goal under review. 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

Matchstatus

Sent when the status of the match changes.

External Feed (BC)See the above table for match statuses for squash.--

1015

Free text

Free text message. Free comment is used for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..

External Feed (BC)---

1024

Match about to start

Match is about to start

External Feed (BC)---
1044 Deleted event alertManual removal of an event.External Feed (BC)Id of event that was deleted--
1102Coverage status

Sent when the coverage status for the match changes.

External Feed (BC)

Possible values:

  • 0 = Covered
  • 1 = Coverage abandoned
  • 2 = Match will not be covered
--
1834

Squash full scoreSquash full score. Sends whenever a point is scored.External Feed (BC)---
1835

Squash current serveSquash Current Serve. Holds player serving and from which side of the court (left or right)External Feed (BC)

Position on the court. Possible values:

  • 1 = Left
  • 2 = Right
  • 0 = Unknown
--
1836

Squash decision outcomeSquash Decision outcome. Stroke, Let, No Let.External Feed (BC)

Decision outcome. Possible values:

  • 1 = Stroke
  • 2 = Let
  • 3 = No let
--
2063Score under reviewIndicates that a score is being reviewed.External Feed (BC)---


Sport specific XML elements and attributes

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

Attributes in the <match> element

Code Block
languagexml
titleXML example
<match betstatus="BETSTOP" connectionstatus="0" extrainfo="-1" feedtype="full" firstserve="home" matchid="10114836" matchtime="0
:2842:46" numberofsets="5" setlimit="11" start="1464697828000" t1id="1265255" t1name="DUNCALF, JENNY" t2id="7339963" t2name=
"FERNANDES, NICOLETTE">
...
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
Matchfirstserve

Which player has first serve of match.

Integer
setlimit

The amount of points which needs to be achieved to win the set. In the XML example: 11 points are needed to win the set. (If the score reaches 10-all, the game continues until one player leads by 2 points)

Integer
numberofsets

How many sets are being played in the match.

Integer

Elements in <match> element

Code Block
languagexml
titleXML example
<match t2name="GAULTIER, GREGORY" t2id="710617" t1name="AMAO, ADEWALE" t1id="7541571" start="1592984940000" matchid="21797227" feedtype="full" extrainfo="0" betstatus="BETSTOP" 
numberofsets="5" setlimit="11" connectionstatus="0" dc="1" device="5" coveredfrom="venue" st1id="329049" st2id="190154" matchtime="00:00:00" sportid="37">
<status start="0" name="NOT_STARTED" id="0"/>
<score type="match" t2="0" t1="0"/>
<events/>
<tournament name="Dummy" id="47715"/>
<category name="International" id="371"/>
<sport name="Squash" id="37"/>
<teams>
<team side="away" nationality="EE"/>
<team side="home" nationality="FM"/>
</teams>
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible 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: Squash full score (1834)

t1Amount of points home team.Integer
t2Amount of points away team.Integer
type

For what period in the match the points were scored.

String. Possible values:

  • match
  • game1
  • game2
  • game3
  • game4
  • game5
serveThis element always gets included, in both the full feed and the delta feed.
team

String. Possible values:

  • "home"
  • "away"
teamsThis element only gets included if this information is available (in major Squash Team Competitions)
team side

String. Possible values:

  • "home"
  • "away"
nationality2 digit country code2-digit country codes follow ISO3166
matchproperties

This element always gets included, in both the full feed and the delta feed.

Best of

Determines number of games.  How many sets are being played in the match.

Integer. Possible values:

  • 3
  • 5 (Default value)


Attributes in the <event> element

Code Block
languagexml
titleXML example
<match matchid="9512123">
<serve team="home"/>
<events>
<event extrainfo="1" gamenumber="2" gamescore="10:5" id="639568443" info="Stroke to [T2]" matchscore="1:0" mtime="0:29:32" side="
away" stime="1464363711000" type="1836"/>
</events>
</match>

XML attributes definition

ElementAttributes

AttributeDescriptionPossible values
eventextrainfo

Attribute containing additional information about the event.

Long
gamenumber

The number of the current game in the match.

Integer
gamescoreScore for current game.

String. Format: "[home]:[away]"
Example: "40:30"

matchscoreScore for current match.

String. Format: "[home]:[away]"
Example: "1:0"

XML configurations in Squash

(ID: 122) Include match status defaulted for Squash

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