Get order flow
- Hyperliquid
- HIP-3
- HIP-4
/v1/hyperliquid/orders/{symbol}/flow. Plain perp symbols such as BTC.granularity parameter controls how flow is bucketed.
Request parameters
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
symbol | path | string | Yes | Trading pair symbol, e.g. BTC |
start | query | string | No | Start time, ISO 8601 (e.g. 2026-01-01T00:00:00Z) |
end | query | string | No | End time, ISO 8601 |
granularity | query | string | No | Aggregation granularity |
limit | query | integer | No | Max results. Default 1000, max 10000 |
cursor | query | string | No | Pagination cursor from meta.next_cursor |
When to use it
Order flow answers “what was the shape of order activity here?” rather than “what filled?” Use Trades when you need the executions, Order history when you need each order’s lifecycle, and order flow when you want the aggregated placement and cancel pressure over a window. Thegranularity parameter trades resolution for size: finer buckets show more detail but return more rows. Keep the venue family, symbol, window, and granularity with every stored result so a later run reproduces the same view. Flow is most useful alongside the L4 book, since the same window of activity is what moved the resting orders.
Stream it live
Order flow is a REST-side aggregation, so there is no order-flow channel. For live order activity, stream the L4 order events (l4_orders, or the venue-prefixed variant) and aggregate placement and cancel pressure yourself.
Export in bulk
There is no standalone order-flow export schema. Export the raw order events with thel4_orders (Order Events) schema ($8/GB, $25 minimum) and aggregate to flow downstream. Schema columns and coverage keys are on Export Schemas.