Skip to main content
Verifier configuration

Update verifier configuration

PATCH/v4/config/ows/verifier/configuration

Changes the verifier configuration of the organisation. The change is partial: a member that you leave out keeps its stored value. A change applies to the verification requests that you send after it.

Turn on isCredentialEncryptionEnabled before you create a presentation definition with responseMode direct_post.jwt.

Authorizations

  • Authorizationstringheaderrequired

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

    Scope:wallet:update

Body

application/json

The members to change. A member that the operation does not declare is refused (<name>: unknown field), and a member of the wrong JSON type too (<name>: invalid type).

  • isCredentialEncryptionEnabledboolean

    true: the verifier accepts an encrypted direct_post.jwt response, which a presentation definition with that response mode needs. dc_api.jwt does not need it. null is refused.

    Example:true

  • presentationRequestLifetimeSecondsinteger | null

    How long a verification request is valid, in seconds: the exp of the request. At least 3600. null sets it back to the default, 3600 (the answer then shows 0).

    At least 3600.

    Example:3600

Response

application/json

The changed verifier configuration.

  • globalConfigurationobject

    The verifier configuration of the organisation: the settings that each of its verification requests uses.