> ## 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.

# Delete destination

> Permissions required: **Manage Trusted Destinations**

Remove a destination. Cancels creation if the destination is still `PENDING`, removes it if it is `ACTIVE`. Removal is asynchronous: the destination reports `DELETING` until the work completes.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml delete /accounts/{accountId}/destinations/{destinationId}
openapi: 3.1.0
info:
  title: Anchorage Digital Account APIs (v4)
  version: 4.0.0-beta
  description: >-
    Reference for the Anchorage Digital v4 API, the surface behind Crypto as a
    Service: account management (accounts and the account tree, beneficiaries,
    freeze/unfreeze/close), balances and transactions, trusted destinations,
    orders and allocations, withdrawals, deposit instructions, deposit
    attributions, the policy engine (policies, approval keys), and supported
    asset types. Approval groups, endorsements, compliance profiles, customers
    (onboarding), fee configuration updates, interest enrollment, funding
    allocations, and destination removal are under construction and return
    mocked data only.


    Status: BETA. The v4 API is available in the sandbox only
    (https://api.anchorage-staging.com/v4) and is not available in production
    yet. The contract may change until general availability. Which endpoints are
    live, in final testing, or under construction:
    https://docs.anchorage.com/platform/developers/caas/caas-overview


    Authentication: every request carries an `Api-Access-Key` header. Every
    POST, PATCH, and DELETE additionally requires an `Idempotency-Key`, and is
    signed with `Api-Signature` (hex-encoded Ed25519 over
    `timestamp_epoch_seconds + uppercase(http_method) + request_path +
    request_body`) plus `Api-Timestamp` (unix epoch seconds).


    Pagination: list endpoints accept `after` (cursor) and `limit` (page size, 1
    to 1000, default 100) and return a `page.endCursor` to continue from. Errors
    use a common envelope with a human-readable `message`; batch endpoints
    return a result per item instead.


    Guides: https://docs.anchorage.com/platform/developers/caas/caas-overview
servers:
  - url: https://api.anchorage-staging.com/v4
security:
  - Api-Access-Key: []
tags:
  - name: Accounts
  - name: Compliance Profiles
  - name: Balances
  - name: Transactions
  - name: Trusted Destinations
  - name: Orders & Allocations
  - name: Withdrawals
  - name: Deposit Instructions
  - name: Deposit Attributions
  - name: Policies
  - name: Approval Groups
  - name: Endorsements
  - name: Customers
  - name: Asset Types
paths:
  /accounts/{accountId}/destinations/{destinationId}:
    delete:
      tags:
        - Trusted Destinations
      summary: Delete destination
      description: >-
        Permissions required: **Manage Trusted Destinations**


        Remove a destination. Cancels creation if the destination is still
        `PENDING`, removes it if it is `ACTIVE`. Removal is asynchronous: the
        destination reports `DELETING` until the work completes.
      operationId: deleteDestination
      parameters:
        - name: accountId
          in: path
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          required: true
          description: Account ID or subaccount ID (a UUID).
        - name: destinationId
          in: path
          required: true
          description: ID of the destination
          schema:
            type: string
        - name: Idempotency-Key
          in: header
          schema:
            type: string
          required: true
          description: >-
            Client-supplied key that deduplicates retried requests. Reusing a
            key returns the original result instead of repeating the action.
        - name: Api-Signature
          in: header
          required: true
          schema:
            type: string
            pattern: ^[0-9A-Fa-f]{128,160}$
          description: >-
            A hex-encoded Ed25519 signature of `timestamp_epoch_seconds +
            uppercase(http_method) + request_path + request_body`.
        - name: Api-Timestamp
          in: header
          required: true
          schema:
            type: integer
            format: int64
          description: Current timestamp, represented as unix epoch seconds
      responses:
        '202':
          description: >-
            Deletion accepted. The destination is returned with its updated
            status so the caller can track the removal.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DestinationResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '409':
          description: Conflict
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
components:
  schemas:
    DestinationResponse:
      title: Destination Response
      type: object
      required:
        - data
      properties:
        data:
          $ref: '#/components/schemas/Destination'
    ErrorDetails:
      title: ErrorDetails
      type: object
      properties:
        message:
          description: A human-readable message providing more details about the error.
          example: Missing required field 'amount'.
          type: string
      required:
        - message
    Destination:
      title: Destination
      type: object
      required:
        - id
        - type
        - status
        - owner
        - name
        - createdAt
      properties:
        id:
          description: >-
            A unique ID for the destination, stable from the creation request
            onwards.
          type: string
        externalId:
          description: >-
            The client-provided ID from the creation request. Remains a valid
            key for addressing this destination.
          type: string
        type:
          $ref: '#/components/schemas/DestinationType'
        status:
          $ref: '#/components/schemas/DestinationStatus'
        statusReason:
          description: >-
            An explanation of the current status. Present when `status` is
            `REJECTED` or `FAILED`.
          type: string
        owner:
          $ref: '#/components/schemas/DestinationOwner'
        name:
          description: The name that identifies this destination.
          type: string
        description:
          description: Details about this destination.
          type: string
        createdAt:
          description: The time the destination was requested.
          type: string
          format: date-time
          example: '2026-08-07T12:34:56.000Z'
        destinationInfo:
          description: The destination information.
          oneOf:
            - $ref: '#/components/schemas/DestinationCryptoData'
            - $ref: '#/components/schemas/DestinationFiatData'
    DestinationType:
      title: Destination Type
      description: Indicates which variant object carries the destination's details.
      type: string
      example: CRYPTO
      enum:
        - CRYPTO
        - FIAT
    DestinationStatus:
      title: Destination Status
      description: >-
        The destination's position in its lifecycle.


        * `PENDING` - creation is in progress. This status does not report which
        step is outstanding: the steps are internal, some of them wait on action
        the API caller cannot take, and the mechanism that approves a
        destination is expected to change.

        * `ACTIVE` - the destination exists and can be withdrawn to.

        * `DELETING` - removal is in progress.

        * `REJECTED` - creation was declined. See `statusReason`.

        * `FAILED` - creation could not be completed. See `statusReason`.

        * `CANCELED` - creation was canceled before it completed.

        * `DELETED` - the destination was removed.
      type: string
      example: ACTIVE
      enum:
        - PENDING
        - ACTIVE
        - DELETING
        - REJECTED
        - FAILED
        - CANCELED
        - DELETED
    DestinationOwner:
      title: Destination Owner
      description: The entity that owns a destination.
      type: object
      required:
        - type
        - id
      properties:
        type:
          $ref: '#/components/schemas/DestinationOwnerType'
        id:
          description: The ID of the owner, interpreted according to `type`.
          type: string
    DestinationCryptoData:
      title: Destination Crypto Data
      description: Details of a crypto destination. Required when `type` is `CRYPTO`.
      type: object
      required:
        - address
        - networkId
      properties:
        address:
          description: The crypto address for the intended destination.
          example: 2N19AcihQ1a4MxQW658UFHTioUNnMkiHPkw
          type: string
        assetType:
          description: >-
            A string representing a type of asset, which usually corresponds to
            the asset's ticker symbol. Use `/asset-types` to list all of the
            supported asset types for your organization.
          example: BTC
          type: string
        networkId:
          description: The ID of the network this destination belongs to.
          example: BTC
          type: string
        memo:
          description: >-
            Additional data to be sent along with the transaction on blockchains
            that support it.
          example: Internal trade ID 0xabc123
          type: string
          maxLength: 512
    DestinationFiatData:
      title: Destination Fiat Data
      description: Details of a fiat (wire) destination. Required when `type` is `FIAT`.
      type: object
      required:
        - usage
        - beneficiary
        - beneficiaryBank
      properties:
        usage:
          description: The owner of the recipient account
          example: MY_ORGANIZATION
          type: string
          enum:
            - MY_ORGANIZATION
            - THIRD_PARTY
        beneficiary:
          $ref: '#/components/schemas/DestinationFiatBeneficiaryData'
        beneficiaryBank:
          $ref: '#/components/schemas/DestinationFiatBankData'
        intermediaryBank:
          $ref: '#/components/schemas/DestinationFiatBankData'
        memo:
          description: Note to Beneficiary, maximum 140 characters
          example: Quarterly dividend
          type: string
          maxLength: 140
    DestinationOwnerType:
      title: Destination Owner Type
      description: >-
        The kind of entity that owns a destination, indicating how the owner's
        `id` should be interpreted.


        * `ORGANIZATION` - the organization, at the top of the account tree.

        * `ACCOUNT` - an account. An Omni account holds destinations directly;
        an FBO account holds them for its subaccounts.

        * `SUBACCOUNT` - a single subaccount.

        * `CUSTOMER` - a program customer.
      type: string
      example: ACCOUNT
      enum:
        - ORGANIZATION
        - ACCOUNT
        - SUBACCOUNT
        - CUSTOMER
    DestinationFiatBeneficiaryData:
      title: Destination Fiat Beneficiary Data
      description: The beneficiary of a fiat destination.
      type: object
      required:
        - type
        - account
        - address
        - city
        - state
        - zipCode
        - country
      properties:
        type:
          description: The beneficiary type
          example: INDIVIDUAL
          type: string
          enum:
            - BUSINESS
            - INDIVIDUAL
        firstName:
          description: First name of the beneficiary. Required when `type` is INDIVIDUAL.
          example: Satoshi
          type: string
        lastName:
          description: Last name of the beneficiary. Required when `type` is INDIVIDUAL.
          example: Nakamoto
          type: string
        entityName:
          description: Name of the beneficiary business. Required when `type` is BUSINESS.
          example: Acme Corp.
          type: string
        account:
          description: Beneficiary account number
          example: '123456789'
          type: string
        address:
          description: Beneficiary street address
          example: 123 Main Street
          type: string
        city:
          description: Beneficiary city
          example: Beverly Hills
          type: string
        state:
          description: Beneficiary state or province
          example: CA
          type: string
        zipCode:
          description: Beneficiary zip code
          example: '90210'
          type: string
        country:
          description: Beneficiary country (ISO 3166-1 alpha-2 code)
          example: US
          type: string
    DestinationFiatBankData:
      title: Destination Fiat Bank Data
      description: A financial institution of a fiat destination.
      type: object
      required:
        - name
        - code
        - id
        - address
        - city
        - state
        - zipCode
        - country
      properties:
        name:
          description: The name of the financial institution
          example: The Bank of New York Mellon
          type: string
        code:
          description: |-
            Financial institution ID code

            * `ABA` - Routing number
            * `BIC` - SWIFT code
          example: BIC
          type: string
          enum:
            - ABA
            - BIC
        id:
          description: >-
            Financial institution ID (a 9-digit routing number for `ABA`, a
            SWIFT code for `BIC`)
          example: IRVTUS3N
          type: string
        address:
          description: Financial institution street address
          example: 240 Greenwich Street
          type: string
        city:
          description: Financial institution city
          example: New York
          type: string
        state:
          description: Financial institution state or province
          example: NY
          type: string
        zipCode:
          description: Financial institution zip code
          example: '10286'
          type: string
        country:
          description: Financial institution country (ISO 3166-1 alpha-2 code)
          example: US
          type: string
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

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