Key concepts
| Action | Description |
|---|---|
| View whitelist | List Trusted Destinations on file and retrieve Trusted Destination IDs |
| Manage whitelist | Create, modify, or delete Trusted Destinations |
| Withdraw | Send USD out of an ADB fiat account |
| Transfer | Move USD between accounts you own (internal) or to a Trusted Destination (external) |
Action availability
| Action | API | Web Platform | Path |
|---|---|---|---|
| View Trusted Destinations | Available for testing | Live | API or web platform |
| Manage Trusted Destinations | Not yet available | Live | Web platform |
| Withdraw | Available for testing | Live | API or web platform |
| Transfer API, internal | Available for testing | N/A | API |
| Transfer API, external | Available for testing | N/A | API |
1. Trusted Destination management
Current path: web platform only. To add a fiat Trusted Destination, follow the Adding Trusted Destinations guide. When selecting destination type, choose Fiat. If testing pre-release, contact api@anchorage.com after completing this step to have destinations enabled for your account. Create, modify, and delete API endpoints are in development.2. Fetch Trusted Destinations
To initiate a fiat withdrawal or external transfer via API, call the list endpoint and filter ontype == "fiat" to retrieve the id of the target Trusted Destination.
GET /v2/trusted_destinations — Reference
Example response
3. Withdraw
Send USD from an ADB fiat account to a Trusted Destination. Use the wallet ID assource and the Trusted Destination ID (from step 2) as destination.
POST /v2/withdrawals — Reference
Example payload
| Field | Description |
|---|---|
amount | USD amount as a string |
source.id | ID of the source ADB fiat wallet — retrieve via GET /v2/wallets |
destination.id | Trusted Destination ID from step 2 |
purpose | Enum classifying the reason for the transfer (e.g., TRADING_SETTLEMENT) |
memo | Free-text description sent with the wire |
GET /v2/transactions or webhook events.
4. Transfer
Move USD between accounts you own (internal) or to a Trusted Destination (external). Thedestination.type field discriminates the two flows:
WALLET— internal transferTRUSTED_DESTINATION— external transfer (filter step 2 response ontype == "fiat")
POST /v2/transfers — Reference
| Field | Description |
|---|---|
source.id | ID of the source ADB wallet — retrieve via GET /v2/wallets |
destination.id | Destination wallet ID (internal) or Trusted Destination ID (external) |
transferMemo | Free-text description attached to the transfer |
amount | USD amount as a string |
GET /v2/transactions, GET /v2/transfers, or webhook events.
Key terms
| Term | Definition |
|---|---|
| Trusted Destination (TD) | An external counterparty (bank account or crypto address) pre-registered with Anchorage and approved to receive funds |
| Fiat TD | A TD representing a bank account — identified by type: "fiat" in API responses |
| Crypto TD | A TD representing a blockchain address — identified by type: "crypto" in API responses |
trustedDestinationId | The id field on a TD; used in withdrawal and transfer payloads |
institutionCode | Identifier type for the receiving bank: F = ABA/Fedwire (domestic US), B = SWIFT/BIC (international) |
institutionId | Routing identifier value — format depends on institutionCode |
assetParametersFiatTrustedDestination | Wrapper object for fiat-specific transfer parameters |
purpose | Classifies the reason for the transfer (e.g., TRADING_SETTLEMENT) |
memo | Free-text description sent with the wire |

