A signer can use this operation to sign a signature request by delegating the signature to the platform.
This operation is only available when the email of the signer is set: since the secret identifier is sent by email to the signer, he/she can provide it back to authenticate.
When using this signature mode, the signer's identity and signature key is controled by the platform, which act as a trusted third party.
The signature is automatically anchored on behalf of the owner of the signature request.
The signature anchor created is added to the list of signature anchors of the signature request.
This is a publicly accessible endpoint: authentication is not required to delegate a signature
(authentication of the signers, when required, rely on their knowledge of their secret identifier and OTP, or on their control of their public key).
Invalid request. More details are returned in the response body as a JSON object.
Unauthorized. The signer is not an authorized signer (secret signer identifier not found, or invalid OTP).
Insufficient credits. The owner of the signature request runs out of signature or anchoring credit.
Forbidden. The signature request is not in progress, the maximum number of signatures has been reached or the OTP has expired.
Signature request not found.
Conflict. The signer has already signed.
Too many requests. A minimum delay of 1 second is required after providing an invalid OTP.