predictionMeta WebSocket channel uses the same payload. The standalone outcomeMarkets request has been removed.
Endpoint
Request Body
Response
Prediction markets
TheoutcomeMarkets field is an array. Each row preserves its venue’s identity and settlement fields.
For example, a Hyperliquid question in that array looks like:
venue: "polymarket", one question per
condition with one binary outcome. Only open (tradable) and resolved (redeemable) conditions
are listed. Names are not stored on the node, so name, description and side label are null:
tokenId (the venue identity, as hlEncoding is for Hyperliquid) and the
outcome carries conditionId (as outcomeId is for Hyperliquid). settleFraction is null before resolution. For a resolved condition with a recorded redemption
resolution, it is the stored payout numerator divided by the payout denominator, truncated to 20
decimal places for display. Redemption accounting uses the original exact ratio. If no resolution
record is available, the fraction remains null.
Question (Hyperliquid)
Outcome
Side
Use the side’s
assetId in the standard Notional order action. Do not send hlEncoding as the
order AssetId.
Use the outcome’s numeric outcomeId with
userOutcome.mergeOutcome to merge an equal
number of its Yes and No shares back into USDC. Do not use a side assetId or hlEncoding as the
merge outcome ID.
Hyperliquid rows include currently servable outcomes. Polymarket rows include registered open or
resolved conditions. Either venue can contribute no rows; outcomeMarkets is empty when neither
venue has servable markets. This registry does not include unregistered Polymarket discovery results.