Sport specific information for snooker. Snooker specific XML elements and attributesThis section explains what elements, sub-elements and attributes one can expect for snooker matches in addition to the standard elements and attributes. | Code Block |
|---|
| language | xml |
|---|
| title | XML example |
|---|
| <BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="betstart" time="0" timestamp="1414574453652">
<Match active="1" betstatus="started" matchid="2097712" msgnr="5" remaining_reds="15" score="0:0" setscore1="0:0" status="in_progress"
visit="1"/>
</BetradarLiveOdds> |
XML attributes definition | Element | Attributes |
|---|
| Attribute | Description | Possible values | | Match | visit | Which player is currently visiting. | 1 = home team
2 = away team
0 = undefined | | remaining_reds | Number of remaining red balls. | Integer |
XML configurationsSport specific XML configurations for snooker. (ID: 78) Multiple bets of same type active at once for snooker 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. (ID: 127) Include snooker markets for frames which might not be playedIf set, then markets for frames which may not be played will be included in the feed, example frame 6 when matchscore is 4:0 in best of 9. Match statuses| ID | Status | Status description | Additional information |
|---|
| 0 | not_started | Not started yet | - | | 21 | in_progress | The match is in progress | - | | 30 | paused | Match paused | - | | 445 | session_break | Session break | - | | 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 start is delayed | - | | 80 | interrupted | The match has been interrupted | - | | 90 | abandoned | The match has been abandoned | Status controlled by XML configuration. |
|