Versions Compared

Old Version 25

changes.mady.by.user FormerUser1

Saved on

compared with

New Version 26

changes.mady.by.user Matthew Francis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt
Info
The complete list of possible incidents can be retrieved using the API resource: incidents.index

The main idea of the behind incidents, is that everything that occurs in a sport sporting event is an incident (goals scored, cards received, corner taken etc.). Incidents are sent out when 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 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 for to all sports are betstart and betstop, these are described below. Please note that these incidents for all sports has have the same identificator.

Incident IdIncident nameIs important for traderParticipantAdd info possible valuesAdd info formatNote
1000BetstartYes   

It 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"

1010BetstopYes   

It This means that clients should not accept the bets form theirs their customers. This incident will also change the bet_status attribute value in event object to "suspended". The reasons where why we sent a betstop incident are listed below:

  • any technical problems
  • lost connection with scouts
  • any an important incident occurs


The complete list of possible incidents for all sports are listed below. 

Child pages (Children Display)

...