Betradar Documentation

Betradar - the betting arm of Sportradar

Page tree

Betradar - the betting arm of Sportradar

Skip to end of metadata
Go to start of metadata

Sport specific information for bowls.

Match statuses in bowls

Table Filter Plugin license is not active, please generate a trial license or purchase the product.

IDMatch statusDescriptionAdditional information
0NOT_STARTEDNot started yet-
8FIRST_SET1st set-
301FIRST_PAUSE1st pause-
9SECOND_SET2nd set-
302SECOND_PAUSE2nd pause-
10THIRD_SET3rd set-
303THIRD_PAUSE3rd pause-
11FOURTH_SET4th set-
304FOURTH_PAUSE4th pause-
12FIFTH_SET5th set-
100ENDEDThe match has ended-
93WALKOVER1

The 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

-
97DEFAULTED1

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.

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 bowls

Table Filter Plugin license is not active, please generate a trial license or purchase the product.

IDEventDescriptionCoverageextrainfoextrainfobowls
1010BetstartBetstart indicates that betting markets can be activated. Betstart is not only a pre-match event but is also used during the match.XSA (BC)--
1011Betstop

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.

XSA (BC)--
1013Match status

Sent when the status of the match changes.

XSA (BC)See above table for all match statuses for bowls-
1015Free commentUsed for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..


XSA (BC)--
1022Who throws first bowlInformation about who will throw the first bowl.XSA (BC)--
1024Match about to startThis event is sent when both captains, together with the referee, are selecting which team will start the match.


XSA (BC)--
1036Time started/ stoppedTriggered when the clock is started or stopped.XSA (BC)

Values:

  • 0 = time stopped
  • 1 = time started
-
1044Event deletion alert

Manual removal of an event.

XSA (BC)Id of event that was deleted.-
1102Coverage statusSent when the coverage status for the match changesXSA (BC)

Possible values:

  • 0 = Covered
  • 1 = Coverage abandoned
  • 2 = Match will not be covered
-
1112Match stopSent when a match needs to be stoppedXSA (BC)

Possible values:

  • 0 = Undefined reason
  • 1 = Weather conditions
  • 3 = Injury
  • 11 = Facility delay
-
1113Match stop overThe match resumes after being stoppedXSA (BC)--
 1120Who won coin toss Information about what player won the coin toss.XSA (BC)--
1121Who made first server decisionThe winner of the coin toss decides who throws the first bowl.XSA (BC)--
1179Players walking on Sent when the player walks on to the action.XSA (BC)--
1500Score changeScore ChangeXSA (BC)

Score change type. Possible values:

  • 1 = End
  • 2 = Set
  • 3 = Match
End number of set number.
1501Bowler startsSent before each bowl or jackXSA (BC)-

Value: "x;y"

  • x = 1 (jack) , 0 (bowl) or -1 (don’t want to play).
  • y = 0 (jack) or 1,...,9 (bowl number).
1502Jack rollJack rollXSA (BC)Jack distance in meters-
1503Redeliver jackSent when the jack will be redelivered due to any reasonXSA (BC)--
1504BowlBowl rollXSA (BC)

Possible values:

  • 0 = Forehand
  • 1 = Drive
  • 2 = Backhand

Value: "x;y;z"

  • x = Score (e.g. 0:0, 3:0, 0:2).
  • y = 0 (normal), 1 (toucher) or 2 (dead bowl).
  • z = Bowl number.
1505WarningWarningXSA (BC)--
1506Restart endRestart EndXSA (BC)--
1507Dead endDead end


XSA (BC))--
1508Dead jackDead JackXSA (BC)--

1510

Replay bowlReplay bowlXSA (BC)Bowls number-
1511DisqualificationDisqualificationXSA (BC)--
1512End startEnd StartXSA (BC)End numbers

Possible values:

  • 0 = Bowling from North End
  • 1 = Bowling from South End
1513Trial endTrial endXSA (BC)--
1514Start delayedStart delayedXSA (BC)--
1515Bowls match formatBowls Match FormatXSA (BC)Number of sets

Value: "x;y;z;w"

  • x = Number of ends per set.
  • y = Number of ends in TB.
  • z = End play through. (0 or 1).
  • w = Is TB best of (0 or 1).
1516First set awardedFirst set awarded in bowlsXSA (BC)--

1666


Bowls colorBowls colorXSA (BC)-

Value: "x:y"

  • x = New home color
  • y = New away color


Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for bowls 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" device="4" extrainfo="0" feedtype="full" matchid="10115537" matchtime="0:00:00" start="
1464869040000" t1id="6945699" t1name="BLUNDSTONE MELBOURNE ROYS" t2id="6945701" t2name="MESSENGER PRESS
ADELAIDE ENDURANCE">
...
</match>

XML elements and attributes definition

ElementAttributes

AttributeDescriptionPossible values
Matchfirstservetiebreak

Which player has first serve in the tiebreak.

Integer
firstserve

Which player has first serve of match.

Integer

Elements in <match> element

XML example
<match betstatus="BETSTOP" connectionstatus="0" device="4" extrainfo="0" feedtype="full" matchid="10115537" matchtime="0:00:00" start="
1464869040000" t1id="6945699" t1name="BLUNDSTONE MELBOURNE ROYS" t2id="6945701" t2name="MESSENGER PRESS
ADELAIDE ENDURANCE">
<status id="0" name="NOT_STARTED" start="0"/>
<score t1="0.0" t2="0.0" type="match"/>
<score t1="0" t2="0" type="end"/>
<serve team="home"/>
<tournament id="31241" name="Premier League"/>
<category id="945" name="Australia"/>
<sport id="32" name="Bowls"/>
<events/>
</match>

XML elements and attributes definition

ElementAttributes

AttributesDescriptionPossible 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:

Bowls score change (1500)

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
  • end
serveThis element always gets included, in both the full feed and the delta feed.
teamWhich team served.

String. Possible values:

  • "home"
  • "away"

Attributes in <event> element

XML example
<match matchid="9403865" ... >
<events>
<event endscore="1:0" extrainfo="0" extrainfobowls="0:1;0;2" id="651693461" info="[T2] bowl 2 (Forehand) lying 1" matchscore="1.0:1.0"
mtime="1:01:11" setnumber="3" setscore="1:0" side="away" stime="1465804878033" type="1504"/>
</events>
</match>

XML attributes definition

ElementAttributes


AttributeDescriptionPossible values
eventextrainfo

Attribute containing additional information
about the event.

Long
extrainfobowls

Attribute containing additional information
about the event.

String
endscore

setnumber

The number of the current set in the
match.

Integer
setscoreScore for current set.

String. Format: "[home]:[away]"
Example: "5:4"

matchscoreScore for current match.

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

XML configurations for Bowls

(ID: 119) Include match status defaulted

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

Back to top


Betradar - the betting arm of Sportradar