Skip to main content
Withdrawals require quorum approval; transfers do not. Transfers are also more configurable — specifically in how network fees are charged — and allow you to queue multiple transfers from the same wallet simultaneously, assuming sufficient funds.See the Transfers vs. withdrawals guide and the Transactions section of the API reference for more information.
All external withdrawal requests made via API and the iOS app go through quorum approval and Anchorage Digital risk review. You can add “trusted destinations” and notify your client experience manager to ensure all transfers to non-approved destinations are rejected.
To complete sandbox onboarding, you must complete the KYC form sent to you. If you entered sensitive information you’d like redacted, contact accountexecutive@anchorage.com.In production, all onboarded users undergo full KYC to access the Anchorage Digital iOS app and web dashboard.
Anchorage Digital reviews and approves onboarding video submissions. If your account has not been approved within an hour, contact your Anchorage Digital point of contact via email or Slack.
Anchorage Digital supports iOS devices only — iPhones and iPads — due to the secure enclave within these devices. Without an iPhone, you cannot access the sandbox app, web dashboard, or member quorum. You can still call the APIs using keys created and shared during onboarding.Device security is critical for safeguarding accounts and signing on-chain transactions. If other devices release similar functionality, Anchorage Digital will re-evaluate support at that time.Supported iOS devices:
  • iPhone 8, 8 Plus, X, XS, XS Max, XR, 11, 11 Pro, 11 Pro Max, SE (2nd gen), 12, 12 Pro, 12 mini, 13, 13 Pro, 13 mini
  • iPad (5th gen and later), mini 4, mini (5th and 6th gen), Air 2, Air (3rd and 4th gen), Pro (all versions)
To gain access to the TestFlight app, the new member should contact your main Anchorage Digital point of contact. Once the app is installed, an admin must generate a QR code:Admin steps:
  1. Tap the gear icon ⚙️ at the lower right of the app, then tap Users.
  2. Tap the add icon ➕ at the top right.
  3. Follow the prompts to set policies and vaults.
  4. Share the unique QR code with the new user (screenshot and email if not in the same location).
New user steps:
  1. Scan the QR code in the Anchorage Digital iOS app.
  2. Input preliminary KYC information including basic personal data, voice, and biometric training.
  3. Wait for quorum approval.
The initiating admin will be prompted for biometric approval. A second approver is then required. Finally, Anchorage Digital compliance reviews the new user’s PII and completes due diligence before approving.
EnvironmentURL
Productionhttps://api.anchorage.com/v2
Sandboxhttps://api.anchorage-staging.com/v2
See the Request Signing page for full instructions and reference client scripts.
The default is to require a signature; read-only endpoints are the exception. Signatures are optional unless explicitly required but are encouraged for all requests — if provided, they will be verified.Endpoints that require signing will specify the Api-Signature and Api-Timestamp headers as additional parameters and require an Ed25519 signature alongside the API key.
Yes. Sandbox assets run on their own testnets. For example, sandbox uses BTC_T (testnet) while production uses BTC (mainnet).
Inform your client experience manager at Anchorage Digital immediately. The device will be marked as “lost” and deactivated. When you get a new device, your team can help you recover access. Contact Anchorage Digital for support.
Yes. Revoke a key via the web dashboard or by emailing accountexecutive@anchorage.com.
Revoked keys cannot be reinstated. A new key must be created. You do not need quorum approval or risk review to create a new key using an existing permission group.
To revoke: go to the API section of the web dashboard, select the three-dot icon next to the key, and select Revoke.Only admin users with the correct access credentials can revoke API keys. Any user (admin, member, view-only) can view permission group details and past keys, but no user can see the actual hexadecimal key value.
A quorum authenticates organizational intent — ensuring that initiated transactions align with your organization’s governing structure. Quorums are required both internally at Anchorage Digital and for client operations.
New clients must onboard a minimum of three admins. All initial users are admins. From there, new users, vaults, and policies are established through an admin quorum.
Yes. All transactions require a valid quorum of unique, unforgeable cryptographic signatures from multiple organization members. Quorums are configurable per vault as any M-of-N.For example, a company with five employees authorized to transfer funds might require three of five approvals per transaction. You can also specify a required user for any quorum and use different quorum settings per vault within an account.

​
Network & gas fees

The wallet must hold sufficient balance to cover transaction fees — an estimated balance for withdrawals, staking, and smart contract operations, and a fixed fee threshold for API-initiated transfers.
Gas fees are calculated by multiplying the gas limit (maximum gas willing to spend) by the gas price (ETH per gas unit). They are paid in ETH and used to protect the network and incentivize validators.
As of January 24, 2024, the threshold for ETH is set to 0 ETH unless the gas station is used. Actual fees vary by network conditions at broadcast time. When using the gas station, no minimum ETH balance is required.
The wallet must hold an ETH balance calculated from gas limit estimates, multipliers for gas limit and price, and priority fees — unless the transfer uses the Gas Station, which requires no ETH balance.
Anchorage Digital sets a MaxFee to ensure users don’t overpay while still having enough for transaction processing. Priority fee is set to 0.01 Gwei.
For ERC-20 withdrawals and transfers, avoiding dust is not possible due to the non-deterministic nature of gas for smart contract interactions. For ETH transfers, it is theoretically possible to avoid dust by specifying maxFee and maxPriorityFee to consume the remaining balance, but this is not currently supported on the platform.