The bet_stop message is an optimized signal to indicate that all, or a set of markets should be instantly suspended (continue to display odds, but don't accept tickets). The same effect can also be achieved by sending an odds_change message that lists all the affected markets and moves them to status="-1" (suspended).
It is important to keep in mind that only active markets should be set to suspended, and not markets that are already deactivated, settled or cancelled. This is also the case for the attribute market_status (explained HERE). If it is not present, the market should be moved to suspended. However, if the market is already deactivated, settled or cancelled this is not a good practice. Only move ACTIVE markets to suspended.
The bet_stop is sent very rapidly, as soon as a Betradar operator detects an issue. At the time the bet_stop is sent, the cause for the betstop is not always available (typically not for live matches). The cause of the bet_stop is provided in a subsequent odds_change message (see THIS section for more details.).
| Attribute | Description |
|---|
timestamp | The timestamp (milliseconds since epoch UTC) for this message. |
product
| The Betradar producer that is sending this message (1=LiveOdds, 2=MTS, 3=BetradarCtrl, 4=BetPal, 5=Premium Cricket). See the endpoint descriptions/producers.xml for a listing of current producers. |
event_id | What sport event this message refers to. |
groups | A description of which set of markets should be suspended – the value should be a group-name as can be seen in the market-descriptions (‘all’ is a special keyword that means all markets for this event). |
market_status | If not present, the markets specified should be moved to suspended. If present, they should be either suspended or deactivated based on the value of this field. |
| betstop_reason | If present, describes the reason for the bet stop. The betstop_reason should NOT be used to trigger a bet_stop on the customer side. This is an additional attribute with information that is set by our scouts in order to inform customers why a certain bet_stop was set. This attribute is OPTIONAL and there are scenarios where no betstop_reason will be sent. NOTE: Not all producers use this attribute either (i.e: The Ctrl producer). |
<bet_stop timestamp="12345" product="3" event_id="sr:match:471123" groups="all"/>
The above XML example indicates the bet_stop. The attribute "groups" defines which markets should go to bet_stop (or be closed/deactivated). Currently it is by default set to "all". If a bet_stop message is received, all markets should go to betstop/should be closed.
After the betstop message is received you will find the markets which should be on betstop with the market status attribute set to "-1" in a subsequent odds_change message. As long as a certain market does not change to status="1", it should be on betstop/closed on the customer side.
If a certain market goes to status="1" it would be open (betstart) for betting again.
