Over/Under 0.5 odds
Two questions:
1. Is the Over 0.5 goals line syndicated in your in-play odds feed at
all? If yes, under what market code? I'm currently probing for
'over_under_05' and '[email protected]' outcome slugs — is that correct, or
is 0.5 delivered under a different market key (e.g. next_goal,
total_goals, match_goals)?
2. If Over 0.5 isn't in the standard comparison endpoint, is there a
different endpoint or add-on that carries it? I'd also take
"next goal yes/no" as an equivalent market if that's available
in-play.
Resolution: over_under_05 added to ODDS_MARKET_ENUM + MARKET_OUTCOMES (public/v2_odds.py) and to _KIND_LINE_TO_LEGACY / _LEGACY_CODE_REGEX / _LEGACY_OUTCOME_TO_SELECTION (oddsfeed/api_compat.py). Data was already there (493k rows, 66k in-play); only the enum was blocking it. No next-goal market exists in the feed.
Comments
1
Bzzoiro · Admin
Aug 22, 2026 09:24
Short answer: yes, Over 0.5 is in the feed, in-play included — but neither of the
slugs you were probing was right, and until today the market was not reachable
through the public API at all. It is now.
1. The market key is over_under_05, with outcome over or under.
GET /api/v2/odds/?market=over_under_05&outcome=over&league_id=49
Not over_under_05 as an outcome slug, and not [email protected] — outcome and market are
separate parameters here, and the line comes back in its own line field (0.5).
The other keys you guessed (next_goal, total_goals, match_goals) do not exist.
Anything outside the market enum returns 400 with the valid list in the body, so
probing blind will always tell you what it accepts.
2. It was not you. The enum behind that endpoint only listed 1.5, 2.5 and 3.5, so
over_under_05 was rejected as an invalid market even though the prices were
sitting in the database the whole time. I added it today — same endpoint, no new
route, no add-on.
What you get: roughly 493,000 football prices across about 14,700 fixtures, of
which around 66,000 are in-play, from 1xBet, Bet365, William Hill, Bwin, Betano,
888Sport, Novibet, SportingBet, Interwetten and the rest of the tracked book list.
Half-time 0.5 lines exist in the data as well; the public endpoint serves full-time.
One thing worth knowing before you build against it: about a third of the fixtures
carrying odds are matched to a fixture in our own events table, so rows for the
rest come back with event_id null. If you need the fixture attached, filter by
league_id or event_id and you only get matched ones.
3. Next goal yes/no is not carried. The feed has no next-goal market for football,
so there is nothing I can point you at as an equivalent — I would rather say that
than sell you a lookalike.
Bzzoiro
Log in to comment.