Skip to main content
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.

Filter fields

Behavior

  • Omitted filter = matches everything (no restriction on that dimension)
  • Empty array [] = matches nothing
  • No filters field = firehose (all events)

Umbrella types

Some type names match a group of related events: Use exact type names like "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):
Returns: every new order, filled order, canceled order, rejected order, and every trade execution. Only BTC orders:
Track a specific wallet:
Returns all events from this address across both consensus layers. Pre-consensus cancels only:
These arrive before the cancel is committed to a block. Full firehose (everything):
~6,500 events per second on mainnet. Includes both pre-consensus and confirmed events. Prediction market activity:
Track a specific outcome token. Use the # coin name format. All fills across every market (allFills firehose):
Every trade execution network-wide. Useful for analytics, VWAP calculations, and market-wide tracking. Liquidations only:
Only fills that were part of a liquidation event. Each matching fill carries a 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):
Only fills attributed to the given builder address via HIP-3. Useful for builder DEX operators tracking their own flow in real-time. Monitor liquidations for a specific wallet:
Alert-style feed for when a specific wallet is liquidated.