/wallets/{address}/ledger

GET https://data.vike.io/v1/hyperliquid/wallets/{address}/ledger

Deposits, withdrawals, transfers and vault events. Keyset on (ts, hash).

cURL

# the newest ledger events of one wallet
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?limit=3" \
  -H "X-API-KEY: $VIKE_API_KEY"

# next page of the call just above: NEXT is its nextCursor, passed back verbatim
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?limit=3&cursor=$NEXT" \
  -H "X-API-KEY: $VIKE_API_KEY"

# capital in: deposits only
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?event_type=deposit&limit=100" \
  -H "X-API-KEY: $VIKE_API_KEY"

# capital out: withdrawals only
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?event_type=withdraw&limit=100" \
  -H "X-API-KEY: $VIKE_API_KEY"

# vault activity
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?event_type=vaultDeposit&limit=100" \
  -H "X-API-KEY: $VIKE_API_KEY"

# events inside a pinned window
curl -s "https://data.vike.io/v1/hyperliquid/wallets/0x25773676902085225ae5751075e4161369334897/ledger?start=2026-09-01T00:00:00Z&end=2026-09-02T00:00:00Z&limit=5000" \
  -H "X-API-KEY: $VIKE_API_KEY"

addresspathrequired

The wallet

event_typequeryoptional

One of accountClassTransfer, borrowLend, deposit, internalTransfer, rewardsClaim, send, spotTransfer, subAccountTransfer, vaultCreate, vaultDeposit, vaultDistribution, vaultLeaderCommission, vaultWithdraw, withdraw. Validated against this fixed set

startqueryoptional

ISO-8601 UTC bounds

endqueryoptional

ISO-8601 UTC bounds

limitqueryoptional

Default 100, max 5000

cursorqueryoptional

Keyset cursor

Example response

{
  "wallet": "0x25773676902085225ae5751075e4161369334897",
  "items": [
    {
      "ts": "2026-09-03T00:31:21.150000+00:00",
      "event_type": "send",
      "amount_usd": -10000.0,
      "fee": 0.0,
      "token": "USDC",
      "counterparty": null,
      "hash": "0x1648cc076d05cb6d17c204438ee76502036f00ed0808ea3fba11775a2c09a557"
    },
    {
      "ts": "2026-09-03T00:31:21.015000+00:00",
      "event_type": "send",
      "amount_usd": -10000.0,
      "fee": 0.0,
      "token": "USDC",
      "counterparty": null,
      "hash": "0xaec6e68724b1831cb04004438ee76302012c006cbfb4a1ee528f91d9e3b55d07"
    },
    {
      "ts": "2026-09-03T00:31:20.817000+00:00",
      "event_type": "send",
      "amount_usd": -10000.0,
      "fee": 0.0,
      "token": "USDC",
      "counterparty": null,
      "hash": "0x5bc25cde8ff2319b5d3c04438ee76002034f00c42af5506dff8b08314ef60b85"
    }
  ],
  "nextCursor": "eyJoIjoiMHg1YmMyNWNkZThmZjIzMTliNWQzYzA0NDM4ZWU3NjAwMjAzNGYwMGM0MmFmNTUwNmRmZjhiMDgzMTRlZjYwYjg1IiwidCI6IjIwMjYtMDktMDMgMDA6MzE6MjAuODE3In0"
}

event_type is validated against a fixed set rather than passed through, because an unknown value would return an empty list indistinguishable from "this wallet never did that". The accepted set is: deposit, withdraw, send, spotTransfer, internalTransfer, subAccountTransfer, accountClassTransfer, vaultDeposit, vaultWithdraw, vaultCreate, vaultDistribution, vaultLeaderCommission, borrowLend, rewardsClaim.

send is recorded one-sided

send is recorded one-sided — the outflow is seen while the matching inflow is not. That is the same defect the flow_unbalanced flag on /leaderboard/flow-adjusted reports.