Sport specific information about Aussie rules. Sport specific XML elements and attributesThis section explains what elements / attributes one can expect for aussie rules matches in addition to the standard elements and attributes. | Code Block |
|---|
| language | xml |
|---|
| title | XML example |
|---|
| <BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="alive" timestamp="1486304651489">
<Match active="1" betstatus="stopped" matchid="1003188316" msgnr="34" score="1:0" setscores="0:0" status="ended"
/>
</BetradarLiveOdds> |
| Element | Attributes |
|---|
| Attribute | Description | Possible values | | Match | setscores | Period_1 - Period_2 (aggregated score of all overtime sequences - score of 7 meter shooutout)) So maximum up to 5 scores while 3 and 4 are optional in case of overtime and/or penalty shootout. | String
For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1" |
XML configurationSport specific XML configuration for Aussie rules. (ID: 130) Multiple bets of same type active at once for Aussie Rules 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: 133) Remaining time in Aussie rulesEnable this config to include the remaining_time attribute for the entire match in addition to the regular matchtime in Aussie rules. | Code Block |
|---|
| language | xml |
|---|
| title | XML example |
|---|
| <BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="betstart" time="0" timestamp="1413331559002">
<Match active="1" betstatus="started" matchid="6139956" matchtime="1" msgnr="9" possession="2" position="70" remaining_time="60" score
="0:0" setscores="0:0" status="1q" try="1" yards="10"/>
</BetradarLiveOdds> |
(ID: 134) Remaining time in period for Aussie rulesEnable this config to include remaining_time_in_period attribute. in addition to the normal matchtime in Aussie rules. | Code Block |
|---|
| language | xml |
|---|
| title | XML example |
|---|
| <BetradarLiveOdds xmlns="http://www.betradar.com/BetradarLiveOdds" status="change" timestamp="1287056116518">
<Match active="1" betstatus="started" matchid="5876636" matchtime="1" msgnr="10" remaining_time_in_period="11:07" score="0:0"
setscores="0:0" status="1q">
</BetradarLiveOdds> |
Match statuses| ID | Status | Status description | Additional information |
|---|
| 0 | not_started | Not started yet | - | | 13 | 1q | 1st quarter | - | | 301 | pause1 | 1st pause | - | | 14 | 2q | 2nd quarter | - | | 302 | pause2 | 2nd pause | - | | 15 | 3q | 3rd quarter | - | | 303 | pause3 | 3rd pause | - | | 16 | 4q | 4th quarter | - | | 100 | ended | The match has ended | - | | 32 | awaiting_ot | Waiting for overtime to start | This match status is not used unless the corresponding XML configuration is enabled. | | 41 | 1p_ot | 1st overtime period | - | | 33 | ot_ht | Pause between 1st and 2nd overtime period | This match status is not used unless the corresponding XML configuration is enabled. | | 42 | 2p_ot | 2nd overtime period | - | | 110 | after_ot | Match finished after overtime | This match status is not used unless the corresponding XML configuration is enabled. | | 443 | awaiting_sd | Before sudden death | - | | 440 | SD | Sudden death | - | | 444 | after_sd | Match finished after sudden death | - | | 80 | interrupted | The match has been interrupted | - | | 90 | abandoned | The match has been abandoned | Status controlled by XML configuration. |
|