userFills
Info API
userFills
Commonly used to fetch a user’s most recent trade fills without specifying a time window.
POST
userFills
Documentation Index
Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
Credit Cost
1 per call
Processing
Realtime
- Wire-equal to
POST api.hyperliquid.xyz/infowith{"type": "userFills", "user": "..."}. - Each response contains at most 2,000 fills.
- For real-time push instead of windowed polling, subscribe to
walletTxsand readHypercoreFillTransactionevents.
Endpoint
Request
Always
"userFills".The wallet address (lowercase 0x-prefixed hex).
When
true, partial fills sharing the same timestamp are consolidated into one row. Default false.Example
Response
An array of fill objects ordered most-recent-first.Field descriptions
All numeric fields (
px, sz, startPosition, closedPnl, fee, builderFee) are returned as decimal strings, preserving upstream precision. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.Asset symbol - e.g.
"BTC", "ETH" for perps; spot pairs use the @N form (e.g. "@107").Fill execution price.
Fill size.
"B" for buy/long, "A" for ask/short.Unix timestamp in milliseconds when the fill executed.
Signed position size on the same coin immediately before this fill.
Human-readable direction label - e.g.
"Open Long", "Close Short", "Buy", "Sell".Realized PnL in USDC attributable to this fill (zero when the fill opens or extends a position).
L1 transaction hash that included this fill.
Parent order ID.
Unique trade ID.
true when the fill came from the taker side of the order, false when it was the maker side.Trading fee paid for this fill, denominated in
feeToken.Symbol the fee was paid in - typically
"USDC".Optional. Builder fee paid for this fill if the order routed through a builder code.
Optional TWAP order ID if this fill is a slice of a TWAP order.
Optional client order ID if one was set at order placement.