Frequently Asked Questions

The Hyperliquid API currently has a limitation, so only the last 10k trades for each address is available. If an address has made less than 10k trades as of the time of backfill (~March 2025), then all their historical trades will be available. However, fetching all historical trades is not currently possible for addresses that have done more than 10k trades. Once historical data becomes accessible, any gaps will be backfilled.
As of the beginning of June we have remediated this problem.
At least 99.5% of the entries include buyer and seller in the extra_fields.
The amount of entries that are missing either the buyer, seller or both in the extra_fields is less than 0.5%.
This was due to two limitations.
  1. Hyperliquid’s endpoint not returning more than the 10000 latest fills.
  2. Hyperliquid’s api rate limiting, which causes us to not be able to fetch the data for all the trades fast enough.
Issue 1 coupled with 2 can cause us to not be able to fetch the fills before the the end up outside the 10000 limit, for users with very high trading volume.
From 2025-06-08 12:18:08.047 all order status are available.Up until 2025-06-08 12:18:08.047 the nodes did not expose orders when they were placed. This meant that an order with ‘open’ status did not show up, only subsequent status changes would be reflected in the table.
While the data is available in both. It is not awalys possible to directly match them.

Trades & Orders

Use order id, which is available on the trade and the order.

Orders & Transactions

While an open order is placed by making a transaction, currently we do not have the order id of the transaction available to us. So making the connection is only possible by using the order timestamp along with the size and coin, and try to match it.

Trades & Transactions

Trades aren’t exactly 1-1 with transactions. The transaction in a trade refers to the a transaction made to open one of the orders in the transaction.Trades with 0x0 are made through TWAPS, these only have one transaction, the twapOpen and subsequent orders are done by the Hyperliquid Validators and therefore do not have a transaction hash.