Skip to main content
Verification

Revalidate verification

POST/v4/config/ows/verifier/verifications/{verificationId}/revalidation

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.

The verification must have status presentation_acked and a stored VP Token. The time of the Key Binding JWT is checked against the lifetime of the request, not against the time now. The request has no body. The wallet sends the verifier event ows.verifier.verification.revalidated.

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:verifications:update

Path parameters

Response

application/json

The verification history with the new result of the checks.

  • verificationHistoryobject

    The verification history of one OpenID4VP verification request: the request, the response of the wallet and the result of the checks.

    Each member is always in the answer, except dcApiRequest, dcApiProtocol, cryptographicKeyFormat, cryptographicKeyIdentifier and presentationDefinitionSnapshot, which are left out when they have no value. A member without a value has the empty value of its type: "" for a string, 0 for a number, false for a boolean, null for an object or an array.

    A request has no expiry flag. It expires presentationRequestLifetimeSeconds of the verifier configuration after createdAt; the verification status stream reports it as expired.