Skip to main content
Hyperliquid core is the REST family for standard perp markets such as BTC and ETH, served under /v1/hyperliquid/*. Use it for market state, history, order flow, and depth when the symbol is a plain perp, not a Spot pair (HYPE-USDC), a HIP-3 builder prefix (km:US500), a HIP-4 outcome side (#0), or a Lighter instrument. The wrong namespace can return a valid-looking request shape while pulling the wrong market family.

Order books

Current and historical depth for core perp markets.

Trades

Executions with timestamp, side, price, size, and source-specific fields.

Funding and OI

Funding rates, premium, marks, mids, and open interest.

Order lifecycle

Order history, flow, and TP/SL surfaces, available on every tier.

First Request

curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

Available Route Groups

Core routes cover current and historical market-state work: order books, trades, candles, funding, open interest, liquidations, order history, and L4/order-level surfaces, all available on every tier. Trade routes return fill-level rows with per-trade wallet attribution; the Hyperliquid Fills Data API page maps fills questions to the right routes. Confirm the path with /v1/hyperliquid/orderbook/BTC, then add history, funding, OI, or L4 after auth, response shape, and data-quality checks are working.

Core Request Checklist

Use this checklist when a client, generated test, or coding agent is about to call core Hyperliquid routes.
FieldCore-family value
Namespace/v1/hyperliquid/*
Symbol stylePlain perp symbols such as BTC or ETH
Excluded stylesSpot pairs, HIP-3 builder prefixes, HIP-4 outcome IDs, and Lighter symbols
First probeCurrent order book, trades page, candle page, or freshness check for one symbol
Widening ruleAdd history, pagination, or L4 only after auth, response shape, and request-ID logging work

Store For Reproducible Pulls

For backtests, store the route, query parameters, time window, cursor, and request_id per page. Pair the market-data pull with /v1/data-quality/* so downstream users know whether the window was complete and fresh enough to trust. Raw execution, wallet signing, and venue account actions belong in native Hyperliquid surfaces. 0xArchive documents market data and historical retrieval. Open Order books for depth selection, Trades for event history, Candles for time-series context, or Best Hyperliquid Data API for buying-context boundaries.
Last modified on July 4, 2026