Outcome Balances

Hyperliquid

Returns a user’s non-zero Hyperliquid-routed outcome-share balances and held quantities.

Endpoints

Preferred unified request:

POST /info

{
  "type": "outcomeBalances",
  "user": "0x1111111111111111111111111111111111111111"
}

Compatibility GET request:

GET /outcome/balances?user=0x1111111111111111111111111111111111111111

The GET endpoint also accepts the wallet address through the x-wallet header.

Response

200: Balances

[
  {
    "assetId": "0004000005f77024",
    "hlEncoding": 100102180,
    "label": "Below 4.3% Yes",
    "questionId": 820,
    "outcomeId": 10218,
    "sideIndex": 0,
    "total": "12",
    "hold": "3",
    "entryNtl": "6"
  }
]

Fields

Field	Meaning
`assetId`	16-character AssetId, e.g., `"0004000005f77024"`
`hlEncoding`	Encoded outcome-side ID, e.g., `100102180`
`label`	Display label, e.g., `"Below 4.3% Yes"`, or `null`
`questionId`	Question ID, e.g., `820`, or `null` when metadata is unavailable
`outcomeId`	Outcome ID, e.g., `10218`, or `null` when metadata is unavailable
`sideIndex`	Outcome side index, e.g., `0`, or `null`
`total`	Total outcome shares, e.g., `"12"`
`hold`	Shares reserved by active orders, e.g., `"3"`
`entryNtl`	Estimated total entry value, or `null` when unavailable

Zero-balance rows without a hold are omitted. An empty array is a valid response.

Mergeable Balance

For one outcomeId, match its Yes and No rows and compute each available balance as total - hold. The maximum complete-set merge is the smaller of those two values. You can compute that amount client-side or send amount: null to userOutcome.mergeOutcome. An accepted merge increases hold on both rows while venue execution is pending. Execution removes the held shares and credits USDC; failure releases the holds.

Start Here

Info

Exchange

WebSocket

Endpoints

Response

Fields

Mergeable Balance

​Endpoints

​Response

​Fields

​Mergeable Balance

Endpoints

Response

Fields

Mergeable Balance