Skip to main content
POST
/
info
userFills | Hyperliquid Info API
curl --request POST \
  --url https://hypercore.goldrushdata.com/info \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "<string>",
  "user": "<string>",
  "aggregateByTime": true
}
'
{
  "coin": "<string>",
  "px": "<string>",
  "sz": "<string>",
  "side": "<string>",
  "time": 123,
  "startPosition": "<string>",
  "dir": "<string>",
  "closedPnl": "<string>",
  "hash": "<string>",
  "oid": 123,
  "tid": 123,
  "crossed": true,
  "fee": "<string>",
  "feeToken": "<string>",
  "builderFee": "<string>",
  "twapId": {},
  "cloid": {}
}

Credit Cost

1 per call

Processing

Realtime
The Hyperliquid info endpoint with type: "userFills" is used to fetch a user’s most recent trade fills without specifying a time window.
  • Wire-equal to POST api.hyperliquid.xyz/info with {"type": "userFills", "user": "..."}.
  • Each response contains at most 2,000 fills.
  • For real-time push instead of windowed polling, subscribe to walletTxs and read HypercoreFillTransaction events.
Returns the most recent fills for a user, up to 2,000. Use this when you need the latest trade activity without specifying a time window. User-keyed. The upstream Hyperliquid API caps each response at 2,000 fills per wallet.

​
Endpoint

POST https://hypercore.goldrushdata.com/info
Authorization: Bearer <GOLDRUSH_API_KEY>
Content-Type: application/json

​
Request

​
type
string
required
Always "userFills".
​
user
string
required
The wallet address (lowercase 0x-prefixed hex).
​
aggregateByTime
boolean
When true, partial fills sharing the same timestamp are consolidated into one row. Default false.

​
Example

curl -X POST https://hypercore.goldrushdata.com/info \
  -H "Authorization: Bearer $GOLDRUSH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "userFills",
    "user": "0x31ca8395cf837de08b24da3f660e77761dfb974b"
  }'

​
Response

An array of fill objects ordered most-recent-first. 
[
  {
    "coin": "BTC",
    "px": "43250.5",
    "sz": "0.1",
    "side": "B",
    "time": 1735689600000,
    "startPosition": "0",
    "dir": "Open Long",
    "closedPnl": "0",
    "hash": "0x6b9c0a4a3d54b0d4d6b1a0c4d8c9e7f2b6e5d3c2a1f0e9d8c7b6a5f4e3d2c1b0a",
    "oid": 95012345,
    "tid": 678900012345,
    "crossed": true,
    "fee": "2.16",
    "feeToken": "USDC"
  }
]

​
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.
​
coin
string
Asset symbol - e.g. "BTC", "ETH" for perps; spot pairs use the @N form (e.g. "@107").
​
px
string
Fill execution price.
​
sz
string
Fill size.
​
side
string
"B" for buy/long, "A" for ask/short.
​
time
int
Unix timestamp in milliseconds when the fill executed.
​
startPosition
string
Signed position size on the same coin immediately before this fill.
​
dir
string
Human-readable direction label - e.g. "Open Long", "Close Short", "Buy", "Sell".
​
closedPnl
string
Realized PnL in USDC attributable to this fill (zero when the fill opens or extends a position).
​
hash
string
L1 transaction hash that included this fill.
​
oid
int
Parent order ID.
​
tid
int
Unique trade ID.
​
crossed
boolean
true when the fill came from the taker side of the order, false when it was the maker side.
​
fee
string
Trading fee paid for this fill, denominated in feeToken.
​
feeToken
string
Symbol the fee was paid in - typically "USDC".
​
builderFee
string
Optional. Builder fee paid for this fill if the order routed through a builder code.
​
twapId
int | null
Optional TWAP order ID if this fill is a slice of a TWAP order.
​
cloid
string | null
Optional client order ID if one was set at order placement.

userFillsByTime

fetch a user’s trade fills within a specific time window for P&L recaps, tax ledger reconstruction, or…

userTwapSliceFills

fetch a user’s most recent TWAP slice fills for execution-quality analytics on algorithmic orders.

userFunding

fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.

userNonFundingLedgerUpdates

fetch a user’s USDC and account ledger history within a time window, excluding funding payments, for…
Last reviewed: 2026-05-21