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

# Get a withdrawal

> Permissions required: **Read vault activity**

Get the current state of a single withdrawal.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml get /accounts/{accountId}/withdrawals/{withdrawalId}
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}/withdrawals/{withdrawalId}:
    get:
      tags:
        - Withdrawals
      summary: Get a withdrawal
      description: |-
        Permissions required: **Read vault activity**

        Get the current state of a single withdrawal.
      operationId: getWithdrawal
      parameters:
        - name: accountId
          in: path
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          required: true
          description: Account ID for this withdrawal.
        - name: withdrawalId
          in: path
          required: true
          description: WithdrawalId for this withdrawal.
          schema:
            type: string
      responses:
        '200':
          description: The withdrawal
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WithdrawalResponse'
        '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'
        '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:
    WithdrawalResponse:
      title: Withdrawal Response
      description: A single withdrawal, wrapped in the standard response envelope.
      type: object
      required:
        - data
      properties:
        data:
          $ref: '#/components/schemas/Withdrawal'
    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
    Withdrawal:
      title: Withdrawal
      type: object
      description: A withdrawal from an account to an external destination.
      properties:
        id:
          type: string
          description: Unique ID for the withdrawal.
        quantity:
          type: string
          description: >-
            Withdrawal quantity, as a positive decimal number encoded as a
            string.
          pattern: ^\d+(\.\d+)?$
        assetType:
          type: string
          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.
        info:
          type: object
          description: Info used to determine where to withdraw to
          oneOf:
            - $ref: '#/components/schemas/DestinationData'
            - $ref: '#/components/schemas/AccountData'
        status:
          type: string
          description: >-
            Current status of the withdrawal. One of:

            * `PENDING` - the withdrawal has been created and is being
            processed.

            * `COMPLETE` - the withdrawal has completed.

            * `CANCELED` - the withdrawal was canceled before completion.

            * `FAILED` - the withdrawal's transfer failed.
          enum:
            - PENDING
            - COMPLETE
            - CANCELED
            - FAILED
        transactionId:
          description: Unique Identifier for a transaction
          type: string
      required:
        - id
        - quantity
        - assetType
        - info
        - status
    DestinationData:
      title: Destination Data
      description: Destination for the withdrawal.
      type: object
      properties:
        destinationId:
          type: string
          description: >-
            ID of the destination (from the destinations API) to withdraw to.
            Must reference an ACTIVE destination
      required:
        - destinationId
    AccountData:
      title: Account data
      description: Account for the withdrawal.
      type: object
      properties:
        accountId:
          type: string
          description: ID of the account to withdraw to.
      required:
        - accountId
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [Withdrawals](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-withdrawals.md)
- [Get USD Withdrawal Request for a subaccount](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/subaccounts/get-usd-withdrawal-request-for-a-subaccount.md)
- [Internal withdrawals](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/withdraw/usd/internal.md)
- [Crypto withdrawal](https://docs.anchorage.com/knowledge-base/porto/developers/move-money/withdraw/crypto.md)
