Organization-level DIDs

The DID Registry Service can manage organization-level DIDs. These DIDs are scoped to the entire organization and are not limited to a specific tenant. They are useful for representing entities that manage or oversee multiple tenants within the Enterprise stack.

Example: did:web:{orgID}.enterprise-sandbox.waltid.dev:alice

Accessible at: https://{orgID}.enterprise-sandbox.waltid.dev/alice/did.json.

Organization-level DIDs are used for entities that manage or oversee tenants within the Enterprise stack.

Create Organization-Level DID registry service

CURL

Endpoint: /v1/{target}/resource-api/services/create | API Reference

Example Request

curl -X 'POST' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/{target}/resource-api/services/create' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "type": "did-registry"
}'

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 in which to create the new organization level DID Registry service , e.g. waltid.didregistry

Body Parameters

  • type: serviceType - Specifies the type of service to create. In our case did-registry

Response Codes

  • 201 - Service created successfully.

Setup root DID Registry

CURL

Endpoint: /v1/organization/update-config | API Reference

Example Request

curl -X 'POST' \
  'https://{orgID}.enterprise-sandbox.waltid.dev/v1/organization/update-config' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer {yourToken}' \
  -H 'Content-Type: application/json' \
  -d '{
  "rootDidRegistry": "waltid.didregistry"
}'

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.

Body Parameters

  • rootDidRegistry: resourceIdentifier - The ID of the DID Registry Service to be used for organization-level DIDs. e.g. waltid.didregistry

Response Codes

  • 200 - Configuration updated successfully.
Last updated on April 21, 2025
SetupTenant-Level DIDs