Skip to main content
POST
/
exchange
Transfer spot token
curl --request POST \
  --url https://api.hyperliquid.xyz/exchange \
  --header 'Content-Type: application/json' \
  --data '
{
  "action": {
    "type": "spotSend",
    "hyperliquidChain": "Mainnet",
    "signatureChainId": "0xa4b1",
    "destination": "0x1234567890123456789012345678901234567890",
    "token": "PURR",
    "amount": "1000.0",
    "time": 1705234567890
  },
  "nonce": 1705234567890,
  "signature": {
    "r": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
    "s": "0xfedcba0987654321fedcba0987654321fedcba0987654321fedcba0987654321",
    "v": 27
  },
  "vaultAddress": null
}
'
{
  "status": "ok",
  "response": {
    "type": "spotSend",
    "data": {
      "status": "success"
    }
  }
}
This endpoint requires signature authentication. See our comprehensive Authentication via Signatures guide for implementation details.
Transfers spot tokens directly to another address on the Hyperliquid chain. This is an internal transfer that doesn’t interact with the EVM bridge and uses a human-readable signature format for wallet interfaces.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

​
Required parameters

  • action (object, required) — The spot send action object containing:
    • type (string) — Must be "spotSend"
    • hyperliquidChain (string) — "Mainnet" for mainnet, "Testnet" for testnet
    • signatureChainId (string) — Chain ID used for signing in hex format (e.g., "0xa4b1" for Arbitrum)
    • destination (string) — Recipient address in 42-character hexadecimal format
    • token (string) — Token identifier in format "TOKEN_NAME:TOKEN_ID" (e.g., "PURR:0xc1fb593aeffbeb02f85e0308e9956a90")
    • amount (string) — Amount of tokens to send (e.g., "100.5")
    • time (number) — Current timestamp in milliseconds (must match nonce)
  • nonce (number, required) — Current timestamp in milliseconds (must match action.time)
  • signature (object, required) — EIP-712 signature of the action

​
Token format

The token parameter must include both the token name and its ID:
  • Format: "TOKEN_NAME:TOKEN_ID"
  • Example: "PURR:0xc1fb593aeffbeb02f85e0308e9956a90"
  • The token ID can be found in the spot metadata response

​
Signature format

This endpoint uses EIP-712 typed data signing with a human-readable format: 
{
  "types": {
    "HyperliquidTransaction:SpotSend": [
      {"name": "hyperliquidChain", "type": "string"},
      {"name": "destination", "type": "string"},
      {"name": "token", "type": "string"},
      {"name": "amount", "type": "string"},
      {"name": "time", "type": "uint64"}
    ]
  },
  "primaryType": "HyperliquidTransaction:SpotSend",
  "domain": {
    "name": "HyperliquidSignTransaction",
    "version": "1",
    "chainId": 42161,
    "verifyingContract": "0x0000000000000000000000000000000000000000"
  },
  "message": {
    "hyperliquidChain": "Mainnet",
    "destination": "0x...",
    "token": "PURR:0xc1fb593aeffbeb02f85e0308e9956a90",
    "amount": "100.0",
    "time": 1234567890123
  }
}

​
Returns

Returns an object with transfer status:
  • status — "ok" if successful
  • response — Contains transfer details:
    • type — "default"

​
Example request

curl -X POST https://api.hyperliquid.xyz/exchange \
  -H "Content-Type: application/json" \
  -d '{
    "action": {
      "type": "spotSend",
      "hyperliquidChain": "Mainnet",
      "signatureChainId": "0xa4b1",
      "destination": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb0",
      "token": "PURR:0xc1fb593aeffbeb02f85e0308e9956a90",
      "amount": "100.0",
      "time": 1234567890123
    },
    "nonce": 1234567890123,
    "signature": {...}
  }'

​
Response example

{
  "status": "ok",
  "response": {
    "type": "default"
  }
}

​
Important notes

  • Spot tokens only — This endpoint is for spot tokens, not perpetual positions
  • Token balance required — Must have sufficient token balance
  • Internal transfers only — Doesn’t interact with external bridges
  • Instant settlement — Transfers are immediate within Hyperliquid

​
Use cases

  • Token distribution — Send tokens to multiple recipients
  • P2P transfers — Direct token transfers between users
  • Vault operations — Move tokens to/from vault addresses
  • Airdrops — Programmatic token distribution
You need to know the token ID for the transfer. This can be obtained from the spot metadata endpoint or by checking existing token balances.
Always verify both the destination address and token ID. Transfers are irreversible once confirmed on the Hyperliquid chain.

Body

application/json
​
action
object
required
​
nonce
integer
required

Current timestamp in milliseconds

​
signature
object
required

EIP-712 signature of the action with r, s, v components

​
vaultAddress
string

Address when trading on behalf of a vault or subaccount (optional)

Response

200 - application/json

Spot token transfer result

​
status
string

Request status

​
response
object
Last modified on October 19, 2025