Sign a signature request by delegating the signature.

A signer can use this operation to sign a signature request by delegating the signature to the platform.

When using this signature mode, the signature key of the signer is controled by the platform, which acts 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 signer rely on the knowledge of his secret identifier and OTP, or on the control of his public key).

Path Params
string
required

Identifier of the signature request.

Body Params

Authentication information about the signer.

string
required

Secret identifier of the signer (provided by email).

string

OTP of the signer (only required if requiresOTP was set to true for thìs signer).

Responses

400

Invalid request. More details are returned in the response body as a JSON object.

401

Unauthorized. The signer is not an authorized signer (secret signer identifier not found, or invalid OTP).

402

Insufficient credits. The owner of the signature request runs out of signature or anchoring credit.

403

Forbidden. The signature request is not in progress, the maximum number of signatures has been reached or the OTP has expired.

404

Signature request not found.

409

Conflict. The signer has already signed.

429

Too many requests. A minimum delay of 1 second is required after providing an invalid OTP.

Language
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json