Send verification request
Sends an OpenID4VP Authorization Request from a stored presentation definition and starts a verification. The wallet takes the DCQL query, the response mode, the signing key and the transaction data template from the presentation definition (`presentationDefinitionId`). The answer is the verification history of the request; its `presentationExchangeId` is the `verificationId` of the other verifier operations.
List verification history
Lists the verification history of the organisation, one page at a time, by `updatedAt` (newest first by default). The answer also has `verificationHistoryStats`, the counters of every verification request of the organisation, whatever the filters.
Read verification history
Returns the verification history of one verification request: its status, the result (`isVerified`), the presented credentials (`presentation`) and the result of each check (`presentationValidity`). Use it after [Send verification request](/docs/openid4vc-api/config-create-digital-wallet-open-id-verification-request-v-3), or when a verifier event of a webhook names the verification.
Delete verification history
Deletes the verification history of one verification request. The read and list operations no longer return it, and it no longer counts in `verificationHistoryStats`. The wallet sends the verifier event `ows.verifier.verification.deleted`.
Stream verification status (SSE)
Streams the status of one verification request over Server-Sent Events, for a live status in your frontend while the holder answers, for example a Digital Credentials API request. The stream sends the current status at once, then a frame for each change, and ends after a final status.
Send data agreement verification request
Sends an OpenID4VP Authorization Request for a data agreement (ISO/IEC TS 27560) of the organisation and starts a verification. The latest revision of the data agreement must have the data exchange profile `OID4VC` and the method of use `data_using_service` (see [Create data agreement](/docs/consent-management-admin-api/config-create-agreement)). The request uses the presentation definition of its `dataExchange.id`, and it carries the data agreement, so the holder sees its terms with the request.
Receive DC API verification response
Takes the response of a Digital Credentials API (DC API) request that your frontend got from the browser, checks it and stores the result in the verification history. Use it only for a presentation definition with `responseMode` `dc_api` or `dc_api.jwt`, or with the version `iso18013_7_annex_c`; with `direct_post` the wallet posts its response itself.
Revalidate verification
Checks the stored response of an answered verification again, for example after the issuer revoked a credential or after you changed the trust sources. The wallet checks each presented credential again (signatures, validity, revocation status, and the trusted list check of the issuer when `requiresTrustedCredentialSigner` is on) and replaces `presentationValidity`, `isVerified`, `presentation` and `holder`. The other members do not change.