> ## Documentation Index > Fetch the complete documentation index at: https://docs.hypedexer.com/llms.txt > Use this file to discover all available pages before exploring further. # User funding payments > Hourly funding payments of a wallet, rebuilt from Hyperliquid's official node event archive. Same data as `userFunding` over `POST /info` (Live Data REST API). - `time` is the exact settlement timestamp in milliseconds, the same value Hyperliquid returns; `startTime` and `endTime` are inclusive bounds on it. - Newest settlement first, then by coin (A to Z). All payments of one settlement share the same `time`: when a page comes back full, drop the rows carrying its oldest `time` and request again with `endTime` set to that `time` minus 1. - `usdc` is positive when the wallet received funding and negative when it paid; `szi` is the signed position size at settlement. - Coverage: complete from **2025-09-27 10:00 UTC**, the start of the node event archive. An earlier window returns `[]`. A new settlement is available about 30 seconds after the hour. ## OpenAPI ````yaml /api-reference/openapi.json get /funding/userFunding openapi: 3.0.3 info: title: 'Hypedexer API: Indexed Data' version: 1.0.0 description: >- API to query indexed Hyperliquid trading data. This API provides access to stored/indexed trading data: - **Fills**: Executed orders and fills (Spot-only or All = Spot + Perp) - **Analytics**: Aggregations and statistics based on indexed data - **Completed Trades**: Trade objects and their related fills - **Users**: User overviews, performance and activity - **Social Trading**: Per-trader equity curve, PnL calendar, account leverage and top trades - **Funding**: Funding rate history, user funding payments, predicted rates - **Liquidations**: Liquidation events with filters - **Overview**: Market dashboard metrics (volume, fees, traders, PnL) - **Spot**: Spot token metadata, pairs, and auctions - **TWAPs**: TWAP orders, execution stats and fills - **Vaults**: Vault details, summaries, equity, ledger > Note: No live streaming. Responses are computed from indexed data. servers: - url: https://api.hypedexer.com description: Production, routed to the nearest region (EU or JP) security: - ApiKeyAuth: [] tags: - name: Fills description: Fills endpoints. - name: Analytics description: Aggregations and stats. - name: Completed Trades description: Trades and fills. - name: Users description: User profiles. - name: Funding description: Funding rates and payments (HL-compatible). - name: Liquidations description: Liquidation events. - name: Overview description: Market dashboard metrics. - name: Spot description: Spot token metadata, pairs and auctions. - name: TWAPs description: TWAP orders, stats and fills. - name: Vaults description: Vault details, summaries, equity and ledger. - name: Social Trading description: >- Per-trader equity, PnL calendar, performance, account leverage and top trades. - name: Market history description: >- Historical Hyperliquid market microstructure: best bid/offer aggregates and spread statistics (April 2024 to February 2026), and the order book reconstructed minute by minute: April 2024 to February 2026 from our archive (top ~20 levels per side) and, since 23 September 2026, the full order book replayed from our own node. Served from the EU region. paths: /funding/userFunding: get: tags: - Funding summary: User funding payments description: >- Hourly funding payments of a wallet, rebuilt from Hyperliquid's official node event archive. Same data as `userFunding` over `POST /info` (Live Data REST API). - `time` is the exact settlement timestamp in milliseconds, the same value Hyperliquid returns; `startTime` and `endTime` are inclusive bounds on it. - Newest settlement first, then by coin (A to Z). All payments of one settlement share the same `time`: when a page comes back full, drop the rows carrying its oldest `time` and request again with `endTime` set to that `time` minus 1. - `usdc` is positive when the wallet received funding and negative when it paid; `szi` is the signed position size at settlement. - Coverage: complete from **2025-09-27 10:00 UTC**, the start of the node event archive. An earlier window returns `[]`. A new settlement is available about 30 seconds after the hour. parameters: - name: user in: query required: true description: User address (0x…) schema: type: string - name: startTime in: query description: Inclusive lower bound on the settlement time (epoch ms) schema: type: integer - name: endTime in: query description: Inclusive upper bound on the settlement time (epoch ms) schema: type: integer - name: limit in: query schema: type: integer default: 500 minimum: 1 maximum: 5000 - name: X-API-Key in: header schema: type: string responses: '200': description: OK content: application/json: schema: type: array items: type: object properties: time: type: integer description: Exact settlement timestamp in milliseconds hash: type: string description: >- Always the zero hash: a funding payment has no transaction coin: type: string usdc: type: string szi: type: string delta: type: object properties: type: type: string enum: - funding coin: type: string usdc: type: string description: Positive = received, negative = paid szi: type: string description: Signed position size at settlement fundingRate: type: string description: Hourly funding rate applied nSamples: type: integer nullable: true description: 'Always null: one row per hourly payment' example: - time: 1781481600049 hash: >- 0x0000000000000000000000000000000000000000000000000000000000000000 coin: 0G usdc: '0.167934' szi: '-44405' delta: type: funding coin: 0G usdc: '0.167934' szi: '-44405' fundingRate: '0.0000125' nSamples: null - time: 1781481600049 hash: >- 0x0000000000000000000000000000000000000000000000000000000000000000 coin: 2Z usdc: '0.246354' szi: '272895' delta: type: funding coin: 2Z usdc: '0.246354' szi: '272895' fundingRate: '-0.0000126156' nSamples: null components: securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: >- Your Hypedexer API key. Create one in the console at https://app.hypedexer.com. `Authorization: Bearer ` and the `api_key` query parameter are accepted as well. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.