LD - Rugby

Sport specific information for rugby.

Match statuses in rugby

Events in rugby

Sport specific XML elements and attributes

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

Attributes in the <match> element

<match betstatus="BETSTOP" connectionstatus="0" device="4" extrainfo="0" feedtype="full" matchid="10115219" matchtime="07:00 +1615:28"
start="1464771120000" t1id="5794272" t1name="BATH RUGBY" t2id="5815403" t2name="SALE SHARKS" timerunning="1">
...
</match>

XML elements and attributes definition

Elements in the <match> element

<match betstatus="BETSTOP" connectionstatus="0" device="4" extrainfo="0" feedtype="full" matchid="10115219" matchtime="07:00 +1615:28"
start="1464771120000" t1id="5794272" t1name="BATH RUGBY" t2id="5815403" t2name="SALE SHARKS" timerunning="1">
<status id="6" name="FIRST_HALF" start="1464770875358"/>
<score t1="7" t2="14" type="current"/>
<score t1="7" t2="7" type="period1"/>
<score t1="0" t2="7" type="period2"/>
<possession team="home"/>
<red t1="0" t2="0"/>
<yellow t1="0" t2="0"/>
<weatherconditions id="0" name="UNKNOWN"/>
<pitchconditions id="0" name="UNKNOWN"/>
<matchformat>
<format type="numberofperiods" value="2"/>
<format type="periodlength" value="7"/>
<format type="tryvalue" value="5"/>
<format type="conversionvalue" value="2"/>
<format type="penaltyvalue" value="3"/>
<format type="dropgoalvalue" value="3"/>
<format type="penaltytryvalue" value="5"/>
<format type="numberovertimeperiods" value="2"/>
<format type="lengthovertimeperiods" value="10"/>
<format type="lengthsuddendeath" value="10"/>
<format type="penaltyshootout" value="1"/>
</matchformat>
<tournament id="17101" name="Premiership Rugby 7s"/>
<category id="1118" name="Rugby Union Sevens"/>
<sport id="12" name="Rugby"/>
<events/>
</match>

XML elements and attributes definition

Elements and attributes in the <matchformat> element

If extra attributes are needed to specify the match format, those will be added in the <matchformat>-element, which holds <format>-elements for each match format option. The actual formats are described in the type and value attributes.

<match betstatus="BETSTOP" connectionstatus="0" device="4" extrainfo="0" feedtype="full" matchid="10115219" matchtime="07:00 +1615:28"
start="1464771120000" t1id="5794272" t1name="BATH RUGBY" t2id="5815403" t2name="SALE SHARKS" timerunning="1">
<status id="6" name="FIRST_HALF" start="1464770875358"/>
<format type="numberofperiods" value="2"/>
<format type="periodlength" value="7"/>
<format type="tryvalue" value="5"/>
<format type="conversionvalue" value="2"/>
<format type="penaltyvalue" value="3"/>
<format type="dropgoalvalue" value="3"/>
<format type="penaltytryvalue" value="5"/>
<format type="numberovertimeperiods" value="2"/>
<format type="lengthovertimeperiods" value="10"/>
<format type="lengthsuddendeath" value="10"/>
<format type="penaltyshootout" value="1"/>
</matchformat>
...
</match>

Possible values type and value attributes for rugby

Attributes in the <event> element

<match matchid="10118809" ... >
<events>
<event extrainfo="14693821" id="14693842" info="Event deleted : Score missed rugby" matchscore="50:39" mtime="80:00" periodnumber=
"4" remainingtimeperiod="00:00" side="away" stime="1465896960776" type="1044"/>
</events>
</match>

XML attributes definition

Additional sport specific information

Coordinates system:

For rugby we offer positions on the pitch for events (posx / posy) in a slightly different way than for deep
coverage soccer and tennis.

The field has dimensions of 110 x 70 meters. Unlike for other sports, positions on the field are expressed in meters rather than in percentages. Position (0,0) is located in the top-left corner of the field, therefore point (110,70) is located at the opposite bottom-right corner. In this case the central point of the field is (55,35). In addition, it is possible to receive positions from outside the pitch. If received position has value X less than 0, the current position is on the left side of left "dead ball line" (the outermost field line). If X is greater than 110, the current position is on the right side of right "dead ball line". If coordinate Y is less than 0, the current position is out of bounds above the pitch. If it’s greater than 70, the current position is out of bounds below the pitch Rugby reflects both Rugby League and Rugby Union, they are provided under the same sport id, but different category-ID.

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: 65) Send periodx score types for rugby

The attribute type in the <score> element (subelement from <match> element) has a set list of possible values. If this setting is enabled, the attribute type can have one of the following values, in addition to the regular values for rugby matches:

• period1
• period2

<match matchid="7440630" ... >
<score t1="14" t2="20" type="period1"/>
<!-- Remaining message truncated -->
</match>

(ID: 69) Include matchformat elements for rugby matches

Enabling this setting will add the element <matchformat> as subelement to the <match> element for rugby matches when available.

<match betstatus="BETSTOP" feedtype="full" matchid="1038619" ...>
...
<matchformat>
<format type="numberofperiods" value="2"/>
<format type="periodlength" value="40"/>
<format type="tryvalue" value="5"/>
<format type="conversionvalue" value="2"/>
<format type="penaltyvalue" value="3"/>
<format type="dropgoalvalue" value="3"/>
<format type="penaltytryvalue" value="5"/>
<format type="numberovertimeperiods" value="0"/>
<format type="lengthovertimeperiods" value="0"/>
<format type="lengthsuddendeath" value="0"/>
<format type="penaltyshootout" value="1"/>
</matchformat>
</match>

(ID: 104) Send lineups for rugby matches where this is available

If this setting is enabled, the element <lineups> gets enabled for matches which have this configured. Lineups are sent when subscribing to a match, and when the lineup changes.

<lineups matchid="6856980">
<player id="560834" name="Jiang, Jiajun" shirtnumber="5" substitute="false" team="1"/>
<player id="802814" name="Yang, Jiawei" shirtnumber="7" substitute="false" team="1"/>
<!-- Remaining message truncated -->
</lineups>

(ID: 135) Include early betstatus for Rugby

Right before one of the teams scores a goal, the match status will be set to betstop. Normally, the match will be on betstop until the match continues, which is after the next kick off. As bookmakers have different requirements in terms of reoffering markets after goals, Betradar allows you to enable early betstart. If you have this setting enabled, information related to early betstart will be sent in addition to the normal betstart information.

The behaviour of early betstart is quite similar to the normal betstart, but instead of waiting until the next kick off, early betstart already starts right after the goal was confirmed.

If the match is in either betstart or early betstart, the match can be treated as betstart. It is up to the bookmaker to decide whether to receive the new prices right after the score change or after the match continues.

(ID: 126) Include player positions in lineup in Rugby

If this setting is enabled, the attribute position gets added to the <player> element, for matches which this is set up. A full list with possible values for this attribute can be found in the XSD.

<lineups matchid="1062714">
<player id="521" name="Almunia, Manuel" shirtnumber="1" substitute="false" team="1" position="G"/>
<player id="518" name="Fabregas, Cesc" shirtnumber="4" substitute="false" team="1" position="D"/>
<player id="15479" name="Fabianski, Lukasz" shirtnumber="12" substitute="false" team="1" position="M"/>
<!-- Remaining message truncated -->
</lineups>