Hyperliquid OHLCV JSON-RPC API
Query Hyperliquid OHLCV candles over JSON-RPC with the public Dwellir OHLCV endpoint.
Use the JSON-RPC transport when you want OHLCV data in a standard RPC shape.
Endpoint
POST https://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEY/jsonrpcHistorical coverage start
JSON-RPC candle lookups are intended to cover history back to 2025-07-27T08:00:00Z, which is the first available node_fills_by_block
archive hour.
Method
ohlcv_getCandleParameters
| Field | Required | Description |
|---|---|---|
market | yes | Hyperliquid market symbol, for example BTC |
interval | yes | Candle interval, one of 1s, 1m, 5m |
time | yes | Candle open timestamp in ISO-8601 UTC |
Example
curl "https://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEY/jsonrpc" \
-H "content-type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "ohlcv_getCandle",
"params": {
"market": "BTC",
"interval": "1m",
"time": "2026-03-30T23:00:00Z"
}
}'Response:
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"market": "BTC",
"interval": "1m",
"bucket_start": "2026-03-30T23:00:00Z",
"open": "66745",
"high": "66746",
"low": "66687",
"close": "66687",
"volume": "4.78586",
"trades_count": 256,
"vwap": "66733.634306059987321311"
}
}Behavior
- one JSON-RPC request returns one candle
- candle responses use the same sparse dataset as the REST transport
- JSON-RPC is a transport convenience, not a separate data product
No historical batch method yet
The shipped JSON-RPC surface documents the current product only: single-candle lookup with ohlcv_getCandle.
When to Use JSON-RPC
- clients that already expect RPC envelopes
- systems sharing transport patterns with existing blockchain JSON-RPC code
- internal tooling that prefers method-based request logging