vaultTransfer. It is sent to POST https://api.hyperliquid.xyz/exchange with a JSON body that includes the action, nonce, and signature. The action object requires vaultAddress, isDeposit, and usd; expiresAfter is optional.
This article uses the documented request shape from the Hyperliquid exchange-endpoint docs. It is not a live-account test.
Endpoint and signing
Use:
- Method:
POST - URL:
https://api.hyperliquid.xyz/exchange - Header:
Content-Type: application/json
Vaults and subaccounts do not have private keys. To perform actions on behalf of a subaccount or vault, the docs say signing should be done by the master account and the vault address should be supplied. For vaultTransfer, the vault address is inside the action object as action.vaultAddress. The Python SDK includes a basic_vault.py example that demonstrates vault actions.
The request body also includes:
nonce: a number, recommended to be the current timestamp in milliseconds.signature: an object generated by the signing process. The exchange-endpoint page does not expand the signature object fields in this section.expiresAfter: optional timestamp in milliseconds after which the action will be rejected. Actions canceled due to a staleexpiresAftervalue consume 5x the usual address-based rate limit. See Hyperliquid API expiresAfter: Action Deadline, Rejection, and 5x Rate-Limit Cost.
vaultTransfer request fields
| Field | Type | Required | Description |
|---|---|---|---|
action.type | String | Yes | Use "vaultTransfer". |
action.vaultAddress | String | Yes | Vault address in 42-character hexadecimal format. |
action.isDeposit | Boolean | Yes | Direction of the transfer; the documented action is for depositing into or withdrawing from a vault. |
action.usd | Number | Yes | Amount field documented as usd. |
nonce | Number | Yes | Recommended current timestamp in milliseconds. |
signature | Object | Yes | SDK-generated signature object. |
expiresAfter | Number | No | Optional deadline in milliseconds. |
action object has this documented shape:
{
"type": "vaultTransfer",
"vaultAddress": "0x0000000000000000000000000000000000000000",
"isDeposit": true,
"usd": 100
}
Wrap that object in the request body with nonce and signature. The usd field is documented as a number, unlike several other transfer actions that use string amounts.
Expected response
The documented successful response is:
{
"status": "ok",
"response": {
"type": "default"
}
}
Like what you're reading? Try it yourself โ this link supports ChartedTrader at no cost to you.
Sign up on Hyperliquid โ
Difference from hip3LiquidatorTransfer
hip3LiquidatorTransfer is a separate action for adding or removing funds from an HIP-3 DEX's backstop liquidator address. It uses the same POST https://api.hyperliquid.xyz/exchange endpoint and also supports nonce, signature, and optional expiresAfter.
| Aspect | vaultTransfer | hip3LiquidatorTransfer |
|---|---|---|
| Action type | "vaultTransfer" | "hip3LiquidatorTransfer" |
| Target field | vaultAddress: 42-character hexadecimal vault address | dex: string, e.g. "xyz" |
| Amount field | usd: number | ntl: integer in units of 1e-6 quote tokens |
| Amount constraint | Not specified in this source | Must be a multiple of 1000 quote tokens, i.e. ntl % 1000000000 == 0 |
| Direction field | isDeposit: boolean | isDeposit: boolean |
| Optional deadline | expiresAfter supported | expiresAfter supported |
| Documented response | {"status": "ok", "response": {"type": "default"}} | {"status": "ok", "response": {"type": "default"}} |
| Withdrawal scope | Documented as adding or removing funds from a vault | Only principal amount is withdrawable, not PnL |
hip3LiquidatorTransfer action object has this documented shape:
{
"type": "hip3LiquidatorTransfer",
"dex": "xyz",
"ntl": 1000000000,
"isDeposit": false
}
In that example, 1000000000 represents 1,000 quote tokens because ntl uses 1e-6 quote-token units.
CTA
The Hyperliquid link below is a referral link; supa.is may earn a commission or referral reward. Sign up on Hyperliquid
Continue with Hyperliquid
Browse the Hyperliquid guide hub for the complete user journey.
Official reference: Hyperliquid documentation.