Skip to main content
POST
/
info
settledOutcome | Hyperliquid Info API
curl --request POST \
  --url https://hypercore.goldrushdata.com/info \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "<string>",
  "outcome": 123
}
'
{
  "spec": {
    "outcome": 123,
    "name": "<string>",
    "description": "<string>",
    "sideSpecs": [
      {
        "name": "<string>"
      }
    ],
    "quoteToken": "<string>"
  },
  "settleFraction": "<string>",
  "details": "<string>",
  "question": {
    "question": {
      "settled": 123,
      "name": "<string>",
      "description": "<string>"
    }
  }
}

Credit Cost

1 per call

Processing

Realtime
The Hyperliquid info endpoint with type: "settledOutcome" is used to retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.
  • Wire-equal to POST api.hyperliquid.xyz/info with {"type": "settledOutcome", "outcome": <int>}.
Returns the on-chain settlement data for a single settled HIP-4 outcome: the integer outcome ID, the resolved side, the resolution price, and the settlement timestamp. Use this once an outcome has resolved to confirm which side paid out and reconcile against your own books.

​
Endpoint

POST https://hypercore.goldrushdata.com/info
Authorization: Bearer <GOLDRUSH_API_KEY>
Content-Type: application/json

​
Request

​
type
string
required
Always "settledOutcome".
​
outcome
int
required
Integer outcome ID for the settled HIP-4 market. Outcome IDs are stable across the market’s lifecycle - the same ID returned by outcomeMeta while live is queried here once the outcome has resolved.

​
Example

curl -X POST https://hypercore.goldrushdata.com/info \
  -H "Authorization: Bearer $GOLDRUSH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "settledOutcome",
    "outcome": 1
  }'

​
Response

{
  "spec": {
    "outcome": 1,
    "name": "Recurring",
    "description": "class:priceBinary|underlying:BTC|expiry:20260504-0600|targetPrice:78213|period:1d",
    "sideSpecs": [
      { "name": "Yes" },
      { "name": "No" }
    ],
    "quoteToken": "USDH"
  },
  "settleFraction": "1.0",
  "details": "price:79980"
}
For question-class outcomes (free-form markets resolved by an oracle question), the response also includes a question object: 
{
  "spec": {
    "outcome": 100,
    "name": "Fallback",
    "description": "",
    "sideSpecs": [{ "name": "Yes" }, { "name": "No" }],
    "quoteToken": "USDC"
  },
  "settleFraction": "0.0",
  "details": "",
  "question": {
    "question": {
      "settled": 19,
      "name": "May CPI year-over-year",
      "description": "The question resolves by assigning Yes to exactly one of …"
    }
  }
}

​
Field descriptions

settleFraction is returned as a decimal string with full upstream precision. Do not parse it as a float - keep it as a string or use a fixed-precision decimal type.
​
spec
object
Original market specification for the outcome - the same shape outcomeMeta returns while the market is live.
​
settleFraction
string
The fraction the Yes side (index 0) paid out at resolution, as a decimal string. "1.0" means Yes won outright, "0.0" means No won, fractional values indicate a partial settlement.
​
details
string
Free-form resolution detail. For priceBinary markets, contains the resolved underlying value (e.g. "price:79980"). Empty string when settlement detail is carried in the question object instead.
​
question
object
Optional. Present only for question-class outcomes. Wraps the structured oracle question that produced the resolution.

outcomeMeta

enumerate all active HIP-4 binary outcome markets on HyperCore.
Last reviewed: 2026-06-19