- For programmatic transfers that do not require quorum, see Crypto Transfers.
- For AML questionnaire field details, see the AML questionnaire guide.
destination.type values:
WALLETADDRESSTRUSTED_DESTINATIONVAULT(not recommended — reduced precision)
Asset support by destination type
| Destination type | Digital assets | USD |
|---|---|---|
| Wallet | Supported | Not supported |
| Trusted destination | Supported | Not supported |
| Non-allowlisted address | Supported | Not supported |
| Vault (not recommended) | Supported | Not supported |
Withdrawal examples
API endpoints
| Endpoint | Description |
|---|---|
| Create a withdrawal | Initiates a withdrawal from an Anchorage Digital wallet to an external destination. Requires quorum approval to process. No queuing. |
| List transactions | Returns metadata across all transactions in vaults permissioned to the API key. start_date and end_date format: YYYY-MM-DD. |
| Get transaction by ID | Returns metadata for a specific transaction including assets, fees, status, destination addresses, and transaction type. |
Status values
| Status | Description |
|---|---|
SUCCESS | Transaction succeeded. |
NEEDS APPROVAL | Transaction initiated, awaiting quorum member approval. |
INPROGRESS | Transaction currently in progress. |
FAILURE | Transaction failed. |
REJECTED | Transaction was rejected. |
EXPIRED | Transaction expired. |
Withdrawals and transactions
A withdrawal is a type of transaction at Anchorage Digital (transfers are another type). Each has its own transaction ID plus a type-specific ID:withdrawalIdtransferId
Quorum approval workflow
- Initiate a withdrawal request via the create withdrawal endpoint.
- A mobile-based quorum approval is triggered — the vault policy must be satisfied by approvals from designated users on iOS.
- Once quorum is reached, Anchorage Digital performs a risk review and policy check.
- If requirements are met, the transaction is broadcast to the network.
- Network fees apply; processing time depends on blockchain speed and congestion.
- Ensure the wallet holds sufficient funds to cover the withdrawal amount plus network fees.
- Status is reflected in API responses once the transaction completes.
Network fees
For withdrawals via web dashboard and API, network fees are added to the withdrawal amount and paid in the native layer-1 asset (e.g., ETH for ERC-20 withdrawals). The only case where the fee is deducted from the withdrawal amount is when withdrawing the full wallet balance via the web dashboard.UTXO asset processing
Anchorage Digital abstracts UTXO-based processing by exposing a single wallet-level address (the most recently created address in the wallet) as the representative address for all pooled UTXOs. When executing a transfer or withdrawal:- UTXOs are selected randomly across addresses within the wallet to preserve privacy.
- If multiple deposits have been made to the same address, the wallet may hold multiple UTXOs at that address — the exact selection used for a transaction is random.
- Balances of sub-UTXOs are visible on-chain via a block explorer.
Troubleshooting
Request-level failures:- An ongoing withdrawal already exists. Withdrawal requests are not queued like transfers.
- The specified asset does not exist — verify the symbol and vault.
- Amount exceeds available funds (including network fees).
- Destination address is invalid.
- API key lacks withdrawal permissions for the vault.
- Withdrawal using a wallet ID or address will fail — specify at the vault level using a vault ID.
- Insufficient funds to cover network fees at broadcast time.
- Blockchain-level failure.

