This endpoint requires signature authentication. See our comprehensive Authentication via Signatures guide for implementation details.
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 USD send action object containing:type
(string) — Must be"usdSend"
hyperliquidChain
(string) —"Mainnet"
for mainnet,"Testnet"
for testnetsignatureChainId
(string) — Chain ID used for signing in hex format (e.g.,"0xa4b1"
for Arbitrum)destination
(string) — Recipient address in 42-character hexadecimal formatamount
(string) — Amount of USDC to send (e.g.,"100.5"
for 100.5 USDC)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
Signature format
This endpoint uses EIP-712 typed data signing with a human-readable format:Returns
Returns an object with transfer status:status
—"ok"
if successfulresponse
— Contains transfer details:type
—"default"
Example request
Response example
Important notes
- Internal transfers only — This doesn’t interact with external bridges
- Instant settlement — Transfers are immediate within Hyperliquid
- No gas fees — Internal transfers don’t require gas
- Decimal precision — Amount is a string to preserve decimal precision
Use cases
- P2P transfers — Send USDC directly to other users
- Account funding — Transfer between your own accounts
- Payment processing — Programmatic USDC payments
- Vault operations — Transfer funds to/from vault addresses
The
time
parameter in the action must exactly match the nonce
parameter. This ensures signature uniqueness and prevents replay attacks.Always verify the destination address. Transfers are irreversible once confirmed on the Hyperliquid chain.
Body
application/json