Hyperliquid OHLCV WebSocket API
Subscribe to completed Hyperliquid OHLCV candles over WebSocket using the public Dwellir OHLCV endpoint.
Use the WebSocket endpoint when you want completed live candles pushed to your client after subscribing.
Endpoint
wss://api-hyperliquid-ohlcv.n.dwellir.comFor path-auth clients, including browser-native WebSocket usage, connect to:
wss://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEYSubscribe Message
{
"type": "subscribe",
"market": "BTC",
"interval": "1m"
}Example Flow
Client sends:
{ "type": "subscribe", "market": "BTC", "interval": "1m" }Server acknowledges:
{ "type": "subscribed", "market": "BTC", "interval": "1m" }Then sends completed candle events:
{
"type": "candle",
"market": "BTC",
"interval": "1m",
"candle": {
"market": "BTC",
"interval": "1m",
"bucket_start": "2026-04-08T11:51:00Z",
"open": "71564",
"high": "71575",
"low": "71563",
"close": "71575",
"volume": "0.15805",
"trades_count": 42,
"vwap": "71572.210503005377659097"
}
}Behavior
- subscription is keyed by
marketandinterval - the transport streams completed live candles
- candle payloads use the same schema as REST and JSON-RPC
Authentication
- non-browser clients can authenticate with the standard Dwellir API key header against
wss://api-hyperliquid-ohlcv.n.dwellir.com - browser-native WebSocket clients should use the path-auth form
wss://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEY - both forms connect to the same completed-candle stream
WebSocket is for live completed candles
The WebSocket surface is not a historical replay API. It is intended for live completed-candle delivery after a successful subscription.
When to Use WebSocket
- live dashboards
- alerting or monitoring pipelines
- trading systems that want completed candles pushed instead of polled
JSON-RPC API
Query Hyperliquid OHLCV candles over JSON-RPC with the public Dwellir OHLCV endpoint.
Info Endpoint Overview
Access comprehensive Hyperliquid exchange data through Dwellir's HyperCore Info Endpoint. Query market metadata, account states, vault information, and more with higher rate limits than public endpoints.