These docs are for v1.6.2. Click to read the latest docs for v1.15.1.

Sign a signature request.

Use this operation to register a signature in a signature request.

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.

Path Params
string
required

Identifier of the signature request.

Body Params

Signature to register.

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.

string
required

Public key used to sign.

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 authorized signee as set in the signature request.

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.

string

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

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

string
enum

The type of device the authorized signee used to sign:

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

Secret identifier of the signee (only required if email was set for this signee).

string

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

Responses

400

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

401

Unauthorized. The signee is not an authorized signee (public key or signee 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 suspended, the deadline has been reached, the maximum number of signatures has been reached or the OTP has expired.

404

Signature request not found.

409

Conflict. The signee 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