Decentralized Identifiers (DIDs)

Create a DID Document.

post
/did/create

This endpoint creates a DID and associated DID Document. As input, it can take the DID Document parameters via a form, or the fully-assembled DID Document itself.

Authorizations
x-api-keystringRequired
Body
networkstring · enumOptional

Network to create the DID on (testnet or mainnet)

Possible values:
providerIdstringOptional

Identity Provider to create the DID

identifierFormatTypestring · enumOptional

Algorithm to use for generating the method-specific ID. The two styles supported are UUIDs and Indy-style Base58. See cheqd DID method documentation for more details.

Possible values:
verificationMethodTypestring · enumOptional

Type of verification method to use for the DID. See DID Core specification for more details. Only the types listed below are supported.

Possible values:
keystringOptional

The unique identifier in hexadecimal public key format used in the verification method to create the DID.

@contextstring[]OptionalExample: ["https://www.w3.org/ns/did/v1"]
Responses
chevron-right
200

The request was successful.

application/json
post
/did/create

Update a DID Document.

post
/did/update

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.

Authorizations
x-api-keystringRequired
Body
didstringOptional

DID identifier to be updated.

Example: did:cheqd:testnet:7bf81a20-633c-4cc7-bc4a-5a45801005e0
authenticationstring[]Optional

Authentication section of the DID Document.

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.

Responses
chevron-right
200

The request was successful.

application/json
post
/did/update

Import a DID Document.

post
/did/import

This endpoint imports a decentralized identifier associated with the user's account for custodian-mode clients.

Authorizations
x-api-keystringRequired
Body
didstring · uriRequired

DID to be imported

Responses
chevron-right
200

The request was successful.

application/json
post
/did/import

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.

Responses
chevron-right
200

The request was successful.

application/json
post
/did/deactivate/{did}

Fetch DIDs associated with an account.

get
/did/list

This endpoint returns the list of DIDs controlled by the account.

Authorizations
x-api-keystringRequired
Query parameters
networkstring · enumOptional

Filter DID by the network published.

Possible values:
providerIdstringOptional

Filter DID by the provider.

metadatabooleanOptional

Include metadata in response.

createdAtstring · dateOptional

Filter resource by created date

pagenumberOptional

Page number.

limitnumberOptional

Number of items to be listed in a single page.

Responses
chevron-right
200

The request was successful.

application/json
get
/did/list

Resolve a DID Document.

get
/did/search/{did}

Resolve a DID Document by DID identifier. Also supports DID Resolution Queries as defined in the W3C DID Resolution specificationarrow-up-right.

Authorizations
x-api-keystringRequired
Path parameters
didstringRequired

DID identifier to resolve.

Example: did:cheqd:mainnet:7bf81a20-633c-4cc7-bc4a-5a45801005e0
Query parameters
metadatabooleanOptional

Return only metadata of DID Document instead of actual DID Document.

versionIdstring · uuidOptional

Unique UUID version identifier of DID Document. Allows for fetching a specific version of the DID Document. See cheqd DID Method Specification for more details.

Example: 3ccde6ba-6ba5-56f2-9f4f-8825561a9860
versionTimestring · date-timeOptional

Returns the closest version of the DID Document at or before specified time. See DID Resolution handling for did:cheqd for more details.

Example: 1970-01-01T00:00:00Z
transformKeysstring · enumOptional

This directive transforms the Verification Method key format from the version in the DID Document to the specified format chosen below.

Possible values:
servicestringOptional

Query DID Document for a specific Service Endpoint by Service ID (e.g., service-1 in did:cheqd:mainnet:7bf81a20-633c-4cc7-bc4a-5a45801005e0#service-1). This will typically redirect to the Service Endpoint based on DID Resolution specification algorithm.

Example: service-1
relativeRefstringOptional

Relative reference is a query fragment appended to the Service Endpoint URL. Must be used along with the service query property above. See DID Resolution specification algorithm for more details.

Example: /path/to/file
Responses
chevron-right
200

The request was successful.

application/json
get
/did/search/{did}

Export a DID Document.

post
/did/export/{did}

This endpoint exports a decentralized identifier associated with the user's account with the custodied keys.

Authorizations
x-api-keystringRequired
Path parameters
didstringRequired

DID identifier to resolve.

Body
passwordstringOptional
providerIdstringOptional
Responses
chevron-right
200

The request was successful.

application/json
post
/did/export/{did}

Last updated

Was this helpful?