Replies: 2 comments 2 replies
-
|
I am observing inconsistencies between the sportsbook web UI and the API responses for the same markets. For identical selections (e.g., 1X2, Asian Handicap, and Totals), the prices shown in the UI do not match the prices returned by the API at the same time. The differences are significant and exceed normal rounding or minor timing delays. Additionally, the probability values in the API do not reconcile with the corresponding price fields (e.g., implied probability from price does not match the provided probability). Please investigate whether the UI and API are sourcing odds from different feeds or snapshots, whether there is caching or websocket-based updates affecting the UI, and clarify the intended meaning of the probability field in the API. |
Beta Was this translation helpful? Give feedback.
-
|
Confirming the same regression 2 months later (April 21, 2026). Account 4072b1e3-..., trading-tier. /pub/v2/odds/competitions/soccer-england-premier-league returns 25 events with zero soccer.match_odds, zero soccer.totals; only soccer.match_odds_period_second_half, halftime_fulltime_result, BTTS/correct_score/draw_no_bet remain. Filtering ?markets=soccer.match_odds returns empty markets: {}. Affects every event across PL / La Liga / Bundesliga / Serie A / Primeira Liga. Is this a tier restriction or the same data pipeline issue reported by @dpamuklu? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
Since yesterday, I cannot reach out soccer.match_odds in the api. The key soccer.match_odds is no longer appearing in the response. Somethings changed?
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions