> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trusted destinations

> Register the crypto addresses and bank accounts an account can withdraw to, track approval, and look destinations up.

A withdrawal never carries a raw address or bank account. It names a destination you registered ahead of time, and that destination must be `ACTIVE`. Registering destinations separately keeps every payout target reviewable, reusable, and governed by [policy](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-policies.md).

## What's available

| Action | Status | Notes |
| :- | :- | :- |
| Create a crypto destination | Live | |
| Create a USD destination | Live | Enabled per organization |
| List and get destinations | Live | |
| Delete a destination | Under construction | Returns mocked data only |

## How it works

**1. Create the destination**

`POST /v4/accounts/{accountId}/destinations` with the owner, a name, and either a crypto address or bank details. The response returns the destination's ID and `PENDING` status right away.

**2. Wait for it to become ACTIVE**

Creation runs through Anchorage Digital's review steps. Poll `GET /v4/accounts/{accountId}/destinations/{destinationId}` until `status` is `ACTIVE`. A `REJECTED` or `FAILED` destination carries the reason in `statusReason`.

**3. Reference it in withdrawals**

Pass the destination's `id` as `info.destinationId` when you [create a withdrawal](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-withdrawals.md). One destination can serve any number of withdrawals.

## Owner

Every destination has an `owner`, which decides who can withdraw to it:

| `owner.type` | Meaning |
| :- | :- |
| `ORGANIZATION` | Your organization, at the top of the account tree |
| `ACCOUNT` | An account. An omnibus holds destinations directly. An FBO holds them for the accounts under it. |
| `SUBACCOUNT` | A single segregated account |
| `CUSTOMER` | An end customer onboarded through Anchorage Digital |

`owner.id` is the ID of that entity. The `accountId` in the path is the account you're working in.

## Destination status

| Status | Meaning |
| :- | :- |
| `PENDING` | Creation is in progress. The status doesn't say which step is outstanding. |
| `ACTIVE` | The destination exists and can be withdrawn to |
| `REJECTED` | Creation was declined. See `statusReason`. |
| `FAILED` | Creation couldn't be completed. See `statusReason`. |
| `CANCELED` | Creation was canceled before it completed |
| `DELETING` | Removal is in progress |
| `DELETED` | The destination was removed |

***

## Integration steps

### Step 1: Create a crypto destination

**`POST /v4/accounts/{accountId}/destinations`**

| Field | Required | Description |
| :- | :- | :- |
| `type` | Yes | `CRYPTO` |
| `name` | Yes | A name that identifies the destination |
| `description` | No | Details about the destination |
| `owner` | Yes | `type` and `id`, as above |
| `externalId` | No | Your ID for the request. It stays a valid key for the destination, so it must be unique in your organization for all time. |
| `destinationInfo.address` | Yes | The address |
| `destinationInfo.networkId` | Yes | The network, such as `BTC` or `ETH`. Take it from `GET /v4/asset-types`. |
| `destinationInfo.assetType` | No | Restrict the destination to one asset. Leave it out for a network-level destination. |
| `destinationInfo.memo` | No | A memo or tag, on networks that use one |
| `amlQuestionnaire` | Yes | Who holds the receiving address and who receives the funds. See below. |

The `amlQuestionnaire` says where the funds are going. `destinationType` is `FINANCIAL_INSTITUTION` (name the institution and its country) or `SELFHOSTED_WALLET` (describe the wallet and say whether your organization or another person or entity owns it). `recipientType` says who receives the funds: `DESTINATION_INSTITUTION`, `MY_ORGANIZATION`, `PERSON` (first and last name, country), or `ENTITY` (full name, country). The reference page lists every field and when each is required.

```bash Request theme={null}
curl --request POST \
     --url https://api.anchorage-staging.com/v4/accounts/cb80459c-a930-444e-8f17-69ba9d0e122f/destinations \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json' \
     --header 'Api-Signature: {signature}' \
     --header 'Api-Timestamp: {unix epoch seconds}' \
     --header 'Idempotency-Key: 6c1f2e3d-4a5b-4c6d-8e7f-9a0b1c2d3e4f' \
     --header 'content-type: application/json' \
     --data '{
  "type": "CRYPTO",
  "name": "Acme treasury - BTC",
  "externalId": "acme-dest-0042",
  "owner": { "type": "SUBACCOUNT", "id": "cb80459c-a930-444e-8f17-69ba9d0e122f" },
  "destinationInfo": {
    "networkId": "BTC",
    "assetType": "BTC",
    "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
  },
  "amlQuestionnaire": {
    "destinationType": "FINANCIAL_INSTITUTION",
    "institutionName": "Example Exchange",
    "institutionCountry": "US",
    "recipientType": "MY_ORGANIZATION"
  }
}'
```

```json Response (202) theme={null}
{
  "data": {
    "id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "externalId": "acme-dest-0042",
    "status": "PENDING",
    "createdAt": "2026-11-05T14:02:00Z"
  }
}
```

### Step 2: Create a USD destination

The same endpoint with `type: FIAT`. `destinationInfo` carries the beneficiary, the beneficiary bank, and an optional intermediary bank.

| Field | Required | Description |
| :- | :- | :- |
| `destinationInfo.usage` | Yes | `MY_ORGANIZATION` or `THIRD_PARTY` |
| `destinationInfo.beneficiary` | Yes | `type` (`INDIVIDUAL` with `firstName` and `lastName`, or `BUSINESS` with `entityName`), `account`, `address`, `city`, `state`, `zipCode`, `country` |
| `destinationInfo.beneficiaryBank` | Yes | `name`, `code` (`ABA` for a routing number, `BIC` for a SWIFT code), `id`, and the bank's address fields |
| `destinationInfo.intermediaryBank` | No | Same shape as `beneficiaryBank` |
| `destinationInfo.memo` | No | Note to beneficiary, up to 140 characters |

```json Request body theme={null}
{
  "type": "FIAT",
  "name": "Acme operating account",
  "owner": { "type": "ACCOUNT", "id": "7d04d1b8-20f1-4b5a-93e4-7fd3019c58f3" },
  "destinationInfo": {
    "usage": "MY_ORGANIZATION",
    "beneficiary": {
      "type": "BUSINESS",
      "entityName": "Acme Holdings LLC",
      "account": "000123456789",
      "address": "100 Main St",
      "city": "Austin",
      "state": "TX",
      "zipCode": "78701",
      "country": "US"
    },
    "beneficiaryBank": {
      "name": "Example Bank",
      "code": "ABA",
      "id": "021000021",
      "address": "1 Bank Plaza",
      "city": "New York",
      "state": "NY",
      "zipCode": "10001",
      "country": "US"
    }
  },
  "amlQuestionnaire": {
    "destinationType": "FINANCIAL_INSTITUTION",
    "institutionName": "Example Bank",
    "institutionCountry": "US",
    "recipientType": "MY_ORGANIZATION"
  }
}
```

USD destinations are enabled per organization. If yours isn't enabled yet, a `FIAT` request returns `400`.

### Step 3: List and get destinations

**`GET /v4/accounts/{accountId}/destinations`** lists destinations, including ones still `PENDING`. Filter with `status`, `type`, `ownerType` and `ownerId` together, `networkId`, `assetType` (which also returns network-level destinations on that network), `address`, `name`, or `externalId`. Page with `limit` and `after`.

**`GET /v4/accounts/{accountId}/destinations/{destinationId}`** returns one destination. This is also how you track creation.

```bash Request theme={null}
curl --request GET \
     --url https://api.anchorage-staging.com/v4/accounts/cb80459c-a930-444e-8f17-69ba9d0e122f/destinations/7c9e6679-7425-40de-944b-e07fc1f90ae7 \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json'
```

```json Response (200) theme={null}
{
  "data": {
    "id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "externalId": "acme-dest-0042",
    "type": "CRYPTO",
    "status": "ACTIVE",
    "owner": { "type": "SUBACCOUNT", "id": "cb80459c-a930-444e-8f17-69ba9d0e122f" },
    "name": "Acme treasury - BTC",
    "createdAt": "2026-11-05T14:02:00Z",
    "destinationInfo": {
      "networkId": "BTC",
      "assetType": "BTC",
      "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
    }
  }
}
```

### Step 4: Delete a destination

**Under construction.** `DELETE /v4/accounts/{accountId}/destinations/{destinationId}` is in the reference and accepts requests, but it doesn't yet remove the destination. The contract: a `PENDING` destination's creation is canceled, an `ACTIVE` one is removed, and the response reports `DELETING` until the work completes. This section will be updated when the endpoint is available for testing.


## Related topics

- [Trusted destinations](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/setup/trusted-destinations.md)
- [Delete Trusted Destination](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/trusted-destinations/delete-trusted-destination.md)
