DID Storage

By default, the DID service does not save the DIDs (Decentralized Identifiers) and their corresponding DID documents that are created. However, you can enable this feature by using the DID store service. Once the DID store service is attached to the DID service, all created DIDs and their associated DID documents will be stored in the designated DID store.

There is also the option to attach more then one DID store, in this case the created DIDs & Documents will be stored in all attached DID stores.

Link DID Store to DID Service

If you don't have a DID store yet, you can learn how to create on here.

CURL

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

Example Request

curl -X 'POST' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/did-service-api/dids/dependencies/add' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d 'waltid.tenant1.did-store1'

Body

waltid.tenant1.did-store1

Path Parameters

  • orgID: - When performing operations within an organization, it is essential to use the organization's Base URL or another valid host alias. For example, if your organization is named test, your default Base URL will be test.enterprise-sandbox.walt.dev when using the sandbox environment.
  • target: resourceIdentifier - The target indicates the organization + tenant + DID service to which to add an existing DID Store ({organizationID}.{tenantID}.{didServiceID}), e.g. waltid.tenant1.did1

Body Parameters

  • Specifies the ID of the DID store that should be linked.

Response Codes

  • 201 - Unit attached.
SetupDID Service