This type of message is sent through AMQP service when indicated group of betting offerschanges are made in the event e.g. stats were edited/corrected or event start date was changed etc.
‘Bet_stop’ 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 be achieved by sending an odds-changes message that lists all the affected markets and moves them to status="suspended".
...
offers should change their status to suspended or closed.
Message structure
| .message | |
|---|---|
| id | For this message type id attribute has no value. |
| type | bet_stop |
| source | Internal attribute, please dont use this attribute |
| ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP |
| ..data | |
| ...bet_stop | |
| object_id | Identifier of the object depends on object type, e.g. if you choose an event as an object_type you should use event identificator |
| object_type | Possible object type:
|
| action | Describes type of operation. For this message type, action attribute always has create value |
| betting_offer_ids | List of betting offers identifiers separated by a comma (e.g. 123,234,321). Possibility to input multiple identifiers, separated by comma. If empty value ALL betting offers for specified object_id should be suspended or closed. |
| betting_offer_status | The betting offers specified in betting_offer_ids attribute can receive following values:
|