Skip to main content
POST
/
4f8d8f4040bdacd1577bff8058438274
/
info
info (settledOutcome)
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "settledOutcome",
  "outcome": 0
}
'
{
  "spec": {
    "outcome": 123,
    "name": "<string>",
    "description": "<string>",
    "sideSpecs": [
      {
        "name": "<string>",
        "token": 123
      }
    ],
    "quoteToken": "<string>"
  },
  "settleFraction": "<string>",
  "details": "<string>"
}
This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see Hyperliquid methods for the full availability breakdown.
The info endpoint with type: "settledOutcome" retrieves the specification and settlement details for an outcome market, identified by its outcome index. Outcome markets are binary (Yes/No) prediction markets on Hyperliquid. Use this method to read an outcome’s definition and how it settled.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Request body

  • type (string, required) — The request type. Must be "settledOutcome".
  • outcome (integer, required) — The outcome identifier.

​
Response

Returns a settled outcome object, or null if the outcome is not settled.
  • spec (object) — The outcome specification:
    • outcome (integer) — The outcome identifier.
    • name (string) — The name of the outcome.
    • description (string) — The description of the outcome.
    • sideSpecs (array) — The side specifications, each with a name and an optional token.
    • quoteToken (string) — The quote token for this outcome.
  • settleFraction (string) — The settlement fraction.
  • details (string) — The settlement details.

​
Example request

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"type": "settledOutcome", "outcome": 0}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/info
Use your own endpoint in your code. The code examples use a placeholder Chainstack endpoint (YOUR_CHAINSTACK_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the Chainstack console. The curl above uses a shared public endpoint for quick checks only; do not use it in production.

​
Example response

{
  "spec": {
    "outcome": 0,
    "name": "Recurring",
    "description": "class:priceBinary|underlying:BTC|expiry:20260503-0600|targetPrice:78213|period:1d",
    "sideSpecs": [
      { "name": "Yes" },
      { "name": "No" }
    ],
    "quoteToken": "USDH"
  },
  "settleFraction": "0.0",
  "details": "price:78212.4"
}

​
Use cases

The info endpoint with type: "settledOutcome" is useful for:
  • Reading the definition of an outcome market (underlying, target price, expiry)
  • Checking how an outcome settled and its settlement fraction
  • Building prediction-market dashboards and settlement reports

Body

application/json
​
type
enum<string>
default:settledOutcome
required

Request type

Available options:
settledOutcome
​
outcome
integer
default:0
required

Outcome identifier.

Response

200 - application/json
object | null

Information about a settled outcome, or null if the outcome is not settled

​
spec
object

Outcome specification.

​
settleFraction
string

Settlement fraction.

​
details
string

Settlement details.

Last modified on June 24, 2026