> ## 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.
# userFillsByTime | Hyperliquid Info API
> Hyperliquid userFillsByTime: fetch a user’s trade fills within a time window for P&L recaps and tax ledger reconstruction.
1 per call
Realtime
The Hyperliquid info endpoint with `type: "userFillsByTime"` is used to fetch a user’s trade fills within a time window for P\&L recaps and tax ledger reconstruction.
Estimate your monthly cost for this API using the [Pricing Calculator](/pricing-calculator?endpoint=%2Fapi-reference%2Fhyperliquid-info%2Fuser-fills-by-time).
* Wire-equal to `POST api.hyperliquid.xyz/info` with `{"type": "userFillsByTime", "user": "...", "startTime": ...}`.
* Each response contains at most 2,000 fills; widen the window in chunks or page by advancing `startTime` if you need more.
* GoldRush serves this `type` from a dedicated HyperCore historical store, so windows older than upstream Hyperliquid’s 10,000-fill retention are still fulfilled.
* For real-time push instead of windowed polling, subscribe to `walletTxs` and read `HypercoreFillTransaction` events.
* Use `userFills` (no `Time` suffix) when you only need the most recent N fills without specifying a window.
Returns a single user’s fills bounded by a `[startTime, endTime)` window in milliseconds. Use this when you want fills since a specific moment - daily P\&L recaps, post-deploy backfills, or rebuilding a tax ledger - rather than the most recent N fills.
User-keyed. The upstream Hyperliquid API caps each response at **2,000 fills**; page by advancing `startTime`. **NOT LIMITED TO THE 10,000 MOST RECENT FILLS.** GoldRush serves this `type` from a dedicated HyperCore historical store so windows extending past the upstream retention limit are fulfilled from GoldRush data rather than truncated.
## Endpoint
```
POST https://hypercore.goldrushdata.com/info
Authorization: Bearer
Content-Type: application/json
```
## Request
Always `"userFillsByTime"`.
The wallet address (lowercase 0x-prefixed hex).
Unix timestamp in milliseconds. Inclusive lower bound.
Unix timestamp in milliseconds. Inclusive upper bound. Defaults to current server time when omitted.
When `true`, partial fills sharing the same timestamp are consolidated into one row. Default `false`.
### Example
```bash cURL theme={null}
curl -X POST https://hypercore.goldrushdata.com/info \
-H "Authorization: Bearer $GOLDRUSH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "userFillsByTime",
"user": "0x31ca8395cf837de08b24da3f660e77761dfb974b",
"startTime": 1735689600000
}'
```
```typescript TypeScript theme={null}
const response = await fetch("https://hypercore.goldrushdata.com/info", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
type: "userFillsByTime",
user: "0x31ca8395cf837de08b24da3f660e77761dfb974b",
startTime: 1735689600000,
}),
});
const fills = await response.json();
```
```python Python theme={null}
import os, requests
response = requests.post(
"https://hypercore.goldrushdata.com/info",
headers={"Authorization": f"Bearer {os.environ['GOLDRUSH_API_KEY']}"},
json={
"type": "userFillsByTime",
"user": "0x31ca8395cf837de08b24da3f660e77761dfb974b",
"startTime": 1735689600000,
},
)
fills = response.json()
```
## Response
An array of fill objects ordered by `time`.
```json theme={null}
[
{
"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.
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.
## Related endpoints
fetch a user's TWAP slice fills within a time window for execution-quality reconciliation on algorithmic…
fetch a builder’s attributed trade fills within a time window for revenue attribution and fee accounting.
fetch a user's most recent trade fills without specifying a time window.
fetch a user's most recent TWAP slice fills for execution-quality analytics on algorithmic orders.
*Last reviewed: 2026-06-16*