Full-time soccer markets always return SELECTION_DISABLED with maxStake=0 via Feed API, while second-half and exotic markets are enabled

[oremantovani]

Using a Trading API key, GET /v2/odds/events/{id} returns HTTP 200 with a normal payload, but every full-time soccer market comes back disabled with a zero max stake. Second-half and exotic markets on the same event are enabled and priced normally.

Example — event 36089854 (AEK Athens v LASK, soccer-international-clubs-uefa-champions-league):

soccer.match_odds  (submarket period=ft)
  home    price 0    SELECTION_DISABLED   maxStake 0   probability 0
  draw    price 0    SELECTION_DISABLED   maxStake 0   probability 0
  away    price 0    SELECTION_DISABLED   maxStake 0   probability 0

soccer.total_goals (submarket period=ft)
  over  total=2.5    price 0   SELECTION_DISABLED   maxStake 0
  under total=2.5    price 0   SELECTION_DISABLED   maxStake 0
  (identical for total = 2, 2.25, 2.75, 3, 3.25, 3.5, 3.75, 4)

soccer.match_odds_period_second_half
  home  2.06   SELECTION_ENABLED   maxStake 54.4
  draw  2.71   SELECTION_ENABLED
  away  3.91   SELECTION_ENABLED

soccer.total_goals_period_second_half
  over  total=1.5   1.91   SELECTION_ENABLED

Corners, cards, HT/FT and anytime-goalscorer markets are also enabled with positive maxStake on the same event.

What I've ruled out

• Not event-specific: same pattern on every event I check, across Champions League, Premier League, League One and Brasileirão.
• Not transient: persists for hours, not minutes.
• Not a bad market key: the keys and submarket params match the docs, and non-FT variants of the same markets work fine.
• Not a request-format issue: same response with and without the markets filter, and with currency=USDC and currency=BTC.
• Not a wrong key type: the key is a Trading key.
• Not reflected on the site: the same events show Full Time Result and Total Goals as active and priced when logged in via the browser (1.75 / 3.90 / 4.15 for the example above).

The key has never been used to place a bet.

Question

What causes period=ft selections to return SELECTION_DISABLED with maxStake: 0 while other periods on the same event are enabled? Support told me there is no documented account-level or key-level setting that disables specific markets, so I'd like to understand what else produces this. If it's a regional or data-provider restriction, is there a way to see that from the API response?

Thanks.

[kgravenreuth]

it s related to #170