Best fit for TikTape
Teams that want a single authenticated REST endpoint for full historical OHLCV on Hyperliquid, without stitching together raw exchange artifacts.
This page compares three ways to pull Hyperliquid candles. It stays narrow on purpose: route shape, authentication, and how each option presents historical OHLCV access.
TikTape is compared here strictly as a Hyperliquid OHLCV and candle API. This page does not claim TikTape supports funding rates, trades, order books, liquidations, or generalized historical market data.
Teams that want a single authenticated REST endpoint for full historical OHLCV on Hyperliquid, without stitching together raw exchange artifacts.
Teams evaluating a broader historical data platform where candles are one route family inside a larger Hyperliquid market-data product.
Builders who only need the official exchange endpoint and can work inside the documented rolling candle window.
| Provider | Candles route | Auth | Historical posture | Notes for OHLCV buyers |
|---|---|---|---|---|
| TikTapeHyperliquid-focused OHLCV product. | GET /api/v1/ohlcv |
X-API-Key |
Designed around full historical OHLCV instead of the official rolling exchange window. | Simple route shape for repeated backtests and candle pulls. Public copy should stay scoped to OHLCV only. |
| 0xArchiveHistorical data API with a dedicated Hyperliquid candles route. | GET /v1/hyperliquid/candles/:symbol |
X-API-Key |
Historical candle endpoint inside a broader Hyperliquid historical market-data API. | 0xArchive documents the candle route as OHLCV aggregated from trades, next to other Hyperliquid route families. |
| Official Hyperliquid APIExchange-native info endpoint. | POST /info with type=candleSnapshot |
No API key in the documented candle request. | Only the most recent 5,000 candles are available through the documented candle snapshot flow. | Best when you want the official surface and your candle history fits inside the exchange window. |
For TikTape, the cleanest next step is to review the public contract, call the endpoint with your own API key, inspect a sample history page, and then move into the how-to guide or coin-specific recipe. That gives you the exact request shape before you move into backtest or ingestion code.