Overview

Event Types

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"
}

In most cases, the trade_id can be thought of as the unique identifier for a trade. However, there are cases where this isn’t true:

• Before 24 Nov 2023: For historical Hyperliquid trades before 24 Nov 2023, the trade_id for all trades was 0. For those trades, we construct a unique_id from other values.
• After 24 Nov 2023: There are a handful of trades where the Hyperliquid API returns the same trade_id for trades from different transactions. Because of this, we use the combination of trade_id and transaction_hash unique identifier for trades.

0x0000000000000000000000000000000000000000000000000000000000000000

See Hyperliquid TWAP for more details.

A transaction with action “Place TWAP order” will look like the one linked in the; [Hyperliquid Explorer](https://app.hyperliquid.xyz/explorer/tx/0xd6f17b6efa51bd1a1ff30420be17af02015400689f842aff45bb18a090bd8c44

Once such a transaction is sent multiple, orders will be placed within the specified time range, these will have a null transaction hash.

The hyperliquid node currently does not save order statuses unless the order already exists. Therefore open is not saved into the file, that the node generates, which is the source of this data.
For all the statuses the orders currently have run:

SELECT DISTINCT status
FROM hyperliquid.raw.orders
ORDER BY status;

is_trigger field is either true or false.
In the case where is_trigger is true the field

You can see all the different types of actions by running

SELECT DISTINCT action:type from hyperliquid.raw.transactions;

• for quicker query for a subset (may be missing some types)

SELECT DISTINCT action:type from (select * from hyperliquid.raw.transactions limit 100000000);