How to Download Hyperliquid Historical Data

Downloading Hyperliquid historical data sounds simple.

Until you realize that not all historical data is the same.

Some developers need past prices to backtest trading strategies… others want historical trades, funding rates, or order book snapshots. And some need to go deeper, reconstructing individual orders to understand how liquidity behaved at a specific moment.

Hyperliquid offers several ways to access this information, but each comes with different capabilities and limitations.

Let’s look at three ways to download Hyperliquid historical data:

1. Hyperliquid's official S3 archives and API
2. GitHub tools and community projects
3. CoinAPI historical market data

We'll explain what you can download, how each method works, and which one makes the most sense for your research.

1. Download Hyperliquid Historical Data From Official Archives

Hyperliquid maintains its own historical data archives on Amazon S3.

These archives provide access to exchange-native information, including historical trades and L2 order book snapshots.

There are two main sources:

• hyperliquid-archive — contains historical L2 order book snapshots and asset context data.
• hl-mainnet-node-data — contains historical fills, trade records, and other node-level data.

These archives are useful if you want to work directly with information published by Hyperliquid.

How to download the data

You'll need AWS CLI, AWS credentials, and access to the requester-pays S3 buckets.

For example, you can download an archived SOL L2 order book file with:

1aws s3 cp \ s3://hyperliquid-archive/market_data/20230916/9/l2Book/SOL.lz4 \ SOL.lz4 \ --request-payer requester

The file is compressed using LZ4, so you'll need to decompress it before processing the data.

For historical trade and fill records, you can explore the official node archive:

s3://hl-mainnet-node-data/node_fills_by_block

You can find the relevant archive paths in Hyperliquid's official documentation.

What about historical candles and funding rates?

Hyperliquid also provides a native API for retrieving historical candles and funding rates.

For example, its candleSnapshot endpoint allows developers to request OHLCV data for a specific asset and interval.

However, the API only exposes the most recent 5,000 candles. This can be restrictive when building longer historical datasets.

What are the limitations?

Hyperliquid's official resources are a good starting point, but there are a few things to consider:

• The historical S3 archive is updated approximately monthly, and completeness isn't guaranteed.
• AWS requester-pays charges apply when downloading archive data.
• Different datasets have different formats and structures.
• Historical L2 snapshots aren't the same as individual-order L4 data.

Best for: Developers who want to work directly with exchange-native historical data and are comfortable managing their own downloads and processing.

2. Download Hyperliquid Historical Data Using GitHub Tools

Not everyone wants to build a data collection pipeline from scratch.

That's where GitHub comes in.

Developers have created open-source libraries, scripts, and utilities that help retrieve Hyperliquid market data through its APIs or process existing historical archives.

These tools can simplify tasks such as downloading trades, collecting candles, or converting raw data into formats suitable for analysis.

How does it work?

A common approach is to find an open-source Hyperliquid data collector, install it, and configure it for the market and period you're interested in.

For example, the community project hyperliquid-data provides tooling for collecting market data, including candles, funding information, trades, fills, and L2 data.

Other repositories may focus on SDKs, API integrations, or processing historical records.

You can explore available projects through GitHub's Hyperliquid historical data search.

What are the limitations?

GitHub tools can save development time, but there's an important distinction.

A GitHub repository is usually a tool for retrieving data, not a historical data provider.

The historical coverage still depends on the source it connects to.

You should also check whether the project is actively maintained, supports the dataset you need, and handles gaps, rate limits, or changes to the source API.

For example, a script that retrieves candles from Hyperliquid's native API still faces that API's historical availability limits.

Similarly, a tool that downloads L2 snapshots doesn't automatically provide individual-order L4 history.

Best for: Developers building custom pipelines, testing strategies, or experimenting with Hyperliquid data without developing every integration themselves.

3. Download Hyperliquid Historical Data With CoinAPI

The third option is to use a dedicated market data provider.

CoinAPI provides historical Hyperliquid market data through REST APIs and downloadable Flat Files, including detailed L4 order book data.

Instead of collecting and organizing different datasets manually, developers can access structured historical records through consistent interfaces.

The available data includes:

The right interface depends on how much information you need.

For a small historical candle query, REST is usually the simplest option.

For months of trade or order book records, downloading Flat Files is generally more practical.

How to download Hyperliquid historical data from CoinAPI

CoinAPI uses an S3-compatible service for bulk historical downloads.

The endpoint is:

https://s3.flatfiles.coinapi.io

Once you've configured your CoinAPI key for S3 access, you can browse available Hyperliquid datasets and download individual compressed CSV files.

For example, the following command lists available historical L4 order book files for a selected hour:

1aws --endpoint-url https://s3.flatfiles.coinapi.io \ s3 ls s3://coinapi/T-LIMITBOOK_FULL/D-2026060900/E-HYPERLIQUIDL4/

Historical L4 trades follow a similar structure, using T-TRADES instead of T-LIMITBOOK_FULL.

Once you've identified the relevant file, you can download it using the AWS CLI or Python.

The files are delivered in compressed .csv.gz format, making them suitable for storing and processing large amounts of historical information.

Detailed setup instructions are available in the CoinAPI Flat Files S3 documentation.

What makes Hyperliquid L4 historical data different?

This is an important distinction.

Most traditional order book datasets focus on aggregated liquidity at each price level, commonly called Level 2 (L2).

That information is useful, but it doesn't reveal the complete lifecycle of individual orders.

CoinAPI's Hyperliquid L4 Order Book Data goes further.

It includes order-level information such as:

• Individual order identifiers
• Order prices and sizes
• Order updates and lifecycle events
• Buy and sell sides
• Account identifiers where available
• Time-in-force and order-type information

These records can be used to reconstruct historical order book states and study how liquidity changed over time.

CoinAPI also provides historical Hyperliquid L4 trades, including maker/taker order identifiers and account attribution where available from the exchange.

That level of detail becomes particularly valuable for execution analysis, market microstructure research, and sophisticated backtesting.

For more information, see How to Reconstruct Hyperliquid L4 Order Books Correctly.

What about candles and funding rates?

Not every research project requires L4 data.

For historical price analysis, CoinAPI provides OHLCV candles through its Market Data REST API and Flat Files.

Developers can request specific time intervals or download larger datasets for historical analysis.

Historical Hyperliquid funding rates are also accessible through CoinAPI's Metrics API using the DERIVATIVES_FUNDING_RATE_CURRENT metric, subject to symbol coverage.

This means you can work with different levels of market information depending on your application, without forcing every workflow into the same download method.

Best for: Developers, quantitative researchers, and institutions that need structured historical datasets, bulk downloads, detailed order-level history, and consistent interfaces for production research.

Which Hyperliquid Historical Data Source Should You Choose?

Here's how the three approaches compare.

The choice comes down to what you're building.

If you're exploring Hyperliquid's original historical records, the official archive is a reasonable place to start.

If you want to automate data collection or experiment with existing code, GitHub tools may help.

And if you need structured historical downloads, consistent access methods, or detailed L4 order-level information, CoinAPI offers a more specialized solution.

Build on Hyperliquid Data

There are several ways to download Hyperliquid historical data, but they aren't interchangeable.

A few hours of candle history, several months of trade records, and an individual-order market replay are very different data requirements.

Hyperliquid's official archives provide exchange-native records. GitHub projects offer tools for collecting and processing them. CoinAPI provides structured historical datasets through REST and S3-compatible Flat Files, including granular L4 order book information.

The key is choosing the source that provides the level of detail, historical coverage, and access method your project actually needs.

Explore CoinAPI Hyperliquid historical data to see the available datasets and download options.

👉 Get Your API Key and Start with Free Credits

Related Topics

• What Is Level 4 (L4) Order Book Data?
• CoinAPI Introduces Hyperliquid L4 Data
• Hyperliquid HIP-3 Perpetual Deployer Contracts Are Now Listed in CoinAPI
• How to Reconstruct Hyperliquid L4 Order Books Correctly
• Why 99% of Hyperliquid Orders Never Execute
• Building a Reproducible Hyperliquid Order Book Replay from CoinAPI Book L4 Flat Files
• Demystifying Level 4 (L4) Order Book Data: Why Waiting for Block Confirmations Is Dead on Arrival
• Order Book L4: The Complete Guide to Level 4 Order Book Data