Binary markets
YES / NO on a single question. Settled through
CTFExchange
against ConditionalTokens.Neg-risk markets
3+ mutually exclusive outcomes. Settled through
NegRiskAdapterPredictStreetNegRiskCtfExchange.
Lifecycle
Listing markets
Polymarket-equivalent fields
| Field | Meaning |
|---|---|
groupItemTitle | Per-market label inside a multi-market event accordion ("Real Madrid", "Liverpool", "Draw"). Equal to title for single-market events. |
initialOutcomePrices | Per-outcome seed prices parallel to outcomeLabels. Polymarket calls this outcomePrices. |
On-chain identifiers
conditionId / questionId are the bytes32 hex values from
ConditionalTokens. yesTokenId
/ noTokenId are the ERC-1155 position ids you sign over in your
EIP-712 Order typed data. All four are null until the market’s
deployment is confirmed (status PRE_MARKET or beyond).
For multi-outcome (neg-risk) markets noTokenId is null — each
outcome is its own YES token managed by the
NegRiskAdapter. Pull the per-outcome
token ids from the on-chain adapter via the conditionId.
See Events overview for how markets group
under events and how to filter the public catalog.
Individual market detail
group, stage, teamA, teamB, tags, eventStartTime),
call GET /api/events/{id} with the event id from the parent grouping
(see the Events group in the API reference sidebar).
Orderbook snapshot
orderbook WebSocket channel —
polling is rate-limited and latency-inferior.