> ## 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. # Borrow/lend reserve history > History of Hyperliquid's borrow/lend reserves, sampled every minute from our own node since **2026-09-23**. For the current state, use `allBorrowLendReserveStates` and `borrowLendUserState`. - `token` is the Hyperliquid token index (`0` USDC, `150` HYPE, `197` UBTC, `268` USDT0, `360` USDH); omit it for every reserve. - Without `interval`, raw one-minute samples. With `interval`, one row per bucket carrying the **last** sample of the bucket, not an average; `time` is then the bucket start. - `limit` keeps the most recent samples of the window; `history` is returned oldest first. - Values are strings, as in `allBorrowLendReserveStates`. ## OpenAPI ````yaml /live-data/openapi-rest.json post /info#borrowLendReserveHistory 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#borrowLendReserveHistory: post: tags: - Borrow/Lend summary: Borrow/lend reserve history description: >- History of Hyperliquid's borrow/lend reserves, sampled every minute from our own node since **2026-09-23**. For the current state, use `allBorrowLendReserveStates` and `borrowLendUserState`. - `token` is the Hyperliquid token index (`0` USDC, `150` HYPE, `197` UBTC, `268` USDT0, `360` USDH); omit it for every reserve. - Without `interval`, raw one-minute samples. With `interval`, one row per bucket carrying the **last** sample of the bucket, not an average; `time` is then the bucket start. - `limit` keeps the most recent samples of the window; `history` is returned oldest first. - Values are strings, as in `allBorrowLendReserveStates`. operationId: borrowLendReserveHistory requestBody: required: true content: application/json: schema: type: object required: - type properties: type: type: string enum: - borrowLendReserveHistory token: type: integer minimum: 0 description: Token index; omit for every reserve startTime: type: integer description: 'Inclusive, epoch milliseconds. Default: now minus 7 days' endTime: type: integer description: Inclusive, epoch milliseconds interval: type: string enum: - 1m - 5m - 15m - 1h - 4h - 1d description: Resampling; omit for raw one-minute samples limit: type: integer minimum: 1 maximum: 10000 default: 1000 example: type: borrowLendReserveHistory token: 0 interval: 1h limit: 2 responses: '200': description: Reserve history, oldest first content: application/json: schema: type: object properties: token: type: integer nullable: true interval: type: string nullable: true history: type: array items: type: object properties: time: type: integer description: >- Sample time, or bucket start when `interval` is set (ms) token: type: integer tokenName: type: string borrowYearlyRate: type: string supplyYearlyRate: type: string balance: type: string utilization: type: string description: Borrowed รท supplied oraclePx: type: string ltv: type: string description: Loan-to-value totalSupplied: type: string totalBorrowed: type: string example: token: 0 interval: 1h history: - time: 1790409600000 token: 0 tokenName: USDC borrowYearlyRate: '0.05' supplyYearlyRate: '0.0279124045' balance: '208202451.005587' utilization: '0.6202756556' oraclePx: '1' ltv: '0' totalSupplied: '548298787.797238' totalBorrowed: '340096390.067647' - time: 1790413200000 token: 0 tokenName: USDC borrowYearlyRate: '0.05' supplyYearlyRate: '0.0278340968' balance: '209209869.07949' utilization: '0.6185354843' oraclePx: '1' ltv: '0' totalSupplied: '548438471.178158' totalBorrowed: '339228655.390016' '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. ````