# Femtos | Wallet order history | API reference

> One wallet's orders that left the book, newest first: how (filled, canceled, rejected) and why, the size filled and its average price. GET /v1/hypercore/wallet/{address}/orders/history on HyperCore: parameters, response fields and a live call per layer.

- Base URL: `https://api.femtos.xyz/v1` (REST) · `wss://api.femtos.xyz/v1/ws` (WebSocket) · MCP: `https://api.femtos.xyz/mcp`
- Auth: `Authorization: Bearer $FEMTOS_KEY`. Free key: https://dashboard.femtos.xyz/signup (browser), or with
  no browser: `GET https://femtos.xyz/accounts/agent/challenge`, solve its proof of work, then `POST https://femtos.xyz/accounts/agent/signup`
  (https://femtos.xyz/agents.md#agent-onboarding)
- Decimals are exact strings, times Unix milliseconds, addresses lowercase `0x`
- Whole API in one file: https://femtos.xyz/agents.md · OpenAPI: https://api.femtos.xyz/v1/openapi.json · Index: https://femtos.xyz/llms.txt
- Page with live calls: https://femtos.xyz/reference/wallet-order-history

## Wallet order history — GET `/v1/hypercore/wallet/{address}/orders/history`

One wallet's orders that left the book, newest first: how (filled, canceled, rejected) and why, the size filled and its average price.

Layers: HyperCore. Not on Elysium or HyperEVM: orders, fills and funding payments are HyperCore's: on the EVM layers an address swaps and holds tokens, see its trades, ERC-20 transfers and balances.
Page with live calls: https://femtos.xyz/reference/wallet-order-history?layer=hypercore

| Param | In | Example or values | Meaning |
|---|---|---|---|
| `address` | path | `0x5a69a60ca8a4d189855b33bd9f1bbe71095c1039` | 0x address, or a named wallet's handle <entityId>.<hex> |
| `coin` | query | (optional) | Only this market (BTC, xyz:TSLA, @107) |
| `outcome` | query | `(empty)`, `filled`, `canceled`, `rejected` | Only the orders that left the book this way |
| `from` | query | (optional) | Window start (Unix ms): in the last-days part, the orders that left the book since then (whenever placed); in the older part, the orders placed since then (default and at most 30 days back) |
| `limit` | query | `20` | Orders |

```bash
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/hypercore/wallet/0x5a69a60ca8a4d189855b33bd9f1bbe71095c1039/orders/history?limit=20"
```

| Field | Type | Meaning |
|---|---|---|
| `orders[]` | object | Newest first, in two parts. The last 1 to 2 days (orders that left the book since `statusSince`, 00:00 UTC yesterday): by exit time (`statusTime`). Older orders: by placement day (`placedAt`), then order id, not by exit time, down to `from`: {oid, coin, dex, side, kind, exec, orderType, limitPx, triggerPx, triggerCondition, sz, origSz, …} |
| `orders[].outcome` | filled \| canceled \| rejected | How it left the book: filled, canceled (any …Canceled), rejected (any …Rejected) |
| `orders[].status` | string | Hyperliquid's last status, the reason: filled, canceled, marginCanceled, reduceOnlyCanceled, siblingFilledCanceled, iocCancelRejected, badAloPxRejected… |
| `orders[].filledSz` | decimal | Size filled: origSz − sz (what its fills add up to) |
| `orders[].avgPx` | decimal \| null | Average fill price: Σ px × sz ÷ Σ sz of the order's fills; null when nothing filled, or its fills are not in our table yet |
| `orders[].statusTime` | ms | Time of the last status: when it left the book |
| `statusSince` | ms | Where the two parts meet (00:00 UTC yesterday): orders that left the book since then come first, by statusTime. A later midnight, up to the next one, while our status events are not available: then every order comes by placement day |
| `from` | ms | Window start read (from, at most 30 days back): the oldest placement the older part serves; the last-days part lists the orders that left the book since the later of from and statusSince |
| `entity` | object | Named wallet (labels), when known |
| `next_cursor` | string \| null | Opaque cursor of the next page: pass it as `cursor`, unchanged. null on the last page |
| `billing` | medium | medium |

Next page: `cursor` = the `next_cursor` of the previous answer (https://femtos.xyz/agents.md#pagination).

## Related (Bridges & wallets)

- [Cross-layer wallet](https://femtos.xyz/reference/wallet.md) `GET /v1/wallet/{address}`: One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events. (Elysium, HyperCore, HyperEVM)
- [Wallet stream](https://femtos.xyz/reference/ws/wallet.md) `WS wallet`: Every event of the three layers touching one address. (Elysium, HyperCore, HyperEVM)
- [Wallet list stream](https://femtos.xyz/reference/ws/wallets.md) `WS wallets`: Every event of the three layers touching any of up to 100 addresses, in one subscription, each event tagged with its address. (Elysium, HyperCore, HyperEVM)
- [HyperCore account](https://femtos.xyz/reference/hypercore-account.md) `GET /v1/hypercore/wallet/{address}`: One address's HyperCore account: perp value and margin, positions, spot balances. (HyperCore)
- [Wallet open orders](https://femtos.xyz/reference/wallet-orders.md) `GET /v1/hypercore/wallet/{address}/orders`: One wallet's open orders: resting limit orders and trigger orders, on the main dex and every HIP-3 dex. (HyperCore)
- [Wallet fills](https://femtos.xyz/reference/wallet-fills.md) `GET /v1/hypercore/wallet/{address}/fills`: One wallet's HyperCore fills, newest first, with closed PnL, fees and the position before each. (HyperCore)
- [Wallet fills per bar](https://femtos.xyz/reference/wallet-fill-bars.md) `GET /v1/hypercore/wallet/{address}/fills/bars`: One wallet's fills on one market summed per bar: buys and sells with their average price, and the position after each bar. (HyperCore)
- [Wallet funding](https://femtos.xyz/reference/wallet-funding.md) `GET /v1/hypercore/wallet/{address}/funding`: One wallet's funding payments, newest first: paid or received per perp and hour, with the position and the rate. (HyperCore)
- [Swaps by wallet](https://femtos.xyz/reference/wallet-trades.md) `GET /v1/trades`: Every swap a wallet sent (or a pool’s, a token’s), newest first, filterable by token, side, size and time. (Elysium, HyperEVM)
- [Transfers by wallet](https://femtos.xyz/reference/wallet-transfers.md) `GET /v1/transfers`: ERC-20 transfers sent and received by a wallet, newest first, filterable by token, direction, size and time. (Elysium, HyperEVM)
- [Wallet PnL](https://femtos.xyz/reference/wallet-pnl.md) `GET /v1/wallet/{address}/pnl`: Any wallet on HyperEVM: per token balance, cost basis, realized and unrealized PnL, with 1d / 7d / 30d / all totals and win rate. (Elysium, HyperEVM)
- [Portfolio value history](https://femtos.xyz/reference/wallet-value.md) `GET /v1/wallet/{address}/value`: Any address on HyperEVM: its total USD value per 5 min (1d), hour (7d) or day (30d, all). (Elysium, HyperEVM)
- [Wallet PnL curve](https://femtos.xyz/reference/hypercore-wallet-pnl.md) `GET /v1/hypercore/wallet/{address}/pnl`: One HyperCore wallet's PnL per hour or day: realized, fees, funding, net and cumulative, and its account value. (HyperCore)
- [Wallet PnL stream](https://femtos.xyz/reference/ws/pnl.md) `WS pnl`: A wallet's positions and PnL on HyperEVM (GET /v1/wallet/{address}/pnl), pushed on subscribe, then the positions each block changes. (Elysium, HyperEVM)
- [Was I sandwiched?](https://femtos.xyz/reference/wallet-mev.md) `GET /v1/wallet/{address}/mev`: Every sandwich of a wallet’s swaps on Elysium: the bot, its two transactions, what the wallet lost. Free, no key. (Elysium)
- [Ledger stream](https://femtos.xyz/reference/ws/ledger.md) `WS hc.ledger`: Deposits, withdrawals, transfers and other non-trade balance moves. (HyperCore)
- [Bridge movements](https://femtos.xyz/reference/bridge.md) `GET /v1/bridges`: Matched HyperCore ↔ HyperEVM transfers with 24 h stats. (Elysium, HyperCore, HyperEVM)
- [Bridge stream](https://femtos.xyz/reference/ws/bridge.md) `WS elysium.bridge | bridge.transfers`: Each HyperCore ↔ HyperEVM transfer, initiated then completed. (Elysium, HyperCore, HyperEVM)
- [Bridge movements stream](https://femtos.xyz/reference/ws/bridges.md) `WS bridges.recent`: The GET /v1/bridges answer (movements newest first, 24 h stats), pushed on subscribe, then when a movement of the route changes state. (Elysium, HyperCore, HyperEVM)
- [Bridge coverage](https://femtos.xyz/reference/bridge-coverage.md) `GET /v1/bridges/coverage`: Every HyperCore ↔ HyperEVM leg since our data starts, paired with its other leg: matched share per direction and token, why the others are not, latency. (HyperCore, HyperEVM)

Every page: https://femtos.xyz/reference.md