> ## 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. # Ledger events of all users > Non-funding ledger events (deposits, withdrawals, transfers, vaults, staking, borrow/lend, ...) of every user on Hyperliquid, or of a list of wallets, in time order: the REST counterpart of the [`allLedgerUpdates` WebSocket channel](/live-data/ws-all-ledger-updates). Use it to catch up after a disconnect, or to read a past window. Same items as the WebSocket channel: `time`, `hash`, `users` (the one or two addresses involved, sorted; a transfer between two addresses is returned once) and `delta`, the event as Hyperliquid emits it. **Paging**: `limit` items per page, ascending time. The response headers `X-Has-More` and `X-Next-Cursor` tell whether a next page exists; pass `X-Next-Cursor` as `cursor` with the same `startTime` / `endTime` / `users` / `types`. Pages always end on a whole millisecond. Without `users`, a page covers at most one day of events: it can then hold fewer than `limit` items, or none, with `X-Has-More: true`. Keep following `X-Next-Cursor` until `X-Has-More` is `false`. **Coverage**: complete for every user from 27 September 2025. Before that date, only some addresses are covered. Served from the EU region whatever the client's location. **Filters**: `users` (up to 20,000 wallets) and `types` (`delta.type` values) combine with AND. Unknown fields are refused with `422` and the name of the field, so a typo never returns the unfiltered stream. ## OpenAPI ````yaml /live-data/openapi-rest.json post /info#allLedgerUpdates 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, one user (`user`) or many in one call (`users`), per dex with `dex` | Locally with upstream proxy per user | | `openInterestHistory` | Open interest history of a market (~30 s samples, with mark price, 24h volume, funding, premium) | Indexed history | | `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 | | `userTwapSliceFills` | Fills of a user's TWAP orders with their parent | Indexed history, returned unwrapped | | `fills` / `recentFills` | Indexed fills with filters (compact shape) | Indexed history, returned unwrapped; paging in `X-Has-More` / `X-Next-Cursor` headers | | `builderFills` / `builderFillsByTime` / `builderOrdersByTime` | Every fill or order routed through one builder code | Indexed history | | `tpslBook` | Aggregated resting TP/SL trigger orders of a coin, by price | Indexed history | | `oraclePriceHistory` / `slippageHistory` / `marketLiquidityHistory` | Per-market series (~30 to 60 s samples, about 7 days) | Indexed history | | `stakingOverview` / `validatorAprHistory` / `globalStakingSummary` | Validator snapshots and network staking figures | Indexed history | | `liqHistory` | Liquidation events, cursor paging in headers | Indexed history | | `userTwapStatusesByTime` / `userTwapSummaries` | Status and latest state of a user's TWAP orders | Indexed history | | `dataCoverage` | Start and latest timestamp per dataset | Indexed history | | `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 Required. Send your key in the `X-API-Key` header or as `Authorization: Bearer `. A request without a valid key returns `401`. ## 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. - name: Builders description: >- Builder-wide feeds: every fill and order routed through one builder code, whatever the user. - name: Market History description: >- Per-market series sampled from our own node every 30 to 60 seconds, kept about 7 days: open interest, oracle prices, slippage, liquidity. - name: Staking description: Validator snapshots and network staking figures from our own node. - name: Liquidations description: Indexed liquidation events with cursor paging. - name: Coverage description: >- What the index holds: per-dataset start and latest timestamp in the region answering. paths: /info#allLedgerUpdates: post: tags: - Account History summary: Ledger events of all users description: >- Non-funding ledger events (deposits, withdrawals, transfers, vaults, staking, borrow/lend, ...) of every user on Hyperliquid, or of a list of wallets, in time order: the REST counterpart of the [`allLedgerUpdates` WebSocket channel](/live-data/ws-all-ledger-updates). Use it to catch up after a disconnect, or to read a past window. Same items as the WebSocket channel: `time`, `hash`, `users` (the one or two addresses involved, sorted; a transfer between two addresses is returned once) and `delta`, the event as Hyperliquid emits it. **Paging**: `limit` items per page, ascending time. The response headers `X-Has-More` and `X-Next-Cursor` tell whether a next page exists; pass `X-Next-Cursor` as `cursor` with the same `startTime` / `endTime` / `users` / `types`. Pages always end on a whole millisecond. Without `users`, a page covers at most one day of events: it can then hold fewer than `limit` items, or none, with `X-Has-More: true`. Keep following `X-Next-Cursor` until `X-Has-More` is `false`. **Coverage**: complete for every user from 27 September 2025. Before that date, only some addresses are covered. Served from the EU region whatever the client's location. **Filters**: `users` (up to 20,000 wallets) and `types` (`delta.type` values) combine with AND. Unknown fields are refused with `422` and the name of the field, so a typo never returns the unfiltered stream. operationId: allLedgerUpdates requestBody: required: true content: application/json: schema: type: object required: - type - startTime properties: type: type: string enum: - allLedgerUpdates startTime: type: integer description: Inclusive lower bound on `time`, epoch milliseconds endTime: type: integer description: >- Inclusive upper bound on `time`, epoch milliseconds. Default: now users: type: array items: type: string maxItems: 20000 description: >- Optional: only the events involving at least one of these wallets (0x-prefixed, case-insensitive), up to 20,000 types: type: array items: type: string maxItems: 50 description: >- Optional: only these `delta.type` values, e.g. `["deposit", "withdraw"]` limit: type: integer minimum: 1 maximum: 5000 default: 2000 description: Items per page cursor: type: string description: The `X-Next-Cursor` header of the previous page example: type: allLedgerUpdates startTime: 1793995200000 endTime: 1793998800000 types: - deposit - withdraw limit: 2000 responses: '200': description: Ledger events in time order content: application/json: schema: type: array items: type: object properties: time: type: integer hash: type: string users: type: array items: type: string delta: type: object properties: type: type: string example: - time: 1793998982519 hash: >- 0x1e2d3c4b5a69788796a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3 users: - '0x5c4d3e2f1a0b9c8d7e6f5a4b3c2d1e0f9a8b7c6d' delta: type: deposit usdc: '500.0' '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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.