...
* For these objects betting offer that is described below could be related in to our BetPartner product
Below you'll find a detailed explanation of some terms:
...
An event is a main object in our sports data structure. It describes a soccer match, a volleyball match, a formula 1 race or a cycling event as well. All events have a unique identificator. Each event always belongs to a season. An event could be optionally related with a stage and/or group. Each event has its own unique identificator and the structure of the event object is the same across all sports. An event could optionally belong to a Round e.g: Round 1, QuerterfinalQuarterfinal, etc. The rounds list can be found in the API resource: rounds.index
...
For each event we added Participants. For team sports like football, volleyball, ice hockey we added 2 participants to to an event e.g. Real Madrid and Barcelona. The number of participants related to an event could be higher for some sports e.g: formula 1, cycling, ski jumping. A Ski Jumping event contains 50 participants (each jumper is a participant for the event). We differentiate between the three types of participants (teams, persons individuals and doubles (used for tennis)).The participants list can be found in the API resource: participants.index. For each participant related to the event we will deliver Results and Statistics updated in real time and explained further below.
...
For some events we deliver lineups the lineup for each participant. This object includes the players starting and the names of all substitute players available for the event.
...
Everything that happens in an event is an incident. Incidents are sent out when the events are running. For each sport the list of incidents can be different. The complete list of possible incidents are available in the Incidents section.
Some examples of incidents:
Goal scored
Throw in
2pts 2pt shot scored
3pts 3pt shot missed
First half started
...
We differentiate between two types of betting offers: live and prematch. It's described by the attribute is_live_offer. For prematch odds the is_live_offer attribute has a "no" value, for live odds the value of this attribute is "yes". We start to offer live odds a few minutes before events start. The data structure of the betting object is the same for live and prematch odds.
...
| Betting offer type | Object type id | Object type | Object name | Market type | Market name | Outcomes |
|---|---|---|---|---|---|---|
| live | 34561 | event | Los Angeles Lakers - Utah Jazz | Totals | Totals |
|
| prematch | 325671 | event | Real Madrid - Barcelona | Main | 1x2 |
|
| prematch | 78912012 | season | Premiership 2015/16 | Outrights | Topscorers |
|
More information concering concerning betting offers and their structure is available at: betting-offers.index
...
Markets are related with betting offer. Each market has their it's own unique identificator, name, static name and market type. Additionaly Additionally for each market we defined default outcomes. Default outcomes are always assigned to a market and used when the same outcomes appears for that market every time e.g. "Odd/even" market is always decided between default "Odd" and "Even" and a "1x2" market always has always three possible outcomes: "Home", "Draw", "Away". the Subtype of the market defines number of possible outcomes for a particular market (2-way, 3-way-, n-way). Some markets are offered in a prematch odds feed, some could be offered in a live odds feed, some markets are offered in both types of odds. For some markets the scope is assigned to help you find market markets related to each m
Some markets and their default outcomes names includes replacers. Replacers is a pattern to generate final market or outcomes name for specific betting offer, e.g. for market name "Who will win #nextPoint# point" we use replacer #nextPoint# and that generates final market name: "Who will win 3. point". The similar situation occurs when default outcomes name for a market include replacer e.g. "Under #totalPoints#" -> "Under 195.5", etc.
...