View Service Dependencies

Enterprise Stack services often rely on other services to provide their full functionality. For instance, a Wallet Service might depend on KMS, DID, DID Store, and Credential Store services, and a DID Service can depend on a DID Store. You can view all current dependencies of a service via the /dependencies/list endpoint on its service API.

List dependencies (DID Service example)

CURL

Endpoint: /v1/{target}/did-service-api/dependencies/list | API Reference

Example Request

curl -X 'GET' \
  'https://{orgHost}.enterprise-sandbox.waltid.dev/v1/{target}/did-service-api/dependencies/list' \
  -H 'accept: application/json' \
  -H 'Authorization: Bearer {yourToken}'

Path Parameters

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

Example Response 200 OK

[
  "test.tenant1.did-store-1"
]
  • Each entry is the fully-qualified service path of a dependency. The list is empty when no dependencies are configured.
Last updated on December 3, 2025
Update Service ConfigurationAdd Service Dependency