> ## 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. # Historical orders > The wallet's most recent orders with their latest status, in Hyperliquid's shape. - Without `lookbackDays`, returns the `limit` most recent orders whatever their age, latest status first, as Hyperliquid does. `lookbackDays` restricts the result to statuses from the last N days. - Prices and sizes use Hyperliquid's format, always with at least one decimal (`"93604.0"`, `"0.0"`). `cloid` and `tif` are always present, `null` when absent. `children` is always `[]`: TP/SL children are not indexed. - Beyond the `limit` most recent orders, an older order whose status changes today is not returned. ## OpenAPI ````yaml /live-data/openapi-rest.json post /info#historicalOrders 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#historicalOrders: post: tags: - Account History summary: Historical orders description: >- The wallet's most recent orders with their latest status, in Hyperliquid's shape. - Without `lookbackDays`, returns the `limit` most recent orders whatever their age, latest status first, as Hyperliquid does. `lookbackDays` restricts the result to statuses from the last N days. - Prices and sizes use Hyperliquid's format, always with at least one decimal (`"93604.0"`, `"0.0"`). `cloid` and `tif` are always present, `null` when absent. `children` is always `[]`: TP/SL children are not indexed. - Beyond the `limit` most recent orders, an older order whose status changes today is not returned. operationId: historicalOrders requestBody: required: true content: application/json: schema: type: object required: - type - user properties: type: type: string enum: - historicalOrders user: type: string description: Wallet address (0x-prefixed, case-insensitive) limit: type: integer minimum: 1 maximum: 5000 default: 2000 lookbackDays: type: integer minimum: 1 maximum: 365 description: Optional. Only statuses from the last N days example: type: historicalOrders user: '0x010461c14e146ac35fe42271bdc1134ee31c703a' limit: 1 responses: '200': description: Orders with their latest status, latest first content: application/json: schema: type: array items: type: object properties: order: type: object properties: coin: type: string side: type: string enum: - A - B limitPx: type: string sz: type: string description: Remaining size origSz: type: string description: Original size oid: type: integer orderType: type: string tif: type: string nullable: true reduceOnly: type: boolean isTrigger: type: boolean triggerPx: type: string triggerCondition: type: string isPositionTpsl: type: boolean timestamp: type: integer description: Order placement time, ms cloid: type: string nullable: true children: type: array items: type: object status: type: string description: >- Latest status, e.g. `filled`, `canceled`, `open`, `selfTradeCanceled` statusTimestamp: type: integer description: Time of the latest status, ms example: - order: coin: XPL side: A limitPx: '0.11161' sz: '216095.0' origSz: '248829.0' oid: 557019688085 orderType: Limit tif: Gtc reduceOnly: true isTrigger: false triggerPx: '0.0' triggerCondition: N/A isPositionTpsl: false timestamp: 1790395641208 cloid: null children: [] status: selfTradeCanceled statusTimestamp: 1790395662053 '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. ````