Update or Deactivate DID
Update or deactivate a DID
Users are able to update DID Documents for various reasons, such as to include a new section or to rotate the Verification Method keys within the DID Document.
With the /did/update
API, users are able to input either:
The section of the DID Document they would like to update; or
The full updated DID Document body.
Update a DID Document.
This endpoint updates a DID Document. As an input, it can take JUST the sections/parameters that need to be updated in the DID Document (in this scenario, it fetches the current DID Document and applies the updated section). Alternatively, it take the fully-assembled DID Document with updated sections as well as unchanged sections.
DID identifier to be updated.
"did:cheqd:testnet:7bf81a20-633c-4cc7-bc4a-5a45801005e0"
Service section of the DID Document.
Verification Method section of the DID Document.
Authentication section of the DID Document.
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.
This input field contains either a complete DID document, or an incremental change (diff) to a DID document. See Universal DID Registrar specification.
The request was successful.
The default key id of which is the key associated with the first verificationMethod
The list of keys associated with the list of verificationMethod's of DIDDocument
The list of keyRefs which were used for signing the transaction
The list of all possible keys, inlcuding all controller's keys
Users are also able to deactivate DID Documents to prevent further updates and to provide client applications the relevant information that the DID Document is no longer actively used.
A /did/deactivate
request must be signed by all of the Verification Method keys listed in the DID Document.
Deactivate a DID Document.
This endpoint deactivates a DID Document by taking the DID identifier as input. Must be called and signed by the DID owner.
DID identifier to deactivate.
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.
The request was successful.
"https://w3id.org/did-resolution/v1"
This input field contains either a complete DID document, or an incremental change (diff) to a DID document. See Universal DID Registrar specification.
Last updated