curl --request POST \
--url "https://directory.example.com/dids/did%3Aopenpayload%3A1111111111111111111111/document/verification-methods" \
--header "Content-Type: application/json" \
--data '{
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"verification_method": {
"id": "did:openpayload:1111111111111111111111#signing",
"type": "Multikey",
"controller": "did:openpayload:1111111111111111111111",
"publicKeyMultibase": "<public-key>"
},
"nonce": "<nonce>",
"valid_until": "<future-epoch-milliseconds>",
"signer_key_id": "root",
"canonical_payload": "<payload>",
"signature": "<signature>"
}'
{
"status": "accepted",
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"tx_hash": "<transaction-hash>",
"message": "DID document modification submitted"
}
DID documents
Add verification method
Add verification method in a public OpenPayload DID document.
curl --request POST \
--url "https://directory.example.com/dids/did%3Aopenpayload%3A1111111111111111111111/document/verification-methods" \
--header "Content-Type: application/json" \
--data '{
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"verification_method": {
"id": "did:openpayload:1111111111111111111111#signing",
"type": "Multikey",
"controller": "did:openpayload:1111111111111111111111",
"publicKeyMultibase": "<public-key>"
},
"nonce": "<nonce>",
"valid_until": "<future-epoch-milliseconds>",
"signer_key_id": "root",
"canonical_payload": "<payload>",
"signature": "<signature>"
}'
{
"status": "accepted",
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"tx_hash": "<transaction-hash>",
"message": "DID document modification submitted"
}
Add verification method in a public OpenPayload DID document.
A verification method publishes a public key that compatible clients can use to verify signatures. Adding the method does not automatically authorize it for every purpose; authentication and service authorization are separate references.
Read Authorize a Directory update before signing.
Path parameters
string
required
The DID to update.
Request body
string
required
The DID to update. It must match the path.
string
required
The operation name. Use
AddVerificationMethod.object
required
The public verification method value for this operation.
string
required
The request nonce.
string
required
The authorization expiration time.
string
The public signing-key identifier. Defaults to
root.string
required
The payload supplied by an OpenPayload-compatible signer.
string
required
The authorization signature.
curl --request POST \
--url "https://directory.example.com/dids/did%3Aopenpayload%3A1111111111111111111111/document/verification-methods" \
--header "Content-Type: application/json" \
--data '{
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"verification_method": {
"id": "did:openpayload:1111111111111111111111#signing",
"type": "Multikey",
"controller": "did:openpayload:1111111111111111111111",
"publicKeyMultibase": "<public-key>"
},
"nonce": "<nonce>",
"valid_until": "<future-epoch-milliseconds>",
"signer_key_id": "root",
"canonical_payload": "<payload>",
"signature": "<signature>"
}'
Response
string
required
The submission status.
string
required
The affected DID.
string
required
The document operation.
string
required
The transaction hash.
string
required
A human-readable submission result.
{
"status": "accepted",
"did": "did:openpayload:1111111111111111111111",
"action": "AddVerificationMethod",
"tx_hash": "<transaction-hash>",
"message": "DID document modification submitted"
}
202 Accepted means the Directory accepted the request for processing. It does not confirm final settlement.Straight to the point
- Action:
AddVerificationMethod - Signed item: complete
verification_methodobject - Controller must equal the DID