Skip to main content
Delete a DID
This endpoint submits the delete_did control operation for an OpenPayload DID. Use it only when the identity is meant to be removed from the registry. For a device retirement, use Tombstone a device instead.

Request

string
required
The complete DID to delete, URL-encoded in the path.
The JSON body must include the same DID-key proof fields as Deactivate a DID, with action: "delete_did": did, current control_nonce as nonce, future valid_until, authorized signer_key_id, canonical_payload, and signature. Sign the locally constructed canonical payload bytes. The Directory rejects a path and body DID mismatch, stale nonce, expired request, or mismatched payload. The 202 Accepted response contains the DID, status: "accepted", extrinsic: "apply_control_with_proof", and tx_hash. It confirms submission only. Verify the resulting registry state after chain finalization. A deleted DID may no longer resolve; clients must not assume a 202 response has already removed it.

Straight to the point