| client_order_id | VARCHAR(16777216) | Custom order ID provided by the user |
| order_id | VARCHAR(16777216) | Order ID generated by Hyperliquid |
| coin | VARCHAR(16777216) | A unique identifier for the asset being traded: • The coin for perpetuals is the standard token symbol, e.g. HYPE • The coin for spot tokens is an ID representing a pair of tokens based on Hyperliquid’s metadata, e.g. @4 (coin) represents token 5/token 0, which corresponds to JEFF/USDC The metadata is available from the info endpoint of Hyperliquid’s API |
| is_take_profit_or_stop_loss | BOOLEAN | Boolean Whether this order is a take profit or stop loss order |
| is_trigger | BOOLEAN | Boolean Whether this order has a trigger condition. For instance the order is only in effect if the price goes above 25. See Notes for more details. |
| type | VARCHAR(16777216) | The type of order. Refer to the Hyperliquid Docs |
| original_size | VARCHAR(16777216) | The size of the original order For example if the order size has since changed since it was partially filled, then the original_size will show a different value |
| is_reduce_only | BOOLEAN | Whether this order can only reduce an existing position and cannot open or increase one. |
| side | VARCHAR(16777216) | B - Buy A - Ask (Sell) |
| size | VARCHAR(16777216) | Order size. This is the current order size. So if partially filled, this will be the size of the unfilled part |
| time_in_force | VARCHAR(16777216) | Behaviour for the order. Refer to the Hyperliquid Docs |
| order_timestamp | TIMESTAMP_NTZ(9) | This refers to the original order timestamp. See original_size. So depending on when the order status changes, this can be quite different from status_change_timestamp. |
| trigger_condition | VARCHAR(16777216) | What will make this order become active, go into the order book. For example ‘Price below 1560.1’ The value can also be ‘Triggered’ which means the trigger condition has already been met and the order is in active in the order book. For an example see SELECT * from hyperliquid.raw.orders where order_id = '44776647532'; |
| trigger_price | VARCHAR(16777216) | The price for it to be triggered, if it is a trigger. See is_trigger Will match the value in trigger_condition |
| limit_price | VARCHAR(16777216) | Maximum price the buyer or seller are willing to pay |
| children | VARIANT | Children will contain one or two orders, which will be added once the parent order is triggered. These can be a take profit and/or a stop loss. For examples see SELECT * from hyperliquid.raw.orders where order_id = '82039428821' or order_id = '82161896540' or order_id = '82182749399'; |
| status | VARCHAR(16777216) | The status which the order has after the order_status_change_timestamp. Refer to the Hyperliquid Docs for a list of all possible statuses. Currently we do not have the initial status Open refer to the Notes |
| user | VARCHAR(16777216) | user that owns the order |
| status_change_timestamp | TIMESTAMP_NTZ(9) | The time at which the status of this order changed. Basically represents the time at which the entries in this row took effect |
| unique_id | VARCHAR(16777216) | A unique identifier for each record |
| _created_at | TIMESTAMP_NTZ(9) | Timestamp of when the entry was created in the database. |
| _updated_at | TIMESTAMP_NTZ(9) | Timestamp of when the entry was last updated in the database. |
| builder_address | VARCHAR(16777216) | The address of the block builder (miner). |
| builder_fee | VARCHAR(16777216) | Total builder fees paid on the trade (buyer + seller), in fee-token units (NOT USD). For HL native perps the fee token is USDC so the value is numerically ≈ USD; on HIP-3 non-USDC and HIP-4 markets the unit is the per-side fee token. For a hydrated USD view, sum buyer_builder_fee_usd + seller_builder_fee_usd from marts_hyperliquid_predictions__trades (HIP-4) or hydrate per row via the hourly token price feed. |
