Sport specific information for bowls. Sport specific XML elements and attributesThis section explains what elements / attributes one can expect for bowls matches in addition to the standard elements and attributes. | Code Block |
|---|
| language | xml |
|---|
| title | XML example |
|---|
| <BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="betstop" time="0" timestamp="1413458626905" type="
scoutmatch">
<Match active="1" betstatus="stopped" matchid="4977471" msgnr="5" score="0.0:0.0" setscores="0:0" status="1set" remaining_bowls_home
="3" remaining_bowls_away="4" current_end="1" delivery="2"/>
</BetradarLiveOdds> |
| Element | Attributes |
|---|
| Attribute | Description | Possible values | | Match | delivery | The player which will deliver the next bowl | 1 = home
2 = away | | remaining_bowls_home | The remaining bowls for the home team. | Number >= 0 | | remaining_bowls_away | The remaining bowls for the away team. | Number >= 0 | | current_end | Current end in set. | Integer |
XML configurationsSport specific XML configurations for bowls. (ID: 92) Multiple bets of same type active at once for bowls matchesThe Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total 1.5 and 3.5 would be sent as well. Match statuses| ID | Status | Status description | Additional information |
|---|
| 0 | not_started | Not started yet | - | | 8 | 1set | 1st set | - | | 301 | pause1 | 1st pause | - | | 9 | 2set | 2nd set | - | | 302 | pause2 | 2nd pause | - | | 10 | 3set | 3rd set | - | | 303 | pause3 | 3rd pause | - | | 11 | 4set | 4th set | - | | 304 | pause4 | 4th pause | - | | 12 | 5set | 5th set | - | | 100 | ended | The match has ended | - | | 93 | walkover walkover1 | The home team won the match by walkover | Status controlled by XML configuration. | | 94 | walkover walkover2 | The away team won the match by walkover | Status controlled by XML configuration. | | 95 | retired retired1 | The away team won because the home team retired | Status controlled by XML configuration. | | 96 | retired retired2 | The home team won because the away team retired | Status controlled by XML configuration. | | 97 | defaulted1 | The away team won because the home team defaulted | - | | 98 | defaulted2 | The home team won because the away team retired | - | | 61 | delayed | The match has been delayed | - | | 80 | interrupted | The match has been interrupted | - | | 90 | abandoned | The match has been abandoned | Status controlled by XML configuration. |
|