Trusted destinations

A trusted destination is an allowlisted external address. Adding one requires quorum approval. Once allowlisted, it can be used across the iOS app, web dashboard, and APIs.

What you can do where

Operation	API	Web dashboard
View trusted destinations
Create (digital assets)
Delete
Edit
Batch upload
Network-level destination (`isNetworkLevel`)

Sending to your own org’s addresses

You can allowlist addresses that belong to your own organization as trusted destinations to tag and label critical internal addresses. This is purely a convenience for recognition — it isn’t required for internal movement. If your concern is avoiding per-transaction quorum when moving assets between your own wallets, use the internal transfer API instead. Internal transfers set both source.type and destination.type to WALLET and don’t require a trusted destination or allowlisting.

Create a trusted destination via API

Requires the Manage Trusted Destinations permission. Adding a trusted destination requires quorum approval.

// POST /v2/trusted_destinations
{
  "idempotentId": "{unique ID}",
  "trustedDestinations": [
    {
      "address": "{address}",
      "assetType": "{asset}",
      "name": "{name}",
      "description": "{description}",
      "isNetworkLevel": true,
      "memo": "{memo}"
    }
  ]
}

Set isNetworkLevel: true to let the destination receive any asset on that network (digital assets only).

Connect a trusted destination to an API key

If you’re using the Transfers API to transfer to a trusted destination, you need to configure your API key’s permission group to allow it. There are two options, set when configuring the Transfers outside Anchorage permission on your API key.

API key configuration screen with Any trusted destination and Specific destinations options — API key transfer configuration showing the trusted destination options

Specific destinations (default)

By default, your API key is scoped to Specific destinations. Once a trusted destination has been added and approved, you must also add it to the API key’s permission group before you can transfer to it. See Permission groups and API keys for the step-by-step flow.

Any trusted destination

You can select Any trusted destination when configuring your key to automatically allowlist all current and future trusted destinations for that key. This removes the need to manually update the permission group each time a new trusted destination is approved.

APIs

API	Description
List trusted destinations	Returns trusted destinations.
Create new trusted destinations	Allowlists one or more destinations. Requires quorum approval.
Check status of trusted destinations	Returns the approval status of a pending destination.
Delete trusted destination	Removes a destination.

Getting started

Move money

Webhooks

Staking

What you can do where

Sending to your own org’s addresses

Create a trusted destination via API

Connect a trusted destination to an API key

Specific destinations (default)

Any trusted destination

APIs

​What you can do where

​Sending to your own org’s addresses

​Create a trusted destination via API

​Connect a trusted destination to an API key

​Specific destinations (default)

​Any trusted destination

​APIs

What you can do where

Sending to your own org’s addresses

Create a trusted destination via API

Connect a trusted destination to an API key

Specific destinations (default)

Any trusted destination

APIs