Docs

Hyperliquid OHLCV REST API

Query Hyperliquid OHLCV candles over HTTP with one candle per request using your Dwellir API key.

Use the REST endpoint when you want a simple HTTP lookup for one specific candle.

Endpoint

Text
GET https://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEY/v1/candles

Historical coverage start

REST 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.

Query Parameters

ParameterRequiredDescription
marketyesHyperliquid market symbol, for example BTC
intervalyesCandle interval, one of 1s, 1m, 5m
timeyesCandle bucket-open timestamp in ISO-8601 UTC. This identifies the exact candle you want, for example 2026-03-30T23:00:00Z for the 23:00 1m candle. To retrieve multiple candles, iterate over the bucket-open timestamps you need and request each one separately.

Example

Bash
curl "https://api-hyperliquid-ohlcv.n.dwellir.com/YOUR_API_KEY/v1/candles?market=BTC&interval=1m&time=2026-03-30T23:00:00Z"

Response:

JSON
{
  "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 request returns one candle
  • candle timestamps are UTC bucket-open times
  • missing intervals are omitted at the data layer because candles are sparse

How the time parameter works

time is the open time of the candle you want back, not an arbitrary point inside a range. If you want a series of candles, step through the bucket-open timestamps for the interval you are querying and request each bucket individually.

Current contract is intentionally narrow

The REST API does not provide bulk historical range reads today. Historical retrieval is done as one candle per response.

Fetching Multiple Candles

Use the time parameter as the iterator. For 1m, advance by one minute per request. For 5m, advance by five minutes. For 1s, advance by one second.

When to Use REST

  • simple backend lookups
  • dashboards that fetch known candles by timestamp
  • scripts that already work with plain HTTP