Verifiable Credential
Last updated
Last updated
Please before proceeding. Once you generated the access_token
, you can pass this token as bearer authorization token in the header for all APIs.
An issuer may issue a to a subject using this API. The credential document is signed by issuer's identity key and its status is registered on the blockchain.
A signed verifiable credential must has signature of the issuer. Any one may verify an issued credential document. The verification result state the following facts:
This document was issued by intended issuer
This document have not been tampered
This document have not been revoked
NOTE: Verifying a credential document is different than verifying a n. Verification result of later, also states that "Only intended subject holds this document and not one else".
Bearer <access_token>
Origin as you set in application cors
Page value
1
Fetch limited list of data
10
Bearer <access_token>
Origin as you set in application cors
Bearer <access_token>
Origin as you set in application cors
credential document
Bearer <access_token>
Origin as you set in application cors
Namespace to be added in vcId.
testnet
Credential status
LIVE / SUSPEND / REVOKE
Credential status Reason
Reason
issuerDid of the credential
Verification Method id for did updation
did:hid:testnet:........#key-${idx}
Bearer <access_token>
Origin as you set in application cors
schemaId for credential Schema
holder did of the credential
issuerDid of the credential
Date in ISOString format
2027-12-10T18:30:00.000Z
Credential Data fields
{"name":"Random name"}
Namespace to be added in vcId.
testnet
Verification Method id for did updation
did:hid:testnet:........#key-${idx}
Persist in edv
true