Hyperliquid Fill Views - All, User, Builder, Liquidation
Choose among Hyperliquid V3 all-fill, user, builder, and liquidation live streams.
V3 fill views expose one account's execution record per Fill, including position context, order identifiers, fees, and optional builder or liquidation metadata. Fills from one match share (coin, tid), but each participant remains a separate record.
Access
| Availability | Access | Details |
|---|---|---|
| Live | StreamAllFills, StreamUserFills, StreamBuilderFills, and StreamLiquidationFills | Typed live fills and sequence validation. |
| Live / replay | StreamFills | Provides raw fill envelopes with cursor-based access. |
| Historical | Hyperliquid Index fills | Provides all, user, builder, liquidation, and time-range history. |
| Archival | S3 Bucket | Provides archival fill files. |
Method family
| Method | Selection |
|---|---|
| StreamAllFills | All fills, optionally scoped by coin and owning user. |
| StreamUserFills | Fills whose own user equals one required account. |
| StreamBuilderFills | Fills attributed to one required builder.address. |
| StreamLiquidationFills | Fills carrying liquidation metadata, optionally filtered by liquidated account. |
All 4 methods are live-only with no historical replay. They use a per-subscription sequence; filtered blocks can still produce an empty fills list to preserve continuity. On a gap or ABORTED, reconnect for new live activity and recover the missing interval through a raw or indexed history surface.
Sample data
This synthetic V3 protobuf payload visibly redacts account, transaction, builder, and client-order identifiers:
time: 1785736814057
block_number: 1058646974
sequence: 1
fills: {
user: "<redacted-user>"
coin: "<redacted-market>"
px: "114250.0"
sz: "0.25"
side: "B"
time: 1785736814057
hash: "<redacted-transaction-hash>"
tid: 99887766
crossed: true
dir: "Open Long"
start_position: "0.0"
oid: 123456789
closed_pnl: "0.0"
fee: "0.285625"
fee_token: "USDC"
builder: { address: "<redacted-builder>" fee: "0.01" }
cloid: "<redacted-client-order-id>"
liquidation: {
liquidated_user: "<redacted-liquidated-user>"
mark_px: "114200.0"
method: "market"
}
}Optional nested messages are present only when they apply to the execution.
Related pages
- Whale tracking guide — Combine attributed fills with order-book and account signals.
- Matched trades — Use match-level executions when participant-specific records are unnecessary.