Verify a Credential using cheqd Studio.
Once you have issued your credential and have a JWT as part of the credential proof, you can use the /credential/verify API 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/verify API, and the API will give you a response including the following verification policies:
Whether the Credential has been tampered
Whether the Credential has a valid issuance date
Whether the Credential has expired
Whether the Credential Status is valid
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.
Verifiable Credential to be verified as a VC-JWT string or a JSON object.
Custom verification policies to execute when verifying credential.
Policy to skip the issuanceDate (nbf) timestamp check when set to false.
Policy to skip the expirationDate (exp) timestamp check when set to false.
Policy to skip the audience check when set to false.
The request was successful.