Skip to main content
Check whether a venue serves a data type, and how, before you call it. GET /v1/capabilities returns one row per venue and data type, and the tables on this page are rendered from that response, so they match what the API serves. The route is public: it needs no API key and costs no credits. Responses are cached for up to five minutes. The Python, TypeScript, and Rust SDKs return the same rows from client.capabilities().

Row fields

Use it before you call

  • Check live and replay before opening a WebSocket subscription or replay. A channel that does not offer a mode answers with error_code unsupported_for_venue.
  • Start history requests at or after available_from. A range that straddles it is served from that point; a range that ends before a policy floor returns range_before_coverage. Per-symbol starts can be later than the venue-wide start, so check /v1/symbols for a specific market.
  • Size pages with page_limit and aggregate with a value from intervals.
  • Build channel and venue allow-lists in your own code from this response instead of hard-coding them, so a newly added replay channel or venue needs no code change.
A data type that a venue does not offer has no row. Requesting it over REST returns 404 with error_code unsupported_for_venue and a list of the venues that do offer it; see Errors.

Matrix

Each cell lists the REST routes, the WebSocket channel and its modes, the first served time, the plans for a data type that not every plan includes, the cadence, the page limit, and any intervals. “No venue-wide start date” and “No fixed page limit” mean the response has no value for that field. The notes under each table repeat the row’s notes text. L4 and full-depth order book replay is bulk (speed is ignored) and single-channel, anchored at the nearest L4 checkpoint; see WebSocket replay.

Hyperliquid

Venue key hyperliquid. REST routes are relative to /v1/hyperliquid/.
  • Full-depth L2: Derived from L4. WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints.
  • Full-depth L2 diffs: Derived from L4.
  • L4 order book: A live or replayed L4 diff stream opens with a full L4 snapshot.
  • L4 diffs: WebSocket replay is bulk (speed is ignored) and single-channel only; it starts at the nearest L4 checkpoint and opens with its snapshot.
  • Order history (L4 order events): WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints.
  • Candles: Older rows exist but are not served; available_from is a policy floor.
  • Liquidations: Older rows exist but are not served; available_from is a policy floor.
  • Liquidations by user: Older rows exist but are not served; available_from is a policy floor.
  • USDC flows: USDC entering and leaving HyperCore: Arbitrum bridge deposits and withdrawals, and transfers to and from HyperEVM (which also carries CCTP), with the HyperCore account. Events page through the whole history by cursor and join on id; /volume totals every flow per interval.
  • Trade intent: Why volume traded, per interval: USD of new longs and shorts, profit taken, stopped out and flips (both sides of every trade; market makers apart, in mm_usd), and the aggregate position and flow of the market’s trailing-72h winners and losers. Hourly intervals from available_from, minute intervals from 2026-07-14 00:00 UTC, second intervals for the last 3 days. A market idle for more than 7 days has no buckets there: a gap, not zero.
  • Breadth above the moving average: Share of perps above their n-day moving average (n required: 5, 20, 50 or 200), with the quartiles of how far above or below. Method ma-breadth/1: a delisted perp stays a candidate, counted in excluded_stale_price from 24 hours after its last trade, and a perp younger than n days in excluded_short_history, so coverage_ratio is not a data-quality ratio and is not comparable with above-VWAP’s; the average is of the daily closes over the n UTC days before the reading’s day. available_from is n = 5; n = 20 from 2025-04-11, 50 from 2025-05-11, 200 from 2025-10-08. A bucket carries its last reading; percentages are never averaged.
  • Positioning: Every listed perp’s open interest change, taker buy and sell volume and liquidations over a trailing window (window required: 1h, 4h or 24h), with each market’s typical move over windows of that length: the median absolute move over the last 2,000 five-minute steps, null under 288 counted windows, and its positioning state (long-buildup, short-covering, short-buildup, long-unwinding, mixed or quiet) from its open interest and net taker flow against its own typical moves. The window ends at the newest 5-minute close; open interest and marks are null when a bucket has no reading, never 0. Current window only: history is not served. One record per perp, unpaged.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.
  • Wallet funding payments: Funding a wallet paid or received, one row per position per hourly settlement; funding_amount is positive when received and negative when paid. At most 31 days per request, ordered by time.
  • Pending transactions (mempool): Signed transactions as our Hyperliquid node receives them, before they are in a block, for every Hyperliquid product. Live only, on wss://stream.0xarchive.io/ws, with the Pro, Scale and Enterprise plans.

Hyperliquid Spot

Venue key spot. REST routes are relative to /v1/hyperliquid/spot/.
  • L4 order book: A live or replayed L4 diff stream opens with a full L4 snapshot. PURR-USDC has L4 checkpoints from 2026-03-11 01:03 UTC; other pairs from 2026-05-05 or later (HYPE-USDC from 2026-05-13 15:33 UTC).
  • L4 diffs: WebSocket replay is bulk (speed is ignored) and single-channel only; it starts at the nearest L4 checkpoint and opens with its snapshot. PURR-USDC has L4 checkpoints from 2026-03-11 01:03 UTC; other pairs from 2026-05-05 or later (HYPE-USDC from 2026-05-13 15:33 UTC).
  • Order history (L4 order events): WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints (PURR-USDC from 2026-03-11 01:03 UTC; other pairs from 2026-05-05 or later). REST order history reaches back further for every pair.
  • Instruments: Spot instruments are listed as pairs.
  • TWAP: REST only: the spot_twap WebSocket channel accepts a subscription but does not stream yet.

HIP-3

Venue key hip3. REST routes are relative to /v1/hyperliquid/hip3/.
  • Full-depth L2: Derived from L4. WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints.
  • Full-depth L2 diffs: Derived from L4.
  • L4 order book: A live or replayed L4 diff stream opens with a full L4 snapshot.
  • L4 diffs: WebSocket replay is bulk (speed is ignored) and single-channel only; it starts at the nearest L4 checkpoint and opens with its snapshot.
  • Order history (L4 order events): WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints.
  • Trade intent: Why volume traded, per interval: USD of new longs and shorts, profit taken, stopped out and flips (both sides of every trade; market makers apart, in mm_usd), and the aggregate position and flow of the market’s trailing-72h winners and losers. Hourly intervals from available_from, minute intervals from 2026-07-14 00:00 UTC, second intervals for the last 3 days. A market idle for more than 7 days has no buckets there: a gap, not zero.
  • Price history: HIP-3 prices read the oracle stream, which reaches back further than open interest.
  • Breadth above the moving average: Share of HIP-3 perps above their n-day moving average (n required: 5, 20, 50 or 200), with the quartiles of how far above or below. Method ma-breadth/1: a delisted perp stays a candidate, counted in excluded_stale_price from 24 hours after its last trade, and a perp younger than n days in excluded_short_history, so coverage_ratio is not a data-quality ratio and is not comparable with above-VWAP’s; the average is of the daily closes over the n UTC days before the reading’s day. available_from is n = 5; n = 20 from 2026-01-11, 50 from 2026-02-10, 200 from 2026-07-10. A bucket carries its last reading; percentages are never averaged.
  • Positioning: Every listed perp’s open interest change, taker buy and sell volume and liquidations over a trailing window (window required: 1h, 4h or 24h), with each market’s typical move over windows of that length: the median absolute move over the last 2,000 five-minute steps, null under 288 counted windows, and its positioning state (long-buildup, short-covering, short-buildup, long-unwinding, mixed or quiet) from its open interest and net taker flow against its own typical moves. The window ends at the newest 5-minute close; open interest and marks are null when a bucket has no reading, never 0. Current window only: history is not served. One record per perp, unpaged.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.
  • Wallet funding payments: Funding a wallet paid or received on HIP-3 dex positions, one row per position per hourly settlement; funding_amount is positive when received and negative when paid. At most 31 days per request, ordered by time.

HIP-4

Venue key hip4. REST routes are relative to /v1/hyperliquid/hip4/.
  • L2 order book: WebSocket replay only: the live channel accepts a subscription but does not stream yet.
  • L4 order book: A live or replayed L4 diff stream opens with a full L4 snapshot.
  • L4 diffs: WebSocket replay is bulk (speed is ignored) and single-channel only; it starts at the nearest L4 checkpoint and opens with its snapshot.
  • Order history (L4 order events): WebSocket replay is bulk (speed is ignored) and single-channel only, anchored at L4 checkpoints.
  • Candles: Prices are implied probabilities (0 to 1); quote volume is in USDH.
  • Open interest: WebSocket replay only: the live channel accepts a subscription but does not stream yet.
  • TWAP: HIP-4 TWAP orders before capture began were not recorded; history starts at the first captured TWAP.

Lighter

Venue key lighter. REST routes are relative to /v1/lighter/.
  • L2 order book: History granularity: checkpoint (default), 30s, 10s, 1s or tick.
  • Trades: Trades up to meta.finalized_through are canonical; /recent and live trades are preliminary. Served trade history begins at this row; exact starts vary by market.
  • Liquidations: Older rows exist but are not served; available_from is a policy floor.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.

Lighter on Robinhood Chain

Venue key rh-lighter. REST routes are relative to /v1/rh-lighter/.
  • L2 order book: History granularity: checkpoint (default), 30s, 10s, 1s or tick.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.

Next step

Last modified on November 4, 2026