SX Bet outcome IDs from matching now join to market detail
GET /v1/matching-markets/sports exists so you can take a provider's exact
native references and look them up on GET /v1/markets/{market_id}. For SX Bet
rows, half of that was broken: matching published outcome IDs shaped
<market_hash>:1 / <market_hash>:2, while market detail returned
outcomeOne / outcomeTwo for the same market. Two spellings for one
selection, and neither resolved on the other surface.
SX Bet rows now publish outcomeOne and outcomeTwo — in
canonical_events[].submarkets[].source_markets[].outcomes[].outcome_id and in
the default map's markets[].outcome_ids — which is byte-identical to what
market detail returns:
{
"platform": "SXBET",
"market_id": "0xb4d047a709aae881e5ccad9d123592967644ee1df1f17078c762b388e41b81c5",
"outcome_ids": [
- "0xb4d047a709aae881e5ccad9d123592967644ee1df1f17078c762b388e41b81c5:1",
- "0xb4d047a709aae881e5ccad9d123592967644ee1df1f17078c762b388e41b81c5:2"
+ "outcomeOne",
+ "outcomeTwo"
]
}Why this spelling. SX Bet publishes no per-outcome identifier at all: a
selection is a market hash plus one of exactly two positions. It encodes that
position several ways in its own API — an integer on the settled market record,
a boolean on orders and fills — but outcomeOne / outcomeTwo is the only one
that addresses a side, and it is how SX Bet's order-book snapshot keys its two
level arrays. The old composite was ours, not SX Bet's, and it duplicated the
market_id the same row already carries.
These IDs are market-scoped, like Kalshi's yes / no on market detail: read
them together with the row's market_id. If you were splitting on the colon to
recover the market hash, use market_id instead — it is the same value.
Polymarket, Predict and AlphaArcade rows are unchanged; their outcome IDs
already matched market detail. Kalshi rows are also unchanged and are still the
one provider whose matching outcome IDs do not round-trip — they are the sibling
market tickers under the event, with side naming the selection.