Hyperliquid Get Transfer History
Get non-funding ledger updates for a Hyperliquid account: deposits, withdrawals, USD sends, vault operations, liquidations, spot transfers, and rewards claims. Enriches send-type entries with directional labels (Received/Sent). Ideal for: transfer tracking, deposit verification, wallet activity monitoring.
Catalog action Hyperliquid
Get non-funding ledger updates for a Hyperliquid account: deposits, withdrawals, USD sends, vault operations, liquidations, spot transfers, and rewards claims. Enriches send-type entries with directional labels (Received/Sent). Ideal for: transfer tracking, deposit verification, wallet activity monitoring.
At a Glance
| Field | Value |
|---|---|
| Action ID | hyperliquid-get-transfer-history |
| Category | Hyperliquid |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | hyperliquid, perps, transfer, history, deposit, withdraw |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | No | Hyperliquid account address (0x...) to query. When omitted the connected wallet address is used. |
startTime | number | No | Unix timestamp in milliseconds. Only return transfers after this time. Defaults to 30 days ago. |
endTime | number | No | Unix timestamp in milliseconds. Upper bound for transfers. Omit for now. |
limit | number | No | Maximum number of entries to return after sorting (newest first). Defaults to 500, hard cap 2000. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
transfers | array | Yes | Ledger entries sorted by time (newest first), capped by limit |
Examples
json{ "type": "hyperliquid-get-transfer-history", "payload": { "address": "0x0000000000000000000000000000000000000000", "startTime": 1, "endTime": 1, "limit": 1 }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/hyperliquid-get-transfer-history/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "address": "0x0000000000000000000000000000000000000000", "startTime": 1, "endTime": 1, "limit": 1 }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.