---
title: "Archive Trust Anchor [EXPERIMENTAL]"
method: DELETE
path: "/trustAnchors/{trustAnchorKey}"
tags: ["Trust Anchors"]
---

# Archive Trust Anchor \[EXPERIMENTAL\]

`DELETE /trustAnchors/{trustAnchorKey}`

## Request

- Base URL: `https://eu-west-1.api.silverflow.com/v1`
- URL: `https://eu-west-1.api.silverflow.com/v1/trustAnchors/{trustAnchorKey}`
- Auth: one of:
  - HTTP basic
  - HTTP bearer
- TypeScript: <https://skmtc.dev/silverflow/apis/silverflow-api/docs/trustAnchors/:trustAnchorKey/delete.ts> (a function with typed inputs; its response is checked against the schema)

This operation archives the referenced Trust Anchor. It fails when a certificate bound to one of the Agent's
API keys still depends on this Trust Anchor; remove or replace those certificates first.

Archiving frees one of the Agent's two active Trust Anchor slots, which is the last step of rotating a CA.

Changes can take up to 15 minutes to take effect.

Requires `trustAnchors:Archive` permission.

## Path parameters

- `trustAnchorKey` string, required

## Response `204`

Trust Anchor archived successfully

## Other responses

- `401`: Authentication information is missing or invalid
- `403`: The authenticated client is forbidden to make the request for the resource identified.
- `404`: The requested resource was not found
- `409`: The request could not be completed due to a conflict with the current state of the resources involved in the request.
- `429`: The number of requests (per minute) has exceeded the configured maximum

---

[API](https://skmtc.dev/silverflow/apis/silverflow-api.md) - [All operations](https://skmtc.dev/silverflow/apis/silverflow-api/llms.txt) - [OpenAPI document](https://skmtc.dev/silverflow/apis/silverflow-api/revisions/43ecbe4fd6ea?raw)