- API permission groups
- Wealth manager master API key
- Shared API key (for Anchorage Digital)
- Request signing
- Sandbox testing considerations
API permission group
Configure permissions before generating an API key.Generate an API key
Generate an API access key in the Anchorage Digital Web Dashboard under the API 2.0 section. Save the key securely as keys are not recoverable.
Name the group and enable the following permissions
| Permission | Enable? | Notes |
|---|---|---|
| Initiate withdrawal | No | Not required — withdrawals occur from vaults/wallets, not ledgered accounts. |
| Read subaccounts | Yes | Read all balances and transactions on the wealth management ledger. |
| Write subaccounts | Yes | Create transactions on the wealth management ledger. |
| Execute trades | Yes | Trade from ledger balances. If not visible, the user is not an enabled trader. |
| Read trades | Yes | Read all trades and trade settlements. Select All Trades on the org. If not visible, contact your account representative to enable trade permissions. |
| Onboarding | Yes | Enables API-based client onboarding. |
| Read deposit attribution | Yes | Access past and current deposit attributions. |
| Configure webhooks | Yes | Set up webhook notifications. |
| Read vault | Yes | Read balances across all wallets. Select All vaults. |
| Create new address | Yes | Create deposit wallets for account funding. |
| Transfer | No | Not needed for wealth management integration. |
| Propose and accept settlements | No | Not needed for wealth management integration. |
| Authorize settlements | No | Not needed for wealth management integration. |
After submitting the permission group, endorse the operation on the iOS app to achieve quorum. Anchorage Digital will then perform a risk review before the permission group can be used to create an API key.
Master API key generation
Create the shared API key for Anchorage Digital
The shared API key allows Anchorage Digital to settle trades on behalf of the wealth manager. It is provisioned by the wealth manager but owned and managed by Anchorage Digital.Create the permission group
The permission group is pre-configured. Select the applicable options, then quorum approve the operation. Wait for Anchorage Digital to complete its risk review before proceeding.
Create the shared API key
This step also requires quorum approval and an Anchorage Digital risk review. No Ed25519 key pair is required — Anchorage Digital manages this key.
API testing
Read-only APIs can be tested directly in the reference docs using your sandbox API key. Production keys will not work in the sandbox environment. For write APIs, generate a request signature outside of Postman or the reference docs. API signing: see the Request Signing guide. Host URLs:| Environment | URL |
|---|---|
| Sandbox | https://api.anchorage-staging.com/v2 |
| Production | https://api.anchorage.com/v2 |
Sandbox setup
Some steps only apply to production (e.g., onboarding, trading, settlement). Note the following before beginning sandbox testing:- Verify you are onboarded to the sandbox iOS app and have web dashboard access. Onboarding details are sent by Anchorage Digital via email.
- Admin users must download the iOS app for quorum approvals and API key creation.
Sandbox testnet assets
All sandbox activity uses testnet assets only.| Mainnet asset | Recommended testnet asset |
|---|---|
| Bitcoin | BTC_S (Signet) |
| Ethereum | ETHHOODI (Hoodi) |
| USDC | USDANCHOL (Hoodi) |
| Solana | SOL_TD (Devnet) |

