...
| Child pages (Children Display) |
|---|
The complete list of possible incidents can be retrieved using the API resource: incidents.index
The main idea behind incidents is, everything that occurs in a sporting event is an incident (goals scored, cards received, corner taken etc.). Incidents are sent out while the sport events are running. For some incidents we deliver additional information described in Participant and Add info columns. The column Important for trader contains our suggestions that a particular incident should be consider in the odds compiling process. Please note that new incidents can be added to the system in the future.
The most important incidents related to all sports are betstart and betstop, these are described below. Please note that these incidents, for all sports, have the same identificator.
Incident Id | Incident name | Is important for trader | Participant | Add info possible values | Add info format | Note |
|---|---|---|---|---|---|---|
1000 | Betstart | Yes | This means that clients can accept bets from their customers. This incident will also change the bet_status attribute value in event object to "active" | |||
1010 | Betstop | Yes | This means that clients should not accept bets form their customers. This incident will also change the bet_status attribute value in event object to "suspended". The reasons why we sent a betstop incident are listed below:
|
The complete list of possible incidents for all sports are listed below.
| Child pages (Children Display) |
|---|