Sign a signature request by registering a signature.

post

https://api.woleet.io/v1/signatureRequest/{requestId}/sign

A signer can use this operation to sign a signature request by registering a signature he procuded on his own.

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 register 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

requestId

string

required

Identifier of the signature request.

Body Params

Signature to register.

signature

string

required

Signature of the hashToSign property of the signature request using the public key pubKey, or, if any of signedIdentity or signedIssuerDomain is provided,
signature of SHA256(hashToSign + signedIdentity + signedIssuerDomain) using the public key pubKey.

pubKey

string

required

Public key used to sign.

signedIdentity

string

X500 Distinguished Name representing the signed identity.

If set, the CN (common name) and EMAILADDRESS (email address) attributes must match the common name and email address of the signer as set in the signature request.

signedIssuerDomain

string

Domain name of the identity issuer (ie. of the organization who verified the identity).

If set, the domain name of the identity URL must be included in the signedIssuerDomain domain name.

identityURL

string

Web hook to use to verify the signer's identity.

If set, it is used in place of the identityURL property of the signer to create the signature anchor.

device

string

enum

Type of device used to sign:

SERVER: Woleet.ID Server or equivalent
MOBILE: Woleet.ID Mobile or equivalent
NANO: Ledger Nano S or equivalent

Allowed:

signeeId

string

Secret identifier of the signer (provided by email).

Only required if pubKey was not set for thìs signer.

OTP

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 (public key or 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.

200Signature succesfully registered. The signature anchor created is returned.