> ## 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. `accountFunding` is an alias and returns the same response. Also served as `GET /funding/userFunding` (Indexed 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`: to page backwards without gaps, request up to `limit=5000`; 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 `[]` rather than estimated values. A new settlement is available about 30 seconds after the hour. ## OpenAPI ````yaml /live-data/openapi-rest.json post /info#userFunding openapi: 3.0.3 info: title: 'Hypedexer API: Live Data (REST)' version: 0.1.0 description: >- REST API for real-time Hyperliquid market data served from our own Hyperliquid nodes. All data is accessed through a single unified endpoint `POST /info` that dispatches based on the `type` field in the JSON body. ## Request types | Type | Description | Handled | |------|-------------|----------| | `metaAndAssetCtxs` | Asset context (funding, OI, prices) | Locally (Redis cache) | | `allMids` | Mid prices for all coins | Locally (Redis cache) | | `userFills` / `userFillsByTime` | Fills for a specific user | Locally (volume files) | | `allFills` | All fills globally | Locally (volume files) | | `trades` | Trade data | Locally (volume files) | | `l2Book` / `l2Books` | L2 order book snapshot | Locally | | `availableDates` | Available data dates | Locally | | `clearinghouseState` | Clearinghouse state (single/multi-user) | Locally with upstream proxy per user | | `userFunding` / `accountFunding` | Funding payments of a user | Indexed history, returned unwrapped | | `userNonFundingLedgerUpdates` | Native ledger of a user: deposits, withdrawals, transfers, vaults, staking, borrow/lend | Indexed history, returned unwrapped | | `historicalOrders` | Latest orders of a user with their status | Indexed history, returned unwrapped | | `borrowLendReserveHistory` | Borrow/lend reserve history, one sample per minute | Indexed history, returned unwrapped | | `meta`, `spotMeta`, `openOrders`, ... | Proxied to local Hyperliquid node | Proxied to upstream | ## Authentication Optional. When `API_KEY` is configured on the server, all requests must include: ``` Authorization: Bearer ``` ## Response format Most types return: ```json { "result": , "cursor": null } ``` `allMids` returns the result directly (not wrapped): ```json { "BTC": "66764.5", "ETH": "3421.2" } ``` Proxied types return the upstream response as-is. contact: name: Hypedexer servers: - url: https://api.hypedexer.com description: Production, routed to the nearest region (EU or JP) security: - BearerAuth: [] tags: - name: Health description: Service health and info. - name: Asset Context description: >- Real-time asset context data: funding, open interest, oracle/mark/mid prices, volumes. - name: Mid Prices description: Mid prices for all coins, optionally filtered by DEX. - name: Fills description: >- Executed fills from the Hyperliquid fullnode volumes. Supports user-specific and global queries. - name: Trades description: Trade data from the fullnode volumes. - name: Order Book description: L2 order book snapshots. - name: Metadata description: Volume availability and data metadata. - name: Clearinghouse description: >- Clearinghouse state with multi-user support. Each user is fetched individually from the upstream Hyperliquid node. - name: Proxied Perpetuals description: >- Perpetual market metadata, margin, OI caps, DEX configs. Proxied to upstream Hyperliquid node. - name: Proxied Spot description: >- Spot market metadata, balances, and deploy state. Proxied to upstream Hyperliquid node. - name: Proxied Trading description: >- Orders, positions, and active asset data. Proxied to upstream Hyperliquid node. - name: Proxied Account description: >- User account info: fees, rate limits, sub-accounts, agents, roles. Proxied to upstream Hyperliquid node. - name: Proxied Vaults description: >- Vault summaries, equities, and leaderboards. Proxied to upstream Hyperliquid node. - name: Proxied Staking description: >- Delegations, staking summaries, and validator votes. Proxied to upstream Hyperliquid node. - name: Proxied Exchange description: >- Exchange status, liquidatable positions, web data. Proxied to upstream Hyperliquid node. - name: Account History description: >- Per-address history served from our index, in Hyperliquid's `info` shapes: funding payments, native ledger and orders. - name: Borrow/Lend description: >- History of Hyperliquid's borrow/lend reserves, sampled every minute from our own node. paths: /info#userFunding: post: tags: - Account History summary: User funding payments description: >- Hourly funding payments of a wallet, rebuilt from Hyperliquid's official node event archive. `accountFunding` is an alias and returns the same response. Also served as `GET /funding/userFunding` (Indexed 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`: to page backwards without gaps, request up to `limit=5000`; 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 `[]` rather than estimated values. A new settlement is available about 30 seconds after the hour. operationId: userFunding requestBody: required: true content: application/json: schema: type: object required: - type - user properties: type: type: string enum: - userFunding - accountFunding user: type: string description: Wallet address (0x-prefixed, case-insensitive) startTime: type: integer description: >- Inclusive lower bound on the settlement time, epoch milliseconds endTime: type: integer description: >- Inclusive upper bound on the settlement time, epoch milliseconds limit: type: integer minimum: 1 maximum: 5000 default: 500 example: type: userFunding user: '0x010461c14e146ac35fe42271bdc1134ee31c703a' startTime: 1781481600000 endTime: 1781481660000 limit: 2 responses: '200': description: Funding payments, newest settlement first content: application/json: schema: type: array items: type: object properties: time: type: integer description: >- Exact settlement timestamp in milliseconds, the same value Hyperliquid returns hash: type: string description: >- Always the zero hash: a funding payment has no transaction coin: type: string description: Market (top-level copy of `delta.coin`) usdc: type: string description: Payment in USDC (top-level copy of `delta.usdc`) szi: type: string description: Position size (top-level copy of `delta.szi`) delta: type: object properties: type: type: string enum: - funding coin: type: string description: Market usdc: type: string description: >- Payment in USDC. Positive = received, negative = paid szi: type: string description: >- Signed position size at settlement (negative = short) fundingRate: type: string description: Hourly funding rate applied nSamples: type: integer nullable: true description: >- Always `null`: one row per hourly payment, never a daily aggregate 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 '401': $ref: '#/components/responses/Unauthorized' security: - BearerAuth: [] components: responses: Unauthorized: description: >- Missing or invalid API key. The body is `missing api key` or `invalid api key`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Invalid API key schemas: ErrorResponse: type: object required: - error properties: error: type: string description: Error message securitySchemes: BearerAuth: type: http scheme: bearer description: >- Your Hypedexer API key, sent as `Authorization: Bearer `. The `X-API-Key: ` header and the `api_key` query parameter are accepted as well. ````