Withdraw

HyperliquidPolymarket

Requests an asynchronous withdrawal to the destination wallet. Hyperliquid spot assets are sent on HyperCore. Canonical Polygon pUSD is sent on Polygon when the deployment permits that route for the signing user.

Endpoint

POST /exchange

Request Body

Parameter	Type	Description
`action`*	object	Withdrawal payload
`nonce`*	number	Timestamp in milliseconds for replay protection, e.g., `1701234567890`
`signature`*	object	Withdrawal signature

action

Field	Type	Description
`type`*	string	Must be `"withdraw"`
`notionalChain`*	string	Notional chain: `"Mainnet"` or `"Testnet"`
`signatureChainId`*	string	EIP-712 chain ID (hex string), e.g., `"0xa4b1"`
`destination`*	string	Destination wallet address (normalized to lowercase), e.g., `"0x1234567890abcdef..."`
`token`*	string	Unprefixed AssetId: 8 hex characters for Hyperliquid spot tokens, 46 for Polygon pUSD
`amount`*	string	Amount to withdraw, e.g., `"1000.0"`
`source`*	string	`"balance"`, or `"segregated"` for funds held after a rejected deposit
`time`*	number	Unix timestamp in milliseconds; must match the request-envelope `nonce`

signature

Field	Type	Description
`r`*	string	First 32 bytes of signature (hex string), e.g., `"0x1234..."`
`s`*	string	Second 32 bytes of signature (hex string), e.g., `"0x5678..."`
`v`*	number	Recovery ID (27 or 28)

Supported Assets and Amounts

Use 00012710 for HyperCore USDC or 800101c011a7e12a19f7b1f670d46f03b03f3342e82dfb for Polygon pUSD. Perpetual markets, spot-pair IDs, outcome shares, and other EVM assets are not withdrawal assets. Polygon pUSD withdrawals are disabled unless the deployment explicitly enables admission for the user. They require a positive amount representable with at most six decimals and must satisfy the deployment’s minimum amount, batch limit, and destination rules. Hyperliquid assets use their transfer precision and can incur a destination-account activation fee.

Signing

The account owner must sign directly. With a connected Viem walletClient:

import { buildNotionalWithdrawalTypedData, buildWithdrawalPayload } from "@notional/common";

const chainId = 42161; // 421614 for testnet
const typedData = buildNotionalWithdrawalTypedData(
  destination,
  "00012710",
  "100",
  "balance",
  "mainnet", // "testnet" for testnet
  chainId,
);
const signature = await walletClient.signTypedData({
  ...typedData,
  account: walletClient.account!,
});
const request = buildWithdrawalPayload(signature, typedData.message, chainId);

The domain is NotionalSignTransaction, version 1, with the deployment’s signature chain ID and the zero address as verifyingContract. The primary type is NotionalTransaction:Withdraw. The signed message contains notionalChain, destination, token, amount, source, and time. signatureChainId selects the domain; it is not an additional message field.

Response

200: Pending
400: Agent Wallet

{
  "success": true,
  "transactionId": "0x1a2b3c4d5e6f7890...",
  "status": "pending"
}

{
  "error": "Agent wallets cannot initiate withdrawals. Please sign with your user account.",
  "code": "VALIDATION_FAILED",
  "timestamp": 1785254400000
}

Response Fields

Field	Type	Description
`success`	boolean	`true` when the withdrawal was accepted and recorded
`transactionId`	string	Deterministic transaction ID, e.g., `"0x1a2b3c..."`
`status`	string	`"pending"` on acceptance; execution happens asynchronously

Poll Pending Withdrawals and refresh balances to follow execution. An exact retry can return the saved acceptance result; a previously rejected withdrawal can return success: false, status: "failed", and error. Inspect the body as well as the HTTP status.

Start Here

Info

Analytics

Exchange

WebSocket

Endpoint

Request Body

action

signature

Supported Assets and Amounts

Signing

Response

Response Fields

​Endpoint

​Request Body

​action

​signature

​Supported Assets and Amounts

​Signing

​Response

​Response Fields

Endpoint

Request Body

action

signature

Supported Assets and Amounts

Signing

Response

Response Fields