Verify a Credential using Credential Service
Once you have issued your credential and have a JWT as part of the credential proof, you can use the
/credential/verifyAPI to check that the JWT has not been tampered.
To verify a Credential, you can either pass the full Credential body or the JWT proof. These can be either obtained from a Credential that has been issued or from a Verifiable Presentation presented to the user.
The user is able to set verification parameters to filter whether they want to verify certain aspects of a Credential, including:
Simply paste the JWT or the full credential body into the request field of the
/credential/verifyAPI, and the API will give you a response including the following verification policies:
- 1.Whether the Credential has been tampered
- 2.Whether the Credential has a valid issuance date
- 3.Whether the Credential has expired
- 4.Whether the Credential Status is valid
Verify a Verifiable Credential.
This endpoint verifies a Verifiable Credential passed to it. As input, it can take the VC-JWT as a string or the entire credential itself.
If set to `true` the verification will also check the status of the credential. Requires the VC to have a `credentialStatus` property.
When dealing with JSON-LD you also MUST provide the proper contexts. Set this to `true` ONLY if you want the `@context` URLs to be fetched in case they are a custom context.
If set to `true` allow to verify credential which based on deactivated DID.
The request was successful.
400: Bad Request
A problem with the input fields has occurred. Additional state information plus metadata may be available in the response body.
Access token is missing or invalid
500: Internal Server Error
An internal error has occurred. Additional state information plus metadata may be available in the response body.