Links

Verify Presentation

A Verifiable Presentation is a collection of multiple Verifiable Credentials that are being presented by a holder to a verifier. In addition to checking whether the Credentials are untampered, Verifiable Presentation verification also checks that the holder subject DID is valid.

Step 1: Obtain Presentation to Verify

To verify a Credential, you can either pass the full VP-JWT string or a JSON object. These can be either obtained from a Verifiable Presentation presented to the user.

Step 2: Configure Verification Parameters

The user is able to set verification parameters to filter whether they want to verify certain aspects of a Presentation, including:
verifyStatus
  • true (indicates that the user wants to verify the Credential Statuses within the Presentatiuon, requiring a credentialStatus property to be present in at least one Credential within the Presentation)
  • false (Default. Indicates that the user does not want to verify the Credential Status.
fetchRemoteContexts
When dealing with JSON-LD type Verifiable Credentials you also MUST provide the proper contexts within a Credential body. Set this to true ONLY if you want the @context URLs to be fetched in case they are a custom context.
  • true
  • false (default)

Step 3: Execute the API

Use the API below to verify a Presentation
post
/presentation/verify
Verify a Verifiable Presentation generated from credential(s).

This endpoint verifies the Verifiable Presentation generated from credential(s). As input, it can take the Verifiable Presentation JWT as a string or the entire Verifiable Presentation itself.

Parameters
Query
verifyStatus
boolean
If set to `true` the verification will also check the status of the presentation. Requires the VP to have a `credentialStatus` property.
fetchRemoteContexts
boolean
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.
allowDeactivatedDid
boolean
If set to `true` allow to verify credential which based on deactivated DID.
Body
Example
Schema
{
"presentation": {},
"verifierDid": "string",
"makeFeePayment": false,
"policies": {
"issuanceDate": true,
"expirationDate": true,
"audience": false
}
}
application/x-www-form-urlencoded
Responses
200: OK
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.
401: Unauthorized
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.
Last modified 5mo ago