Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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_stopis 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".

Specified group of markets for a specified sport event should all change their market status to either suspended or deactivated.


Message structure

.message
id

For this message type id attribute has no value.

type

bet_stop

sourceInternal attribute, please dont use this attribute
utInformation 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



The complete list of possible seasons can be retrieved using the API resource: seasons.index
The complete list of possible events can be retrieved using the API resource: events.index

object_type

Possible object type:

  • season - for betting offers related to the season e.g: Premiership 2015/2016
  • event - for betting offer related to the event e.g: Real Madryt - Barcelona
action

Describes type of operation. For this message type, action attribute always has create value









  • No labels