---
title: "Purge Resource Metadata"
description: "/metadata/purge removes the metadata block attached to a stored resource. This is useful when you want to reset tags and descriptions entirely, or before re-initializing metadata with fresh context."
stack: "Enterprise Stack (commercial) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/administration/services/metadata/purge
generated: 2026-07-20
---
# Purge Resource Metadata

`/metadata/purge` removes the metadata block attached to a stored resource. This is useful when you want to reset tags and descriptions entirely, or before re-initializing metadata with fresh context.

## Purge metadata (KMS key example)

**Option: CURL**

Endpoint: `/v1/{target}/kms-service-api/keys/metadata/purge` | [API Reference](https://enterprise.sandbox.walt.id/swagger/index.html#/Service%20%7C%20Key%20Management/delete_v1__target__kms_service_api_metadata_purge)

**Example Request**

```bash
curl -X 'DELETE' \
  'https://{orgHost}.enterprise-sandbox.waltid.dev/v1/{target}/kms-service-api/keys/metadata/purge' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}'
```

**Path Parameters**

- `orgHost`: _String_ - Organization host alias to call against. In sandbox, `test` maps to `https://test.enterprise-sandbox.waltid.dev`.
- `target`: _resourceIdentifier_ - Full path to the KMS key (or other resource) whose metadata you want to delete, e.g. `test.tenant1.kms-eu.key-auth`.

**Response Codes**

- `200` – Metadata purged successfully.
- `404` – No metadata existed for that resource.
- `401/403` – Authentication or authorization failure.