Deactivate a did:cheqd Decentralized Identifier (DID) using cheqd Studio.
Deactivating a DID marks it as no longer active or in use. This process updates the DID Document on the ledger to signal to verifiers, wallets, and other clients that the DID should no longer be trusted for interactions such as credential issuance or presentation.
Once a DID is deactivated:
✅ It cannot be updated again
❌ It cannot be reactivated
🛑 Applications resolving the DID will see its status marked as deactivated
When to Deactivate a DID
You should deactivate a DID when:
The associated identity (e.g. organisation, credential issuer) is no longer operating
The cryptographic keys have been compromised or rotated to a new DID
You want to enforce a clean break with no further updates to the DID Document
Security Requirement
To prevent unauthorized deactivations, a deactivate request must be signed by all of the Verification Method keys listed in the current DID Document.
This ensures that only the current controller(s) of the DID can authorize its deactivation.
🔐 If even one required key is missing or invalid, the request will be rejected.
How to Deactivate a DID
Use the API below to submit a request to deactivate a did:cheqd DID.
Deactivate a DID Document.
post
/did/deactivate/{did}
This endpoint deactivates a DID Document by taking the DID identifier as input. Must be called and signed by the DID owner.
Authorizations
x-api-keystringRequired
Path parameters
didstringRequired
DID identifier to deactivate.
Body
publicKeyHexsstring[]Optional
List of key references (publicKeys) which will be used for signing the message. The should be in hexadecimal format and placed in the wallet of current user.
