Markets Information
Bayes Live Odds provides you access to key markets which account for ~95% of betting turnover, as well as to a wide range of additional proposition markets (props).
Key markets
Market | Description |
---|---|
Match (Fixture) Winner | The simplest and most common kind of bet, a Match (Fixture) Winner allows bets to be made on a team to win a match |
Map Winner | This is an in-play bet you can make on a team to win a map in a match. |
Map Handicap | Handicap, also referred to as the 'spread', involves giving one team a virtual map deficit (a handicap) to overcome at the start of a game. Example: In a best-of-three match for Counter-Strike match between two teams, an odds provider believes Team A is the underdogs so assigns a +3.5 round handicap for the first match. This gives Team A a 3.5-round advantage on a map so you decide to place a bet. To win the bet, Team A needs to win at least 13 rounds (in the first to 16 scenarios) in the match. Put simply, Team A cannot lose by more than four rounds for you to win the bet. Alternatively, an odds provider believes Team B is stronger than their opponents so assigns this team a -3.5 round handicap for the first match. This gives Team B a 3.5-round disadvantage on a map. If you decide to place a bet, Team B must win by at least 16-12 or by a larger margin for you to win. Simply, Team B needs to win by four rounds or more for you to win the bet. |
Proposition markets (props)
Prop markets – also known as proposition bets – are betting markets beyond the standard ones. Prop bets focus on segmented parts of a game, such as individual team or player performances as well as specific in-game events and happenings during the game.
Market | Description |
---|---|
Match markets | Betting on a specific outcome of a match. Example: “Exact score of the match (in maps)” |
Map markets | Betting on a specific outcome of a map Example: “Number of towers destroyed in on a map by both teams” |
Team markets | Betting on a a team stats for a game Example: “Kills Total for Team B to be over 32.5” |
Player markets | Betting on an individual player’s stats for a game, also known as player props Example: “Player X will have 20 or more kills” |
Flash markets | Betting on specific in-game events and outcomes Example: “Which team will kill the next dragon?” |
Market Naming
Bayes Odds Feed markets will be uniquely identified by the combination of two data fields:
market_name
market_type
market_name | market_type |
---|---|
map_winner_maintime_3way | 3way |
map_total_rounds | exact |
match_rounds_handicap | 2way |
match_total_rounds | overunder |
map_team_wins_pistol_rounds | yesno |
market_name
A naming convention for Bayes Odds Feed markets will adhere to the following pattern:
{match/map}_?{team/player/map}_{description}
market_type
Each market falls into one of the following categories:
Market type | Description |
---|---|
2way | Market with two possible outcomes, often win or lose Example: ”Team A will win the first map” |
3way | Market with three possible outcomes, often win or lose or draw |
exact | Bet on the exact value of some game parameter. Example: ”There will be 20 rounds in Counter-Strike match” |
yesno | Bet on a game parameter being True/False. Example: ”There will be a rampage in DotA game” |
overunder | Bet on some game parameter being over or under the specified value. Example: ”The number of rounds in Counter-Strike match will be under 25” |
oddeven | Bet on some game value being an odd or an even number. Example: ”The number of maps played in the final of DotA match will be odd” |
Market outcomes
Each outcome in a market represents a result of the event that the market stands for. The odds of an outcome reflect the perceived likelihood of that outcome.
Each OddsUpdateMessage
contains a list of markets in the markets
field. Each of these markets then contains a list of outcomes in the outcomes
field. Each outcome has the following structure:
Field | Description | Type |
---|---|---|
outcome | the outcome name | String |
decimalOdd | the odds of the outcome in decimal format | Float |
tradingStatus | the trading status of the outcome | String |
won | the result of the outcome (True or False) | Boolean |
Trading status
An outcome can have one of five trading statuses that indicate whether bets can be made, are no longer allowed, should be paid out or betting has been paused. Each market can have outcomes that have different trading statuses. Imagine an exact score market in a match with a score of 2:0. All outcomes for scores that are not possible anymore (like 0:0, 0:1, 1:1, 1:2,...) should not be bettable on while score outcomes that are still possible (2:0, 2:1:, 3:0,...) can be bet on.
Trading statuses
Trading status | Description |
---|---|
open | The market is currently open for bets |
closed | The market is now closed, no more bets should be accepted |
settled | The market outcome is known (e.g. which team won the first match) and bets should be paid out if the won field of the outcome is set to True |
suspended | Betting is temporarily paused and the odds are temporarily frozen. Possible reasons for a market suspension include: the probability for a market outcome to happen is very high or very low there are integrity concerns, the market is suspended and pending investigation * traders decide to manually pause trading for some other reason |
cancelled | The market outcome is cancelled, all bets should be refunded. Possible reasons for cancellation include: a match is cancelled or interrupted a player expected to appear in the match did not play the map was not played (e.g. map 3 of a best-of-3 match) in some markets the bettors are refunded on specific events (e.g. in Draw No Bet markets when a draw occurs) |