Update 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
AuthorizationstringheaderrequiredYour API key with the prefix
ApiKey:ApiKey <your-api-key>. Get an API key.Scope:
wallet:update
Body
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).
isCredential Encryption Enabled booleantrue: the verifier accepts an encrypteddirect_post.jwtresponse, which a presentation definition with that response mode needs.dc_api.jwtdoes not need it.nullis refused.Example:
truepresentationRequest Lifetime Seconds integer | nullHow long a verification request is valid, in seconds: the
expof the request. At least 3600.nullsets it back to the default, 3600 (the answer then shows0).At least 3600.
Example:
3600
Response
The changed verifier configuration.
globalConfiguration objectThe verifier configuration of the organisation: the settings that each of its verification requests uses.