DID

Manage DID operation using DID APIs

Please generate access token before proceeding. Once you generated the access_token, you can pass this token as bearer authorization token in the header for all APIs.

Note: Some of these APIs are on-chain APIs which means they need network fee to successfully execute, so make sure that your application wallet address has $hid tokens. Read network fee section for more details.

Entity Studio SSI API base URL: https://api.entity.hypersign.id

There are 3 steps involved in DID creation:

• Generate a DID Document: Generate the data structure of the DID document.

• Sign a DID Document (optional): Sign the DID Document using verification method.

• Register a DID Document (optional) : Registers the signed DID Document on the blockchain network.

Note: You can choose not to register a DID on blockchain, in that case, the DID is concidered as private DID. We support Ed25519VerificationKey2020 for private DIDs. Kindly read difference between private and public DID in this section.

Create a DID

Generates the a new DID and DID Document.

POST/api/v1/did/create

Authorization

Authorization

Header parameters

Body

application/json

namespace*string

Namespace to be added in did.

Example: "testnet"

methodSpecificIdstring

MethodSpecificId to be added in did

Example: "0x19d73aeeBcc6FEf2d0342375090401301Fe9663F"

optionsall of

keyType used for verification

Response

201400409

DID Created

Body

application/json

did*string

Did document id

Example: "did:hid:namespace:......................."

registrationStatus*string

Did document registration status

Example: "COMPLETED/PROCESSING"

metaData*all of

metaData contaning initial didDocument

Request

JavaScriptCurlPython

const response = await fetch('/api/v1/did/create', {
    method: 'POST',
    headers: {
      "Authorization": "Bearer JWT",
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "namespace": "testnet"
    }),
});
const data = await response.json();

Response

201400409

{
  "did": "did:hid:namespace:.......................",
  "registrationStatus": "COMPLETED/PROCESSING",
  "metaData": {
    "didDocument": {
      "@context": [
        "https://www.w3.org/ns/did/v1"
      ],
      "id": "did:hid:method:......",
      "controller": [
        "did:hid:method:......"
      ],
      "alsoKnownAs": [
        "did:hid:method:......"
      ],
      "verificationMethod": [
        {
          "id": "did:hid:testnet:z28ScfSszr2zi2Bd7qmNE4mfHX5j8nCwx4DBF6nAUHu4p#key-1",
          "type": "EcdsaSecp256k1RecoveryMethod2020",
          "controller": "did:hid:method:..............",
          "blockchainAccountId": "eip155:1:0x19d73aeeBcc6FEf2d0342375090401301Fe9663F"
        }
      ],
      "authentication": [
        "did:hid:method:......"
      ],
      "assertionMethod": [
        "did:hid:method:......"
      ],
      "keyAgreement": [
        "did:hid:method:......"
      ],
      "capabilityInvocation": [
        "did:hid:method:......"
      ],
      "capabilityDelegation": [
        "did:hid:method:......"
      ],
      "service": [
        {
          "id": "did:hid:testnet:z23dCariJNNpMNca86EtVZVvrLpn61isd86fWVyWa8Jkm#linked-domain",
          "type": "LinkedDomains",
          "serviceEndpoint": "https://stage.hypermine.in/studioserver/api/v1/org/did:hid:testnet:......................"
        }
      ]
    }
  }
}

Request Body Parameters

• Namespace: DID name space. Possible value is testnet

Optional Parameters

• MethodSpecificId: Custom Id string which you want to attach with the DID. Please read did:hid method spec for details about possible format.

• Options.keyTypes: We support Ed25519VerificationKey2020, EcdsaSecp256k1RecoveryMethod2020 verification method key types. So only these two are possible values. Read the full specification here.

• Options.publicKey: Please pass the options.publickey property only for Ed25519VerificationKey2020 verification method key type. For EcdsaSecp256k1RecoveryMethod2020 , this property can be kept blank. Its value would be publickey (in multi base format)

• Options.walletAddress: Please pass options.walletAddress for keyType EcdsaSecp256k1RecoveryMethod2020

• Options.chainId: ChainId in HEX format. For example for Etheruem main net, the chain id would be 0x1. This property is only required for keytype EcdsaSecp256k1RecoveryMethod2020

Note: If no optional parameters are provided then, did will be created of verification key method type Ed25519VerificationKey2020

Note: If you want to create DID for blockchain wallet addresses like EVM wallets, Cosmos wallets, you should use keyType as . Read EcdsaSecp256k1RecoveryMethod2020

Register a DID

Registers a Signed DID Document in DID registry. The Gas fee (network fee) for this DID registration will be done by applications' walletAddress.

POST/api/v1/did/register

Authorization

Authorization

Header parameters

Body

application/json

didDocument*all of

Did doc to be registered

verificationMethodId*string

Verification Method id for did registration

Example: "did:hid:testnet:........#key-${idx}"

clientSpecstring

IClientSpec 'eth-personalSign' or 'cosmos-ADR036'

Example: "eth-personalSign"

signaturestring

Signature for clientSpec

Example: "afafljagahgp9agjagknaglkj/kagka="

Response

201400

DID Registred

Body

application/json

did*string

Did document id

Example: "did:hid:namespace:......................."

registrationStatus*string

Did document registration status

Example: "COMPLETED/PROCESSING"

metaData*all of

metaData contaning initial didDocument

transactionHash*string

Transaction Has

Example: "XYAIFLKFLKHSLFHKLAOHFOAIHG.........."

Request

JavaScriptCurlPython

const response = await fetch('/api/v1/did/register', {
    method: 'POST',
    headers: {
      "Authorization": "Bearer JWT",
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "didDocument": {
        "@context": [
          "https://www.w3.org/ns/did/v1"
        ],
        "id": "did:hid:method:......",
        "controller": [
          "did:hid:method:......"
        ],
        "alsoKnownAs": [
          "did:hid:method:......"
        ],
        "verificationMethod": [
          {
            "id": "did:hid:testnet:z28ScfSszr2zi2Bd7qmNE4mfHX5j8nCwx4DBF6nAUHu4p#key-1",
            "type": "EcdsaSecp256k1RecoveryMethod2020",
            "controller": "did:hid:method:.............."
          }
        ],
        "authentication": [
          "did:hid:method:......"
        ],
        "assertionMethod": [
          "did:hid:method:......"
        ],
        "keyAgreement": [
          "did:hid:method:......"
        ],
        "capabilityInvocation": [
          "did:hid:method:......"
        ],
        "capabilityDelegation": [
          "did:hid:method:......"
        ]
      },
      "verificationMethodId": "did:hid:testnet:........#key-${idx}"
    }),
});
const data = await response.json();

Response

201400

{
  "did": "did:hid:namespace:.......................",
  "registrationStatus": "COMPLETED/PROCESSING",
  "metaData": {
    "didDocument": {
      "@context": [
        "https://www.w3.org/ns/did/v1"
      ],
      "id": "did:hid:method:......",
      "controller": [
        "did:hid:method:......"
      ],
      "alsoKnownAs": [
        "did:hid:method:......"
      ],
      "verificationMethod": [
        {
          "id": "did:hid:testnet:z28ScfSszr2zi2Bd7qmNE4mfHX5j8nCwx4DBF6nAUHu4p#key-1",
          "type": "EcdsaSecp256k1RecoveryMethod2020",
          "controller": "did:hid:method:..............",
          "blockchainAccountId": "eip155:1:0x19d73aeeBcc6FEf2d0342375090401301Fe9663F"
        }
      ],
      "authentication": [
        "did:hid:method:......"
      ],
      "assertionMethod": [
        "did:hid:method:......"
      ],
      "keyAgreement": [
        "did:hid:method:......"
      ],
      "capabilityInvocation": [
        "did:hid:method:......"
      ],
      "capabilityDelegation": [
        "did:hid:method:......"
      ],
      "service": [
        {
          "id": "did:hid:testnet:z23dCariJNNpMNca86EtVZVvrLpn61isd86fWVyWa8Jkm#linked-domain",
          "type": "LinkedDomains",
          "serviceEndpoint": "https://stage.hypermine.in/studioserver/api/v1/org/did:hid:testnet:......................"
        }
      ]
    }
  },
  "transactionHash": "XYAIFLKFLKHSLFHKLAOHFOAIHG.........."
}

Request Parameters

• didDocument : DID documented generated using /api1/v1/did/create API

• verificationMethodId : Verification Method id of referred verification method in the didDocument

Optional Parameters

• clientSpec : Wallet specifications which are used to sign the didDocument string. Use eth-personalSign for Metamask and cosmos-ADR036 for Keplr wallet. Learn more about client specifications here.

• signature: If didDocument is signed using client wallets (Metamask or Keply) then pass the signature hex string.

Note: Read how to use Metamask to create Hypersign DID.

Resolve a DID

Given a DID Id (example: did:hid:testnet:0x123123123123), this API will resolve the corresponding DID Document from the DID registry (or Hypersign Blockchain).

GET/api/v1/did/resolve/{did}

Authorization

Authorization

Path parameters

did*string

Header parameters

Response

200

DID Resolved

Body

application/json

didDocument*all of

Resolved Did Document

didDocumentMetadata*all of

Resolved didDocumentMetadata

Request

JavaScriptCurlPython

const response = await fetch('/api/v1/did/resolve/{did}', {
    method: 'GET',
    headers: {
      "Authorization": "Bearer JWT"
    },
});
const data = await response.json();

Response

200

{
  "didDocument": {
    "@context": [
      "https://www.w3.org/ns/did/v1"
    ],
    "id": "did:hid:method:......",
    "controller": [
      "did:hid:method:......"
    ],
    "alsoKnownAs": [
      "did:hid:method:......"
    ],
    "verificationMethod": [
      {
        "id": "did:hid:testnet:z28ScfSszr2zi2Bd7qmNE4mfHX5j8nCwx4DBF6nAUHu4p#key-1",
        "type": "EcdsaSecp256k1RecoveryMethod2020",
        "controller": "did:hid:method:..............",
        "blockchainAccountId": "eip155:1:0x19d73aeeBcc6FEf2d0342375090401301Fe9663F"
      }
    ],
    "authentication": [
      "did:hid:method:......"
    ],
    "assertionMethod": [
      "did:hid:method:......"
    ],
    "keyAgreement": [
      "did:hid:method:......"
    ],
    "capabilityInvocation": [
      "did:hid:method:......"
    ],
    "capabilityDelegation": [
      "did:hid:method:......"
    ],
    "service": [
      {
        "id": "did:hid:testnet:z23dCariJNNpMNca86EtVZVvrLpn61isd86fWVyWa8Jkm#linked-domain",
        "type": "LinkedDomains",
        "serviceEndpoint": "https://stage.hypermine.in/studioserver/api/v1/org/did:hid:testnet:......................"
      }
    ]
  },
  "didDocumentMetadata": {
    "created": "2023-01-23T13:45:17Z",
    "updated": "2023-01-23T13:45:17Z",
    "deactivated": "false",
    "versionId": "095A65E4D2F9CA2AACE0D17A28883A0E5DDC1BBE1C9BF9D............."
  }
}

Fetch all DIDs for your apps

GET/api/v1/did

Authorization

Authorization

Query parameters

Header parameters

Response

200404

DID List

Body

application/json

totalCount*number

totalCount

Example: 12

data*array of Did (object)

data

Request

JavaScriptCurlPython

const response = await fetch('/api/v1/did', {
    method: 'GET',
    headers: {
      "Authorization": "Bearer JWT"
    },
});
const data = await response.json();

Response

200404

[
  {
    "totalCount": 12,
    "data": [
      "did:hid:testnet:............"
    ]
  }
]

Update a DID

Update a DIDDocument

PATCH/api/v1/did

Authorization

Authorization

Header parameters

Body

application/json

didDocument*all of

Did doc to be updated

deactivate*boolean

Field to check if to deactivate did or to update it

Example: false

verificationMethodId*string

Verification Method id for did updation

Example: "did:hid:testnet:........#key-${idx}"

clientSpecstring

IClientSpec 'eth-personalSign' or 'cosmos-ADR036'

Example: "eth-personalSign"

signaturestring

Signature for clientSpec

Example: "afafljagahgp9agjagknaglkj/kagka="

Response

200400404

DID Updated

Body

application/json

transactionHash*string

Transaction Has

Example: "XYAIFLKFLKHSLFHKLAOHFOAIHG.........."

Request

JavaScriptCurlPython

const response = await fetch('/api/v1/did', {
    method: 'PATCH',
    headers: {
      "Authorization": "Bearer JWT",
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      "didDocument": {
        "@context": [
          "https://www.w3.org/ns/did/v1"
        ],
        "id": "did:hid:method:......",
        "controller": [
          "did:hid:method:......"
        ],
        "alsoKnownAs": [
          "did:hid:method:......"
        ],
        "verificationMethod": [
          {
            "id": "did:hid:testnet:z28ScfSszr2zi2Bd7qmNE4mfHX5j8nCwx4DBF6nAUHu4p#key-1",
            "type": "EcdsaSecp256k1RecoveryMethod2020",
            "controller": "did:hid:method:.............."
          }
        ],
        "authentication": [
          "did:hid:method:......"
        ],
        "assertionMethod": [
          "did:hid:method:......"
        ],
        "keyAgreement": [
          "did:hid:method:......"
        ],
        "capabilityInvocation": [
          "did:hid:method:......"
        ],
        "capabilityDelegation": [
          "did:hid:method:......"
        ]
      },
      "deactivate": false,
      "verificationMethodId": "did:hid:testnet:........#key-${idx}"
    }),
});
const data = await response.json();

Response

200400404

{
  "transactionHash": "XYAIFLKFLKHSLFHKLAOHFOAIHG.........."
}

Request Parameters

• didDocument : DID documented to be updated

• verificationMethodId : Verification Method id of referred verification method in the didDocument

• deactivate : true is you want to deactivate this DID, false otherwise.

Optional Parameters

• clientSpec : Wallet specifications which are used to sign the didDocument string. Use eth-personalSign for Metamask and cosmos-ADR036 for Keplr wallet. Learn more about client specifications here.

• signature: If didDocument is signed using client wallets (Metamask or Keply) then pass the signature hex string.