> ## Documentation Index
> Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# settledOutcome | Hyperliquid Info API

> Hyperliquid settledOutcome: retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.

<CardGroup cols={2}>
  <Card title="Credit Cost"> 1 per call</Card>
  <Card title="Processing"> Realtime</Card>
</CardGroup>

The Hyperliquid info endpoint with `type: "settledOutcome"` is used to retrieve resolution details for a settled HIP-4 binary outcome market on HyperCore.

<Tip>
  Estimate your monthly cost for this API using the [Pricing Calculator](/pricing-calculator?endpoint=%2Fapi-reference%2Fhyperliquid-info%2Fsettled-outcome).
</Tip>

<Info>
  * Wire-equal to `POST api.hyperliquid.xyz/info` with `{"type": "settledOutcome", "outcome": <int>}`.
</Info>

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

<ParamField body="type" type="string" required>
  Always `"settledOutcome"`.
</ParamField>

<ParamField body="outcome" type="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.
</ParamField>

### Example

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST https://hypercore.goldrushdata.com/info \
    -H "Authorization: Bearer $GOLDRUSH_API_KEY" \
    -H "Content-Type: application/json" \
    -d '{
      "type": "settledOutcome",
      "outcome": 1
    }'
  ```

  ```typescript TypeScript theme={null}
  const response = await fetch("https://hypercore.goldrushdata.com/info", {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      type: "settledOutcome",
      outcome: 1,
    }),
  });

  const settlement = await response.json();
  ```

  ```python Python theme={null}
  import os, requests

  response = requests.post(
      "https://hypercore.goldrushdata.com/info",
      headers={"Authorization": f"Bearer {os.environ['GOLDRUSH_API_KEY']}"},
      json={
          "type": "settledOutcome",
          "outcome": 1,
      },
  )

  settlement = response.json()
  ```
</CodeGroup>

## Response

```json theme={null}
{
  "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:

```json theme={null}
{
  "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

<Note>
  `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.
</Note>

<ResponseField name="spec" type="object">
  Original market specification for the outcome - the same shape `outcomeMeta` returns while the market is live.

  <Expandable title="properties">
    <ResponseField name="outcome" type="int">Integer outcome ID. Echoes the request parameter.</ResponseField>
    <ResponseField name="name" type="string">Human-readable label for the market - for example, `"Recurring"` for repeating price-binary markets.</ResponseField>

    <ResponseField name="description" type="string">
      For `priceBinary` markets, a pipe-delimited spec (`class:…|underlying:…|expiry:…|targetPrice:…|period:…`). Empty string for `question`-class outcomes.
    </ResponseField>

    <ResponseField name="sideSpecs" type="array<object>">
      Tradeable sides of the outcome. For binary outcomes, index 0 is `Yes` and index 1 is `No`.

      <Expandable title="properties">
        <ResponseField name="name" type="string">Side label - typically `"Yes"` or `"No"`.</ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="quoteToken" type="string">Symbol of the token the market quotes against - typically `"USDC"` or `"USDH"`.</ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="settleFraction" type="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.
</ResponseField>

<ResponseField name="details" type="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.
</ResponseField>

<ResponseField name="question" type="object">
  Optional. Present only for question-class outcomes. Wraps the structured oracle question that produced the resolution.

  <Expandable title="properties">
    <ResponseField name="question" type="object">
      <Expandable title="properties">
        <ResponseField name="settled" type="int">Encoded settlement side (`19` is observed for `No`-resolved questions in current data).</ResponseField>
        <ResponseField name="name" type="string">Short label for the question.</ResponseField>
        <ResponseField name="description" type="string">Full question description, including resolution criteria and fallback rules.</ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

## Related endpoints

<CardGroup cols={2}>
  <Card title="outcomeMeta" href="/api-reference/hyperliquid-info/outcome-meta">enumerate all active HIP-4 binary outcome markets on HyperCore.</Card>
</CardGroup>

*Last reviewed: 2026-06-19*