Vault profile

One vault: registry fields, current TVL, APR, leverage, depositor concentration and all five windows.

GET https://data.vike.io/v1/hyperliquid/vaults/{vault}

One vault: registry fields, current TVL, APR, leverage, depositor concentration and all five windows. A parent vault's figures include its sub-vaults (child_vaults).

cURL

# HLP: TVL, APR, leverage, depositor concentration and all five windows in one call
curl -s "https://data.vike.io/v1/hyperliquid/vaults/0xdfc24b077bc1425ad1dea75bcb6f8158e10df303" \
  -H "X-API-KEY: $VIKE_API_KEY"

# compare the windows side by side, with how much of each is really covered
curl -s "https://data.vike.io/v1/hyperliquid/vaults/0xdfc24b077bc1425ad1dea75bcb6f8158e10df303" \
  -H "X-API-KEY: $VIKE_API_KEY" \
  | jq '.windows | map_values({start, partial, pnl_usd, return_pct, coverage})'

# the vault's open positions: a vault is a wallet, so the wallet routes take its address
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0xdfc24b077bc1425ad1dea75bcb6f8158e10df303" \
  -H "X-API-KEY: $VIKE_API_KEY"

vaultpathrequired

Vault address

No response has been captured for this route yet. The card shows the fields the code returns, with placeholders in place of values.

Response shape

{
  "vault": "<address>",
  "name": "<vault name>",
  "description": "<the leader's description>",
  "leader": "<address>",
  "parent": "<address, or null>",
  "relationship": "<normal, parent or child>",
  "created_at": "<ISO-8601 UTC>",
  "leader_commission": "<fraction, 0.1 is 10%>",
  "lockup_seconds": "<integer>",
  "is_closed": "<boolean>",
  "allow_deposits": "<boolean>",
  "always_close_on_withdraw": "<boolean>",
  "child_vaults": ["<address>"],
  "as_of": "<ISO-8601 UTC, the newest hourly reading>",
  "tvl_usd": "<USD, or null>",
  "apr_pct": "<percentage points, or null>",
  "leverage": "<open notional over equity, or null>",
  "leader_share_pct": "<percentage points>",
  "top5_share_pct": "<percentage points>",
  "active_depositors": "<integer>",
  "windows": {
    "7d": {
      "start": "<YYYY-MM-DD>",
      "end": "<YYYY-MM-DD, the newest recorded day>",
      "partial": "<boolean>",
      "pnl_usd": "<USD>",
      "return_pct": "<percentage points, or null>",
      "net_flow_usd": "<USD>",
      "volume_usd": "<USD>",
      "fills": "<integer>",
      "coverage": "<fraction from 0 to 1>"
    },
    "30d": "<the same keys>",
    "90d": "<the same keys>",
    "365d": "<the same keys>",
    "all": "<the same keys>"
  }
}

History starts on 2026-10-27: windows are partial and returns are null until it fills

Each window ends on the newest recorded day and starts no earlier than the vault's own first recorded day, which is 2026-10-27 at the earliest. A window longer than that says partial: true, and its figures cover only the recorded days; all means all recorded history, so it is never marked partial but is just as short. pnl_usd and return_pct stay null until a day has been recorded after the window's first day, and apr_pct is null for a vault recorded for less than 30 days. With no recorded history at all, windows, tvl_usd and apr_pct are null.

The windows mean what they mean on /vaults: pnl_usd is the equity change minus net deposits, return_pct the chained share-price return, coverage the fraction of the window's days recorded.
leverage is open notional over equity.
leader_share_pct and top5_share_pct are the leader's and the five largest depositors' shares of the vault, in percentage points.
active_depositors counts depositors holding at least $1. The list is /vaults/{vault}/depositors.
An unknown address is a 404, and a malformed one a 400.

The vault's trading is on the wallet routes

A vault trades from its own address. Its fills, trades and positions are served by /wallets/{address}/fills, /wallets/{address}/trades and /wallets/{address} with the vault's address.