soccer.match_odds and soccer.totals no longer returned by Feed API (regression since Feb 25, 2026) — any update?

[lasitosPT]

Summary

The Cloudbet Feed API stopped returning soccer.match_odds (1X2) and soccer.totals (over/under goals) markets for soccer events some time around February 25, 2026. This regression has been
reported in several prior discussions that have received no response from the technical team:

• #147 — Soccer Match Odds (opened Feb 25, 2026, confirmed by @dpamuklu, @tea-yy, @vezand)
• #158 — match_odds is missed in /events/{id}
• #142 — Most basketball games are missing the main markets
• #154 — Trading API returns all esports selections as DISABLED
• #155 — Discrepancy between website UI and API

I contacted live support (via the chat on cloudbet.com) and was explicitly redirected here: "API-related issues are being solved in GitHub discussions, not in the live chat." So I'm opening
this.

---

Account / key

• UUID: 4072b1e3-01f8-47e7-bd2d-c728401b6aa9
• Tier: trading (per decoded JWT access_tier)
• KYC: complete, USDC balance funded (~$50)
• Tested from both our server's IP and through a residential proxy — same result, ruling out geo-restriction.

---

Reproduction

1. Competition-level fetch (no filter)

GET https://sports-api.cloudbet.com/pub/v2/odds/competitions/soccer-england-premier-league
X-API-Key:

Actual response: 25 events. Across all of them, the following market keys are returned (with submarkets):

Count	Key
20/25	soccer.asian_handicap_period_second_half
20/25	soccer.correct_score_period_2nd_half
20/25	soccer.draw_no_bet_period_1h
20/25	soccer.exact_total_goals_period_second_half
20/25	soccer.halftime_fulltime_result
20/25	soccer.handicap_1x2_period_1h
20/25	soccer.match_odds_period_second_half
20/25	soccer.total_goals_period_second_half
10/25	soccer.both_teams_to_score
10/25	soccer.correct_score
10/25	soccer.draw_no_bet
0/25	soccer.match_odds — NOT RETURNED
0/25	soccer.totals — NOT RETURNED

2. With explicit market filter

GET /pub/v2/odds/competitions/soccer-england-premier-league?markets=soccer.match_odds&markets=soccer.totals

→ 25 events, every event has "markets": {} (empty).

Same result with camelCase (?markets=soccer.matchOdds&markets=soccer.totalGoals) per the official examples page.

3. Single-event fetch (Brighton vs Chelsea, kickoff 2026-04-21 19:00 UTC)

GET /pub/v2/odds/events/33981399

→ Same 21 market keys as above, no soccer.match_odds or soccer.totals.

4. Sanity-check that period-second-half is NOT a relabelled full-match market

Compared soccer.match_odds_period_second_half odds with aggregate bookmaker 1X2 published odds for the same match:

	Home (Brighton)	Draw	Away (Chelsea)
Aggregate market (published full-match)	2.52	3.86	2.78
Cloudbet _period_second_half	2.68	2.75	2.91

The implied draw probability (~36% vs ~26%) confirms the _period_second_half market is genuinely second-half-only and cannot be substituted for the full-match 1X2.

---

Impact

Any API consumer that integrates against the documented soccer.match_odds / soccer.totals keys — as described in your own schema gist
(markets.json) and tutorial examples — is currently
unable to place full-match bets through the API. This breaks any automated-trading integration that relies on the documented behavior.

---

Questions

1. Is this a known regression with an ETA for a fix?
2. Is this a silent restriction on my tier that docs haven't been updated to reflect? If so, what are the requirements to have full-match markets re-enabled for my API key?
3. Is there a different endpoint, flag, or header that returns these markets that I've missed?
4. Is the Market Helper expected to reconstruct soccer.match_odds from some other market that is returned (I checked — it doesn't)?

Any response — even just "we see it, working on it" — would be hugely appreciated. A two-month silence on an issue that breaks the documented API contract is tough for anyone building on top of
Cloudbet.

Thanks.