Order History - 0xArchive

Order history is the per-order lifecycle: placements, fills, cancels, and status changes for a symbol. It is available on Hyperliquid core, Spot, HIP-3, and HIP-4. Lighter has no order-lifecycle routes.

Get order history

Hyperliquid
Spot
HIP-3
HIP-4

curl "https://api.0xarchive.io/v1/hyperliquid/orders/BTC/history" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

/v1/hyperliquid/orders/{symbol}/history. Plain perp symbols such as BTC.

curl "https://api.0xarchive.io/v1/hyperliquid/spot/orders/HYPE-USDC/history" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

/v1/hyperliquid/spot/orders/{symbol}/history. Pair symbols such as HYPE-USDC. Spot supports the time-window filters (start, end, limit, cursor); the status, order-type, triggered, and wallet filters are core, HIP-3, and HIP-4 only.

curl "https://api.0xarchive.io/v1/hyperliquid/hip3/orders/km:US500/history" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

/v1/hyperliquid/hip3/orders/{symbol}/history. Namespaced builder symbols, case-sensitive.

curl "https://api.0xarchive.io/v1/hyperliquid/hip4/orders/%230/history" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"

/v1/hyperliquid/hip4/orders/{symbol}/history. Outcome side ids such as %230.

The OpenAPI spec types this route as a raw object array, so capture a live fixture and pin the fields you depend on before binding stable models. Records carry the order id, timestamps, status, and the price and size of each event.

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
`status`	query	string	No	Filter by order status
`order_type`	query	string	No	Filter by order type
`triggered`	query	boolean	No	Filter by whether the order was triggered
`user_address`	query	string	No	Filter by wallet address
`limit`	query	integer	No	Max results. Default 1000, max 10000
`cursor`	query	string	No	Pagination cursor from `meta.next_cursor`

What the lifecycle covers

Each record is one event in an order’s life: placed, partially filled, filled, canceled, or triggered. Join history to Trades and the L4 book with the order id to follow a single order from placement to fill, and use the status and order_type filters to narrow to the lifecycle stage you care about. The triggered filter separates orders that fired from those that rested. Store the order id, status, and timestamps so a later run can rebuild the same sequence.

Stream it live

There is no separate order-history channel. Live order events stream through the L4 order channels (l4_orders, plus spot_l4_orders, hip3_l4_orders, hip4_l4_orders), which carry placements, fills, cancels, and status changes as they happen.

ws.send(JSON.stringify({ op: "subscribe", channel: "l4_orders", symbol: "BTC" }));

Connection and reconnect handling live in the WebSocket tab; see WebSocket Channels for the family matrix.

Export in bulk

For order-event history as files, use the l4_orders (Order Events / TP/SL) export schema ($8/GB, $25 minimum), delivered as Parquet with ZSTD compression. Build a selection in the Data Catalog; columns and coverage keys are on Export Schemas.

Use Order flow for aggregated activity, Take profits & stop losses for trigger orders, or Order books for the L4 book those orders rest in.

​Get order history

​Request parameters

​What the lifecycle covers

​Stream it live

​Export in bulk

​Next

Get order history

Request parameters

What the lifecycle covers

Stream it live

Export in bulk

Next