userFunding
Info API
userFunding
Commonly used to fetch a user’s per-coin funding payment history within a time window for funding-only P&L attribution.
POST
userFunding
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": "userFunding", "user": "..."}. - For real-time push, subscribe to
walletTxsand readHypercoreFundingEvententries. - Use
userNonFundingLedgerUpdatesfor deposits, withdrawals, transfers, vault flows, liquidations, and other balance-moving events.
[startTime, endTime) window. Each entry is one funding application: a coin, the rate that was applied, the position size at the time, and the resulting USDC delta (negative = paid, positive = received).
User-keyed. Use this for funding-only P&L attribution; use userNonFundingLedgerUpdates for everything else.
Endpoint
Request
Always
"userFunding".The wallet address (lowercase 0x-prefixed hex).
Unix timestamp in milliseconds. Inclusive lower bound for the window.
Unix timestamp in milliseconds. Inclusive upper bound. Defaults to current server time when omitted.
Example
Response
An array of funding event objects, one per applied funding interval and coin.Field descriptions
All numeric
delta fields are returned as decimal strings. Do not parse them as floats - keep them as strings or use a fixed-precision decimal type.Unix timestamp in milliseconds when the funding payment was applied.
L1 transaction hash that included the funding application.
Funding-event payload.