Hyperliquid L4

The WebSocket DS API provides six HYPERLIQUIDL4-only data types:

[!NOTE]

These data types are available only from the Hyperliquid L4 WS DS data source. They are not available on other exchange WS DS streams.

Endpoint

Use the dedicated hyperliquidl4 WS DS data source:

wss://hyperliquidl4.ws-ds.md.coinapi.io/

You can authenticate with any WS DS authentication method documented in the Authentication section. For example, using the API key in the URL path:

wscat --connect wss://hyperliquidl4.ws-ds.md.coinapi.io/APIKEY-YOUR_API_KEY

Subscribe

After connecting, send a hello message with one or more Hyperliquid data types. For symbol-level feeds (book_l4, trade_l4, hl_oracle_prices, hl_twap_statuses), define a symbol filter for the pairs you want to receive.

{
  "type": "hello",
  "heartbeat": false,
  "subscribe_data_type": ["book_l4", "trade_l4"],
  "subscribe_filter_symbol_id": [
    "HYPERLIQUIDL4_PERP_BTC_USDC",
    "HYPERLIQUIDL4_SPOT_AZTEC_USDC"
  ]
}

To subscribe to all Hyperliquid enrichment and raw event feeds:

{
  "type": "hello",
  "heartbeat": false,
  "subscribe_data_type": [
    "hl_oracle_prices",
    "hl_twap_statuses",
    "hl_misc_events",
    "hl_system_events"
  ],
  "subscribe_filter_symbol_id": [
    "HYPERLIQUIDL4_PERP_BTC_USDC",
    "HYPERLIQUIDL4_PERP_ETH_USDC"
  ]
}

To subscribe only to L4 transactions:

{
  "type": "hello",
  "subscribe_data_type": ["trade_l4"]
}

Use the REST symbol metadata endpoints to discover active symbols, then subscribe to the HYPERLIQUIDL4_* symbols you need. The L4 real-time data itself is delivered through this WS DS stream.

Order Book L4

book_l4 provides order-by-order Hyperliquid book data. Snapshot messages contain the visible orders in the book. Update messages contain only the changed orders since the previous message.

Each ask or bid entry includes:

On incremental updates, update_type is set when an order is accepted into the book, rejected when it is rejected, or delete when it is removed. hl4_status indicates the outcome using one of 18 status codes (for example, open, rejected_alo, rejected_margin, or reduce_only_canceled).

See the full book_l4 schema in Messages.

Trades L4

trade_l4 provides executed Hyperliquid transactions with user attribution for both sides of the match.

Each transaction includes:

See the full trade_l4 schema in Messages.

Oracle Prices

hl_oracle_prices provides per-coin oracle and mark price updates derived from Hyperliquid HIP-3 oracle streams. Each message can include validated prices, daily reference values, and raw input prices used in the update.

Common use cases:

• Real-time mark/oracle monitoring for liquidation and risk models.
• Alerting on mark-oracle divergence.
• Tracking data quality and source behavior through update_class and input fields.

See the full hl_oracle_prices schema in Messages.

TWAP Statuses

hl_twap_statuses provides per-TWAP lifecycle updates and execution progress metrics. Messages include execution sizes, notional progress, and additional execution attributes such as randomization and order timestamp.

Common use cases:

• Monitoring TWAP execution progress in real time.
• Detecting completion, termination, and error states.
• Building TWAP execution dashboards per coin and user.

See the full hl_twap_statuses schema in Messages.

Misc Raw Events

hl_misc_events provides raw node misc events as normalized envelopes with:

• exchange identifier,
• source block number,
• event type,
• JSON payload.

This feed is useful when you need low-level exchange-native event payloads in addition to normalized market data.

See the full hl_misc_events schema in Messages.

System Raw Events

hl_system_events provides raw node system action events as normalized envelopes with:

• exchange identifier,
• source block number,
• action type,
• JSON payload.

This feed is useful for monitoring account/system actions and preserving raw action payloads for audit pipelines.

See the full hl_system_events schema in Messages.