Update Resource Metadata (JSON Patch)

/metadata/update lets you modify specific metadata fields without replacing the entire object. It accepts RFC 6902 JSON Patch documents, so you can add, replace, or remove individual fields atomically.

Patch metadata (KMS key example)

CURL

Endpoint: /v1/{target}/kms-service-api/metadata/update | API Reference

Example Request

curl -X 'POST' \
  'https://{orgHost}.enterprise-sandbox.waltid.dev/v1/{target}/kms-service-api/metadata/update' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '[
  {
    "op": "replace",
    "path": "/description",
    "value": "Updated description"
  }
]'

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 patch, e.g. test.tenant1.kms-eu.key-auth.

Body

[
  {
    "op": "replace",
    "path": "/description",
    "value": "Updated description"
  }
]

Body Parameters

  • patch: JSON object - A single JSON Patch operation (op, path, value, etc.). To apply multiple operations, send an array (per RFC 6902).

Response Codes

  • 200 – Patch applied successfully.
  • 400 – Invalid JSON Patch document or patch could not be applied.
  • 401/403 – Authentication or authorization failure.
Last updated on December 3, 2025