Allium provides comprehensive real-time (datastreams) and historical data for Hyperliquid. The data is indexed from our in-house nodes that we operate. We run three nodes concurrently to ensure high availability and data completeness. We have included guides on how to navigate Hyperliquid data and FAQs on the data.
This section is for the Hyperliquid L1. Click here if you are looking for the EVM-compatible blockchain HyperEVM

​
Data Delivery & Interfaces

We offer the following delivery methods for both historical and near real-time data for Hyperliquid.

Explorer

Via Allium App (Historical Data on Snowflake)

Datashares

Via Snowflake, Databricks, Google Cloud (Historical Data)

Datastreams

Via Kafka, Pub/Sub (Near Real-Time Data)

API Endpoints

Via API Endpoints
Historical Data CaveatsHyperliquid DEX Trades
  • Hyperliquid DEX Trades are fully backfilled for every address, except for ~4,000 traders (~1% of traders) who had made more than 10k trades at the time of backfill in March 2025.
  • This is because the Hyperliquid API only makes the last 10k trades available, and there are no other ways to retrieve the missing historical data. This means the following data is available:
  • Pre-March 2025: all trades are available for all addresses, except for ~4,000 traders, where only the last 10k trades are available
  • March 2025 onwards: all trades are available for all addresses
Hyperliquid Orders
  • Hyperliquid Orders cannot be backfilled. Data is available since we started running nodes in house. We minimise the possibility of missing out orders by running three nodes. Gaps may exist in the unexpected event of node failures.

​
Data Schemas

The following data schemas are available:
Using hyperliquid.dex.trades is recommended as it enriches the raw.trades table with relevant trade & token metadata
Table NameDescription
hyperliquid.metrics.overviewDaily overview metrics for Hyperliquid, including total transactions, active users, TVL and bridge flows.
hyperliquid.dex.tradesEnriched DEX trades with tokens metadata and builder fees (partial), enriched from hyperliquid.raw.trades.
hyperliquid.assets.transfersToken transfers on Hyperliquid L1. Currently only includes deposits & withdrawals for Arbitrum.

​
Raw Data Schemas

Table NameDescription
hyperliquid.raw.fillsRaw Hyperliquid fills data.
hyperliquid.raw.ordersRaw Hyperliquid orders data.
hyperliquid.raw.blocksBlocks level metadata, including block height, hash, timestamp, and proposer.
hyperliquid.raw.transactionsTransactions data for each block on Hyperliquid.
hyperliquid.raw.tokensList of tokens that are traded on Hyperliquid DEX, with token metadata such as token name and symbol. Currently only includes spot tokens.
hyperliquid.raw.builder_fillsFills completed builders, including builder fees and the builder address from 2024-10-27
hyperliquid.raw.builder_transactionsSuccessfully completed transactions with builder address and fee, built incrementally from hyperliquid.raw.transactions
hyperliquid.raw.builder_labelsBuildet address and builder identity mapping, source from publicly available data.
hyperliquid.raw.register_referralSuccessfull referral registration filetered from hyperliquid.raw.transactions. Contains the referral code used e.g. PURS and the address of the user registering the referral.
hyperliquid.raw.set_referrerSucessful registration of a referrer filtered from hyperliquid.raw.transactions. Contains the referral code used e.g. PURS and the address of the user settingt the referrer.

​
Data Characteristics

In this section, we explain some of the characteristics of Hyperliquid data.
The extra_fields column contains additional information for each trade including fees and liquidation details. Some caveats to be aware of:
  • New trades are first fetched from Hyperliquid Websocket API, so the extra_fields are initially unavailable. We attempt to refetch all new trades via the Info endpoint, to source the extra_fields. Given the 10k transaction limit on the API, it’s possible that some trades cannot be refetched.
  • Because of the above, trades may have:
    • extra_fields not populated with buyer or seller details: this means the trade could not be backfilled with additional information. These can be identified by extra_fields:source = 'api.hyperliquid.xyz/ws'
    • extra_fields populated with one of the buyer or seller details: we were able to backfill details for one side of the trade (i.e. the buy side or sell side)
    • extra_fields populated with both buyer and seller details: we were able to backfill details for both sides of the trade
**Sample on**
{
  "buyer": {
    "builder_fee": null,
    "closed_pnl": "0.0",
    "crossed": true,
    "dir": "Open Long",
    "fee": "0.0",
    "fee_token": "USDC",
    "liquidation": null,
    "order_id": 80667495079,
    "start_position": "99492.0"
  },
  "seller": {
    "builder_fee": null,
    "closed_pnl": "0.0",
    "crossed": false,
    "dir": "Open Short",
    "fee": "0.0",
    "fee_token": "USDC",
    "liquidation": null,
    "order_id": 80667490005,
    "start_position": "-361760.0"
  },
  "source": "api.hyperliquid.xyz/info"
}