Skip to main content
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.

What’s available

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. One destination can serve any number of withdrawals.

Owner

Every destination has an owner, which decides who can withdraw to it: owner.id is the ID of that entity. The accountId in the path is the account you’re working in.

Destination status


Integration steps

Step 1: Create a crypto destination

POST /v4/accounts/{accountId}/destinations 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.

Step 2: Create a USD destination

The same endpoint with type: FIAT. destinationInfo carries the beneficiary, the beneficiary bank, and an optional intermediary bank.
Request body
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.

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.