> ## 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.
# builderFills | Hyperliquid Info API
> Hyperliquid builderFills: fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics.
1 per call
Realtime
The Hyperliquid info endpoint with `type: "builderFills"` is used to fetch a builder’s most recent attributed trade fills for revenue attribution and order-flow analytics.
Estimate your monthly cost for this API using the [Pricing Calculator](/pricing-calculator?endpoint=%2Fapi-reference%2Fhyperliquid-info%2Fbuilder-fills).
* GoldRush-native: No `POST api.hyperliquid.xyz/info` equivalent. Available only via `POST hypercore.goldrushdata.com/info`.
* Each response contains at most 2,000 fills, ordered most-recent first.
* For windowed queries for revenue reports and monthly reconciliation, use `builderFillsByTime`.
* For real-time push instead of windowed polling, subscribe to `walletTxs` and read `HypercoreFillTransaction` events.
Returns the 2,000 most recent fills attributed to a builder address. Use this when you operate a builder code and want to inspect the order flow routed through it without specifying a time window.
Builder-keyed. GoldRush-native so there is no upstream Hyperliquid `/info` equivalent.
## Endpoint
```
POST https://hypercore.goldrushdata.com/info
Authorization: Bearer
Content-Type: application/json
```
## Request
Always `"builderFills"`.
The builder address that orders were routed through. Must be a `0x`-prefixed 42-character hex address.
When `true`, partial fills sharing the same timestamp are consolidated into one row. Default `false`.
Pagination cursor — a Unix timestamp in milliseconds encoded as a string. When set, returns fills strictly before this time. Use the `time` value of the oldest fill in the previous page to fetch the next page.
### 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": "builderFills",
"builder": "0x0000000000000000000000000000000000000000"
}'
```
```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: "builderFills",
builder: "0x0000000000000000000000000000000000000000",
}),
});
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": "builderFills",
"builder": "0x0000000000000000000000000000000000000000",
},
)
fills = response.json()
```
## Response
An array of fill objects ordered most-recent-first. Each entry is a fill from an order that was routed through the builder address.
```json theme={null}
[
{
"user": "0x73f9c53a8b15e43056d5599f6488ac9a8730f85d",
"coin": "HYPE",
"px": "66.977",
"sz": "0.69",
"side": "B",
"time": 1781518798259,
"startPosition": "0",
"dir": "Open Long",
"closedPnl": "0",
"hash": "0x2b7bd2df9499dfef2cf5043dc500b402068500c52f9cfec1cf447e32539db9d9",
"oid": 469533808540,
"crossed": true,
"fee": "0.048524",
"tid": 332575399132451,
"feeToken": "USDC",
"builderFee": "0.027728",
"cloid": "0xff8ffaa775354e8faf1eaa18127d6b5e"
}
]
```
### Field descriptions
All numeric fields (`px`, `sz`, `startPosition`, `closedPnl`, `fee`, `builderFee`) are returned as **decimal strings** with full upstream precision (up to 18 decimal places). Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.
The trader's wallet address - the account that placed the order routed through the builder code.
Asset symbol - e.g. `"BTC"`, `"ETH"` for perps; spot pairs use the `@N` form (e.g. `"@107"`); HIP-3 markets use the deployer-prefixed form.
Fill execution price.
Fill size.
`"B"` for buy/long, `"A"` for ask/short.
Unix timestamp in milliseconds when the fill executed.
Signed position size the trader held on this coin immediately before this fill.
Human-readable direction label - `"Open Long"`, `"Open Short"`, `"Close Long"`, `"Close Short"`, `"Buy"`, `"Sell"`, or position-flip labels `"Long > Short"` / `"Short > Long"`.
Realized PnL in USDC attributable to this fill for the trader (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 by the trader for this fill, denominated in `feeToken`.
Symbol the fee was paid in - typically `"USDC"`.
Optional. Builder fee earned for this fill, denominated in `feeToken`. Omitted when no builder fee was charged.
Optional. Client order ID (`0x`-prefixed 32-character hex) if one was set at order placement.
Optional. Present only when this fill closed a position as part of a liquidation event.
The wallet whose position was liquidated.
Mark price at the time of liquidation.
Liquidation method - e.g. `"Market"`.
## Related endpoints
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 trade fills within a time window for P\&L recaps and tax ledger reconstruction.
fetch a user's most recent TWAP slice fills for execution-quality analytics on algorithmic orders.
*Last reviewed: 2026-06-16*