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

# Archive a policy

> Archive a policy and submit the change for approval. Archiving does not delete the policy — the
definition is preserved and anything it once decided stays reconstructable.



## OpenAPI

````yaml /knowledge-base/openapi/v4.yaml delete /policies/{policyId}
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:
  /policies/{policyId}:
    delete:
      tags:
        - Policies
      summary: Archive a policy
      description: >-
        Archive a policy and submit the change for approval. Archiving does not
        delete the policy — the

        definition is preserved and anything it once decided stays
        reconstructable.
      operationId: archivePolicy
      parameters:
        - name: policyId
          in: path
          schema:
            type: string
            format: uuid
            example: 3486b413-93d3-4447-afce-2b9c9dc34a32
          required: true
          description: Unique identifier for the policy
        - 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: Change accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PolicyChangeAcceptedResponse'
        '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:
    PolicyChangeAcceptedResponse:
      title: Policy Change Accepted Response
      type: object
      required:
        - data
      properties:
        data:
          $ref: '#/components/schemas/PolicyChangeAccepted'
    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
    PolicyChangeAccepted:
      title: Policy Change Accepted
      type: object
      properties:
        id:
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        status:
          $ref: '#/components/schemas/PolicyStatus'
        action:
          $ref: '#/components/schemas/ActionRef'
        createdAt:
          type: string
          format: date-time
          example: '2019-01-02T12:34:56.000Z'
    PolicyStatus:
      title: Policy Status
      type: string
      enum:
        - PENDING_APPROVAL
        - ACTIVE
        - ARCHIVED
    ActionRef:
      title: Action Reference
      type: object
      required:
        - id
      description: >-
        A pointer to the action opened for this change. Present only when policy
        evaluation found every

        other requirement already satisfied except one: it still needs more
        endorsements. Absent means the

        change applied immediately with no policy blocking it.
      properties:
        id:
          description: The action's id in the Endorsements surface.
          type: string
          format: uuid
          example: 3486b413-93d3-4447-afce-2b9c9dc34a32
        reason:
          type: string
          description: Optional human-readable explanation of why endorsement is needed.
  securitySchemes:
    Api-Access-Key:
      type: apiKey
      name: Api-Access-Key
      in: header
      description: An API key associated with a security role

````

## Related topics

- [Policies and approvals](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-policies.md)
- [Archive an approval key](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/archive-an-approval-key.md)
- [Get a policy](https://docs.anchorage.com/knowledge-base/api-reference/v4/policies/get-a-policy.md)
- [Define a policy](https://docs.anchorage.com/knowledge-base/api-reference/v4/policies/define-a-policy.md)
- [Archive an approval group](https://docs.anchorage.com/knowledge-base/api-reference/v4/approval-groups/archive-an-approval-group.md)
