Data Requirements & Validation Rules
Even though all data points of the contract are suggested, here is a list of the main ones we require to provide basic funcionality.
Market Order
In order to maintain the order of markets we encourage you to maintain a timestamp called addedAt. This helps maintain the order of the markets on the BetVisionUI even after the user interacts in the experience.
Market Resolution
In order to show the market resolution in the BetVision UI we are not able to resolve them with our data because these markets do not pass through our system. This means we need you to provide enough data to resolve a market in the setUserBets.
These are the most important properties on the contract so we can resolve markets on our side:
market.status: Open, Settled or Cancelled. This lets us know if a user can interact with the market or if it already resolved.market.type: Single or Multi.market.selection.status: Won, Lost, Cancelled, Open. This lets us know the state of the selection, without this we cannotmarket.selection.type: Match Result, Union, Union Type.market.cashOutAvailable
Market Format
To correctly format a market on the BetVisionUI we require the following data points.
market.selection.pricemarket.currencymarket.payoutmarket.cashOutPricemarket.cashOutAvailablemarket.stakePerUnitmarket.selection.handicapnot required for all markets, but mostle for overunder betsmarket.selection.outcomenot required for all markets, but mostle for overunder