Credential
Verifiable Credential
Last updated
Verifiable Credential
Last updated
Credentials will be issued based on a template and will be stored in the user's wallet. Each credential has a specific issuer and belongs to a specific user. Therefore you need to specify the wallet when issuing it.
Credentials expired: Credentials can be expired. You can pass credentialExpiration
to time expired for credentials.
POST
https://api.dentity.com/core/api/v1/programmatic/credential
Issues a credential from a previously defined template. Credential templates can be created in Dentity business site or by using Dentity API.
Name | Type | Description |
---|---|---|
GET
https://api.dentity.com/core/api/v1/programmatic/credential/:id
Fetches credential details
DELETE
https://api.dentity.com/core/api/v1/programmatic/credential/:id
Deletes a credential by ID.
POST
https://api.dentity.com/core/api/v1/credential/proofs/verify
Verify proof that you received when Holder finished OIDC for Verifiable Presentation.
Validation results: The verification process performs a number of validations, each of which may fail independently of the others.
For example, a credential may be expired or revoked, but otherwise perfectly valid.
validation_results
contains an entry for each of the following verification steps:
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Type | Description |
---|---|---|
Name | Description |
---|---|
walletId*
String
User’s wallet address
...rest
String
Fields based on “customFields” Credential Template
credentialExpiration*
Number (Unix time) or null
Credential expiration. NOTE: It must be greater than the current date and less or equal than template expiration.
credentialTemplateId*
String
Template ID
id*
String
Credential ID
id*
String
Credential ID
proofs
Array object
SignatureVerification
The cryptographic proof over the entire Verifiable Credential, specifically using BBS+ Proof of Signature
CredentialStatus
(if supported by credential) Checks if credential has been revoked
SchemaConformance
Ensures credential conforms with its schema. It is possible to issue a credential omitting a required field (as captured in the credential template). If your use case allows this kind of omission, you can ignore this validation entry.
TrustRegistryMembership
(if relevant) Verifies that credential issuer is an authorized member of the credential's governing Trust Registry
IssuerIsSigner
Document issuer
is same DID as document signer. If false, it is not safe to assume that the claimed issuer
actually issued the credential.