Filters narrow the event stream to only matching events. All filter dimensions use AND logic: if multiple filters are specified, an event must match all of them.Documentation Index
Fetch the complete documentation index at: https://hypernode-docs.polynode.dev/llms.txt
Use this file to discover all available pages before exploring further.
Filter fields
| Field | Type | Match Logic | Case |
|---|---|---|---|
action_types | string[] | Match on event type | Case-sensitive |
addresses | string[] | Match on event user | Case-insensitive |
assets | string[] | Match on event asset | Case-insensitive |
asset_ids | number[] | Match on event asset_id | Exact numeric |
builders | string[] | Match on fill data.builder (HIP-3 builder address) | Case-insensitive |
liquidations_only | boolean | Match fills where data.liquidation is present | N/A |
Behavior
- Omitted filter = matches everything (no restriction on that dimension)
- Empty array
[]= matches nothing - No
filtersfield = firehose (all events)
Umbrella types
Some type names match a group of related events:| Filter value | Matches |
|---|---|
"order" | order, order_filled, order_canceled, order_rejected |
"fill" | fill |
"cancel" | cancel |
"cancelByCloid" | cancelByCloid |
"batchModify" | batchModify |
"order_filled" or "order_rejected" to match a single event type.
There is no
order_open type. New resting orders use the type "order" with data.status: "open". To get only new resting orders, subscribe to "order" and filter client-side by data.status.Examples
All orders and fills (most common):# coin name format.
All fills across every market (allFills firehose):
data.liquidation object with liquidatedUser, markPx, and method. Both sides of the liquidation (liquidated user and liquidator) appear as separate fills with the same tid.
Fills for a specific builder (HIP-3):