Prerequisites
- An API token sent as the
x-auth-tokenheader - Sufficient
available_balancein the withdrawal currency - The destination address registered in the address book, with Travel Rule
meta_datawhere required
Step 1: Estimate the network fee
Fees track network congestion, so fetch a fresh estimate right before the user confirms — see Supported assets and networks for the full response:network_status is MAINTENANCE, and check the amount against the network’s min_withdraw_amount and withdraw_precision.
Step 2: Create the withdrawal
Call Create Withdraw with an idempotency key:
Response:
actual_amount is what arrives at the destination after fees. The fee actually charged can differ slightly from the Step 1 estimate.
Step 3: Track the withdrawal
Status updates arrive on the Withdrawal webhook:
You can also poll Retrieve Withdraw with either the long or short order ID, or reconcile in bulk with List Withdraws. Completed orders include the on-chain transaction hash (
txid) and completed_time.
Related
- Create Withdraw API
- Withdrawal webhook
- Address book
- Travel Rule compliance
- Supported assets and networks — fee estimation and limits

