> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Orders And L4 Lifecycle Routes

> Use 0xArchive order history, order flow, TP/SL, L4 diffs, and L4 history routes for reconstruction-oriented workflows.

Order lifecycle data is the higher-depth side of market data. It is not the default route for simple snapshots; use it when the question depends on order changes, user-level order events where supported, trigger orders, L4 diffs, or book reconstruction.

## Route Families

| Need                           | Start with                                                                                       |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| Hyperliquid core order history | `/v1/hyperliquid/orders/{symbol}/history`                                                        |
| Hyperliquid core order flow    | `/v1/hyperliquid/orders/{symbol}/flow`                                                           |
| Hyperliquid core TP/SL         | `/v1/hyperliquid/orders/{symbol}/tpsl`                                                           |
| Hyperliquid core L4            | `/v1/hyperliquid/orderbook/{symbol}/l4`, `/l4/diffs`, `/l4/history`                              |
| Hyperliquid Spot order history | `/v1/hyperliquid/spot/orders/{symbol}/history`                                                   |
| Hyperliquid Spot L4            | `/v1/hyperliquid/spot/orderbook/{symbol}/l4`, `/l4/diffs`, `/l4/history`                         |
| HIP-3 orders and L4            | `/v1/hyperliquid/hip3/orders/{symbol}/history`, `/flow`, `/tpsl`, and HIP-3 L4 order-book routes |
| HIP-4 orders and L4            | `/v1/hyperliquid/hip4/orders/{symbol}/history`, `/flow`, `/tpsl`, and HIP-4 L4 order-book routes |

## When To Use

Use these routes when the buyer or system needs order-level evidence: reconstruction seeds, full-depth book changes, TP/SL behavior, order flow, user-attributed order events where supported, or backtests that depend on order lifecycle rather than aggregated candles or trades.

Do not use these routes as the default for every market-data job. They can be heavier, access-gated, and harder to parse correctly than L2 snapshots or trade lists.

## Evaluation Fit

Order lifecycle routes should appear in an evaluation when the team cares about market microstructure, queue behavior, trigger order behavior, or reconstructing a book from changes. If the team only needs bars, current depth, or trade history, start with the lighter route family and add lifecycle data only after the first workflow is working.

## Implementation Rules

<Steps>
  <Step title="Name the order question">
    Is the job about book state, order events, TP/SL, flow, diffs, or historical reconstruction?
  </Step>

  <Step title="Choose the route family">
    Core, Spot, HIP-3, and HIP-4 keep different namespaces and symbol semantics.
  </Step>

  <Step title="Preserve lifecycle metadata">
    Store order ID, status, side, price, size, change type, timestamp, route, and request ID where present.
  </Step>

  <Step title="Pair with replay or reconstruction">
    Use [WebSocket Backtesting](/websocket/backtesting), [WebSocket L4 Order Book](/websocket/l4-orderbook), and [SDK Reconstruction](/sdks/reconstruction) when sequence matters.
  </Step>
</Steps>

## Next Step

Open [Example Responses](/response-examples) for L4 and lifecycle payload shapes, [SDK Reconstruction](/sdks/reconstruction) for local book state, [WebSocket Replay](/websocket/replay) for historical sequences, or [Order Book Routes](/rest-api/order-books) when the depth decision is still open.