How to query HIP-3 markets from the Hyperliquid API

Direct answer

Send POST requests to https://api.hyperliquid.xyz/info. No API key is needed. Call perpDexs to list every builder DEX, then call metaAndAssetCtxs with "dex": "<name>" for that DEX's markets, prices, funding, and open interest. HIP-3 markets use qualified names such as xyz:SKHY, and anything keyed by coin (funding history, candles, order books) takes that qualified name. Omitting dex, or passing an empty string, returns the core DEX.

HIP-3 info requests

From the official perpetuals info-endpoint reference, reviewed September 26, 2026.

predictedFundings only covers the core DEX.

Examples

List every perp DEX, including deployers and caps:

curl -s https://api.hyperliquid.xyz/info \
  -H 'content-type: application/json' \
  -d '{"type":"perpDexs"}'

Live prices, funding, and open interest for every market on one DEX:

curl -s https://api.hyperliquid.xyz/info \
  -H 'content-type: application/json' \
  -d '{"type":"metaAndAssetCtxs","dex":"xyz"}'

Hourly funding history for one HIP-3 market:

curl -s https://api.hyperliquid.xyz/info \
  -H 'content-type: application/json' \
  -d '{"type":"fundingHistory","coin":"xyz:SKHY","startTime":1758240000000}'

Each call returned at most 500 rows in our testing. To page, send the next request with startTime set just after the last row's time.

Loop over every DEX and print each market (JavaScript):

const info = (body) =>
  fetch("https://api.hyperliquid.xyz/info", {
    method: "POST",
    headers: { "content-type": "application/json" },
    body: JSON.stringify(body),
  }).then((response) => response.json());

const dexs = (await info({ type: "perpDexs" })).filter(Boolean);
for (const dex of dexs) {
  const [meta, contexts] = await info({ type: "metaAndAssetCtxs", dex: dex.name });
  meta.universe.forEach((asset, index) => {
    const ctx = contexts[index];
    console.log(asset.name, ctx.markPx, ctx.openInterest, ctx.funding);
  });
}

meta.universe and the contexts array share the same order, so match them by index. Skip entries marked isDelisted.

HIP-3 asset IDs for orders

Order and cancel actions take an integer asset ID, not a name. The official rule for builder-deployed perps is 100000 + perp_dex_index × 10000 + index_in_meta, where perp_dex_index is the DEX's position in the perpDexs response and index_in_meta is the asset's position in that DEX's meta universe. The docs' testnet example: DEX index 1, asset index 0 gives 110000. Core perps use their plain meta index (BTC is 0), and spot uses 10000 plus the spot index.

WebSocket subscriptions

On wss://api.hyperliquid.xyz/ws, the allMids, clearinghouseState, openOrders, and twapStates subscriptions accept a dex field. Coin-keyed feeds such as l2Book, trades, candle, and activeAssetCtx take only a coin, so pass the qualified HIP-3 name.

HIP-4 outcome markets

Outcome market metadata comes from the outcomeMeta info request. Outcome asset IDs follow 100_000_000 + (10 × outcome + side), where side is 0 or 1. Outcome 1, side 0 is asset 100000010. HypeBasis reads the same request for its live HIP-4 outcome board.

Rate limits and free datasets

The info endpoint is rate-limited by request weight per IP, so cache static calls such as perpDexs and meta instead of polling them. Check the official rate-limit page for current weights.

If you need history rather than a live read, HypeBasis publishes free CSVs built from the same official endpoints: the HIP-3 cap and configuration history and the market history dataset of price, funding, and open interest.