Skip to main content
GET /v1/capabilities is the machine-readable answer to “can I get this data type on this venue, and how?”. It returns one row per venue and data type. 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

“Not listed” means the response has no value for that field: no single venue-wide start, or no fixed page limit. 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.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.

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.
  • Price history: HIP-3 prices read the oracle stream, which reaches back further than open interest.
  • Account positions: Page limits: 5,000 rows on wallet/account histories, 2,000 on market listings.

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.

API conventions

Envelope, errors, versioning, time, pagination, and coverage signals.

Venue coverage

Namespaces, symbol styles, and history by data type.

WebSocket channels

Channel names, live and replay availability, and message flow.

Errors

Every error_code and what to do next.
Last modified on October 6, 2026