Update Service Configuration

/configuration/update replaces the configuration of a service. You must send the full service document (not a JSON Patch). This is how you update for example the default key generation options in a KMS or the supported credentials in an issuer service.

For service-specific configuration guidance, check the Setup section inside each service’s docs (e.g., Issuer, Verifier, KMS). Those pages show the concreate config options for a particular service that you can later update.

Update configuration (KMS example)

CURL

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

Example Request

curl -X 'PUT' \
  'https://{orgHost}.enterprise-sandbox.waltid.dev/v1/{target}/kms-service-api/configuration/update' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "traversable": true,
  "_id": "test.tenant1.kms1",
  "defaultKeyGenerationRequests": {},
  "parent": "test.tenant1"
}'

Path Parameters

  • orgHost: String - Organization host alias to call against. When you are working inside the sandbox tenant test, your base URL becomes https://test.enterprise-sandbox.waltid.dev.
  • target: resourceIdentifier - Full path to the service you are updating, following {organization}.{tenant}.{serviceId}. For example, the sandbox KMS target would be test.tenant1.kms1.

Body

{
  "traversable": true,
  "_id": "test.tenant1.kms1",
  "defaultKeyGenerationRequests": {},
  "parent": "test.tenant1"
}

Body Parameters

  • _id: Must be identical to {target}
  • defaultKeyGenerationRequests: Optional, default generation payloads.
  • parent: The identifier of the tenant under which the service lives.

Response Codes

  • 200 – Configuration replaced successfully (response body is empty).
  • 400 – Invalid or incomplete configuration payload.
  • 401/403 – Authentication or authorization failure.
Last updated on December 3, 2025
View Service ConfigurationView Service Dependencies