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

# Unfreeze accounts

> Permissions required: **Manage Accounts**

Unfreeze the specified accounts. You can only unfreeze accounts that were previously frozen through the API, not accounts frozen by Anchorage Digital's compliance program.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml post /accounts/unfreeze
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/unfreeze:
    post:
      tags:
        - Accounts
      summary: Unfreeze accounts
      description: >-
        Permissions required: **Manage Accounts**


        Unfreeze the specified accounts. You can only unfreeze accounts that
        were previously frozen through the API, not accounts frozen by Anchorage
        Digital's compliance program.
      operationId: unfreezeAccounts
      parameters:
        - 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
      requestBody:
        description: Accounts to unfreeze
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - ids
              properties:
                ids:
                  type: array
                  items:
                    type: string
                    format: uuid
                    example: 3486b413-93d3-4447-afce-2b9c9dc34a32
      responses:
        '200':
          description: Per-item result of the action
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BatchActionResponse'
        '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'
        '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:
    BatchActionResponse:
      title: Batch Action Response
      description: Per-item results for a batch action.
      type: object
      required:
        - data
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/BatchItemResult'
    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
    BatchItemResult:
      title: Batch Item Result
      type: object
      description: The per-item result of a batch action, discriminated by status.
      discriminator:
        propertyName: status
        mapping:
          SUCCESS: '#/components/schemas/BatchItemSuccessResult'
          ERROR: '#/components/schemas/BatchItemErrorResult'
      oneOf:
        - $ref: '#/components/schemas/BatchItemSuccessResult'
        - $ref: '#/components/schemas/BatchItemErrorResult'
    BatchItemSuccessResult:
      title: Batch Item Success Result
      type: object
      description: Successful outcome for one item of a batch request.
      properties:
        index:
          $ref: '#/components/schemas/BatchItemIndex'
        id:
          $ref: '#/components/schemas/BatchItemId'
        status:
          type: string
          description: Outcome of the action for this item
          enum:
            - SUCCESS
          default: SUCCESS
      required:
        - index
        - id
        - status
    BatchItemErrorResult:
      title: Batch Item Error Result
      type: object
      description: >-
        Failed outcome for one item of a batch request. Other items in the same
        batch may still have succeeded.
      properties:
        index:
          $ref: '#/components/schemas/BatchItemIndex'
        id:
          $ref: '#/components/schemas/BatchItemId'
        status:
          type: string
          description: Outcome of the action for this item
          enum:
            - ERROR
          default: ERROR
        error:
          description: Human-readable reason the item failed.
          type: string
      required:
        - index
        - status
        - error
    BatchItemIndex:
      title: Batch Item Index
      type: integer
      minimum: 0
      description: >-
        The 0-based position of this item in the request. Always present
        regardless of outcome, so a result can be correlated with its request
        item even when no id was ever assigned.
    BatchItemId:
      title: Batch Item ID
      type: string
      description: >-
        Unique identifier of the item this result applies to. Always present on
        success. On error, present only if an id was assigned before the item
        failed (e.g. an existing entity targeted by an action); absent when the
        item was rejected before any id could exist, such as a failed validation
        on creation. Use `index` to correlate a result with its request item
        when `id` is absent.
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [Accounts](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-accounts.md)
- [Create accounts](https://docs.anchorage.com/knowledge-base/api-reference/v4/accounts/create-accounts.md)
- [List accounts](https://docs.anchorage.com/knowledge-base/api-reference/v4/accounts/list-accounts.md)
- [Get an account](https://docs.anchorage.com/knowledge-base/api-reference/v4/accounts/get-an-account.md)
