You can only use this endpoint on the official Hyperliquid public API. It is not available through Chainstack, as the open-source node implementation does not support it yet.
info endpoint with type: "userFunding" retrieves the funding history for a specific user account on the Hyperliquid exchange. This endpoint provides detailed information about funding payments and receipts across all perpetual positions over time, allowing users to track their funding costs and analyze trading performance.
This endpoint is similar to userNonFundingLedgerUpdates — both query the Hyperliquid
info API with different type values and return structurally similar arrays. The key difference is in the output content: this page returns only funding events, while userNonFundingLedgerUpdates returns all other balance‑affecting ledger updates (deposits, withdrawals, transfers, liquidations, spot activity), excluding funding.Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
Request body
type(string, required) — The request type. Must be"userFunding"to retrieve user funding history.user(string, required) — Address in 42-character hexadecimal format; e.g. 0x0000000000000000000000000000000000000000.startTime(integer, required) — Start time in milliseconds, inclusive.endTime(integer, optional) — End time in milliseconds, inclusive. Defaults to current time.
Response
The response is an array of funding events, chronologically ordered from oldest to newest. Each event represents a funding payment or receipt for a specific perpetual position.Response structure
Each funding event contains: Event metadata:time— Unix timestamp in milliseconds when the funding occurredhash— Transaction hash (typically zero hash for funding events)
delta.type— Always “funding” for funding eventsdelta.coin— Asset symbol (e.g., “BTC”, “ETH”, “SOL”)delta.usdc— Funding amount in USDC (negative = paid, positive = received)delta.szi— Position size at the time of fundingdelta.fundingRate— Funding rate applied for this period
Data interpretation
Funding payments vs receipts:- Negative
usdcvalues indicate funding paid (user is long in a positive funding environment or short in negative funding) - Positive
usdcvalues indicate funding received (user is short in positive funding environment or long in negative funding)
szishows the position size when funding was applied- Positive
sziindicates long positions, negative indicates short positions - Larger absolute position sizes result in proportionally larger funding payments/receipts
fundingRaterepresents the rate charged per unit of time- Positive rates favor shorts (longs pay shorts)
- Negative rates favor longs (shorts pay longs)
- Rates are typically charged every 8 hours (3 times daily)
Trading insights
Funding cost analysis
Position cost calculation:- Total funding cost = sum of all
usdcvalues for a specific asset - Daily funding impact = funding payments/receipts over 24-hour periods
- Funding rate trends indicate market sentiment and position bias
- High funding costs may indicate overleverage or poor market timing
- Consistent funding receipts suggest alignment with market structure
- Funding patterns help optimize position entry and exit timing
Market sentiment indicators
Funding rate patterns:- Consistently positive funding rates indicate bullish bias (demand for long positions)
- Negative funding rates suggest bearish sentiment (demand for short positions)
- Extreme funding rates often coincide with market turning points
- Monitor funding costs relative to trading profits
- Consider position size adjustments during high funding periods
- Use funding rate changes as market sentiment indicators
Historical analysis
Performance tracking
Funding efficiency:- Track funding costs as percentage of trading profits
- Compare funding expenses across different assets
- Identify optimal position sizing for funding cost management
- Analyze funding rate cycles for entry/exit optimization
- Monitor funding rate extremes for reversal signals
- Use historical funding patterns for strategy backtesting
Example request
Shell
Example response
Use cases
Theinfo endpoint with type: "userFunding" is essential for applications that need to:
- Trading analytics: Analyze funding costs and their impact on trading performance
- Portfolio management: Track funding expenses across multiple positions and assets
- Strategy optimization: Optimize position sizing and timing based on funding patterns
- Performance attribution: Separate trading gains from funding costs for accurate measurement
- Tax reporting: Calculate funding payments and receipts for tax documentation
- Risk management: Monitor funding costs as part of overall trading risk assessment
- Market analysis: Study funding rate patterns to understand market sentiment
- Algorithm development: Incorporate funding costs into automated trading strategies
- Position management: Make informed decisions about position holds based on funding trends
- Cost analysis: Compare funding efficiency across different trading strategies
- Backtesting: Include historical funding costs in strategy backtesting and simulation
- Reporting tools: Generate comprehensive trading reports including funding breakdowns
Body
application/json
The request type. Must be 'userFunding' to retrieve user funding history.
Available options:
userFunding User wallet address (0x...)
Start time in milliseconds, inclusive
End time in milliseconds, inclusive. Defaults to current time.
Response
200 - application/json
User funding history data
Array of funding events for the user