---
title: "List destinations reachable from a Link-account source"
method: GET
path: "/api/link/v1/enterprises/{enterpriseId}/transfer-destinations"
tags: ["Link Accounts"]
---

# List destinations reachable from a Link-account source

`GET /api/link/v1/enterprises/{enterpriseId}/transfer-destinations`

Returns enterprise Link accounts the caller has `link.account.view` on that the
given Link-account source can transfer to, split into two segments: off-chain
(`internalDestinations`, with subtype entries) and on-chain (`externalDestinations`,
no subtype). Same-hierarchy accounts are excluded from the external segment since
they are already covered by the internal segment. The response envelope carries
`sourceSupportsOnChainWithdrawal` to indicate whether BitGo-wallet / external-address
destinations can also be used alongside the Link-account destinations returned here.
Excludes accounts with `status != active`.

## Path parameters

- `enterpriseId` string, required

## Query parameters

- `sourceLinkAccountId` string, required
- `sourceAccountSubType` string, required
- `genericAsset` string, required
- `name` string

## Headers

- `user-id` string, required

## Response `200`

OK

- V1GetTransferDestinationsResponse — Response for `GET /api/link/v1/enterprises/{enterpriseId}/transfer-destinations`. Given a Link-account source, returns the destinations it can transfer to. Segments: - `internalDestinations` — off-chain reachable accounts (same-venue), grouped by account with subtype entries. May be empty when no same-venue rail qualifies. - `externalDestinations` — on-chain reachable accounts. May be cross-venue or same- venue but in a different account hierarchy from the source. Same-hierarchy entries are suppressed since they're already covered by the internal segment. `sourceSupportsOnChainWithdrawal` indicates whether BitGo wallet / external-address destinations can also be used alongside the Link-account destinations returned here. It is a property of the source venue, not of the caller's permission scope — always present, even when the caller's `link.account.view` scope yields no Link-account rows. Not paginated — the candidate set (enterprise Link accounts at a small number of candidate venues) is bounded and returned in full in one response.
  - `internalDestinations` object, required
    - `accounts` object[], required
      - `id` string, required
      - `name` string, required
      - `venueId` string, required
      - `venueName` string, required
      - `whitelistingEnabled` boolean, required
      - `accountSubTypes` object[], required
        - `accountSubType` string, required
        - `accountSubTypeLabel` string
      - `subAccounts` object[]
        - `id` string, required
        - `name` string, required
        - `venueId` string, required
        - `venueName` string, required
        - `whitelistingEnabled` boolean, required
        - `accountSubTypes` object[], required
          - `accountSubType` string, required
          - `accountSubTypeLabel` string
  - `externalDestinations` object, required
    - `accounts` object[], required
      - `id` string, required
      - `name` string, required
      - `venueId` string, required
      - `venueName` string, required
      - `whitelistingEnabled` boolean, required
      - `subAccounts` object[]
        - `id` string, required
        - `name` string, required
        - `venueId` string, required
        - `venueName` string, required
        - `whitelistingEnabled` boolean, required
  - `sourceSupportsOnChainWithdrawal` boolean, required

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/bitgo/apis/bitgo-api.md) · [All operations](https://skmtc.net/bitgo/apis/bitgo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bitgo/bitgo-api/revisions/e445c15e5bee/schema)