The Place Kept for a Signature

Keep a spot on the page where an electronic signature will settle, with its name and its frame.

See It in a Real PDF

An Agreement Received and Added to without a Byte Moved

A maintenance agreement somebody else sent, with a signature area, a date and a line of one's own laid over its last page, an annex added after it and an empty place to sign over the signature area, every byte of the agreement left where it was.

Open the PDF The Whole Example

Also shown in: A Two-Page Services Contract · An Interactive Form

Summary

At the foot of a contract, a named place is kept and framed, ready for the seal that settles into it later. That place is the whole of what this draws, and it is already what a sender is usually after: a contract fit to sign, sent to a client who seals it with the software they use every day. Sealing is the step that comes next, and what a signature proves — along with who holds the signing key that makes it — has a page of its own.

Technically

Asked for with "type": "signature_field"

The field is an empty /FT /Sig field and its /Widget annotation, named, its value left for whoever signs, laid over what the other items drew. The form dictionary has /SigFlags set to SignaturesExist, which is how reading software announces a document as one holding a place to sign, and rendering draws of the widget what the border asks for. The request states its name, its rectangle and the settings shared by every field; the certificate, the timestamp and the signed appearance land in the file afterwards, put there by whatever seals it.

Request Schema

Required keys: name, a string; rect. Optional: locks, what signing it freezes: fields, either all, every field of the form and the default, or a set of names written {"only": […]} or {"all_but": […]}; and permits, what stays allowed once it is signed, one of no_changes, form_filling (the form may still be filled in) or annotating, an entry that arrived with PDF 2.0 and so needs "version": "2.0". Optional, shared by every field: read_only, required, no_export, booleans at false; background, the colour behind it; border, an object with a required width, a color (default black, given in light) and a style of "solid" (default), {"dashed": {"lengths": …}}, "beveled", "inset" or "underline"; tooltip and description, strings, absent writing no such entry; mapping_name, a string, the name a submitted form reports the field under; flags, the flag word described on the text field page, absent printing the field and saying nothing else; triggers, one action per moment, the ten of them listed on the text field page; pages, an array of one-based integers, default empty; relative_to. Cross refusal: a CMYK or named-space colour in border.color. seeds, an object, says what the field asks of whoever signs it, each entry written {"value": …, "constraint": …}, constraint being required, kept to or not signed at all, or optional, the default, followed where it can be: filter, the signature handler by the name it registered; sub_filters, the encodings, first acceptable first, among adbe_pkcs7_detached and etsi_cades_detached; digest_methods, among sha256, sha384, sha512 and the four of ISO/TS 32001, sha3_256, sha3_384, sha3_512 and shake256, which write the document as PDF 2.0 with that extension declared; reasons, the reasons offered for signing; legal_attestations, the legal attestations offered; revocation_info, true where the signer checks its certificates for revocation and carries what it found; lock_document, lock, leave or choose, whether the signing dialogue locks the document, PDF 2.0; appearance_filter, the name of the appearance to sign with, PDF 2.0; timestamp, the address of the server a timestamp is asked of; certificate, what the signing certificate has to be, its entries written the same way: subject_names, each a set of attributes the subject has to hold, named by their short names such as CN and O, key_usages, each acceptable usage with the bits it required and the ones forbidden, among digital_signature, non_repudiation, key_encipherment, data_encipherment, key_agreement, key_cert_sign, crl_sign, encipher_only and decipher_only, and url, where a signer holding no such certificate is sent, with url_type beside it. Beside them, kind takes no constraint: "approval", a signature that certifies nothing, or {"certifies": …}, a certification allowing what one of the words of permits says. Every field also takes mark, the label the structure tree claims it by through a node's annotations.

A Whole Request That Creates a PDF

{
  "version": "2.0",
  "items": [
    {
      "type": "signature_field",
      "name": "signature",
      "locks": { "fields": "all", "permits": "no_changes" },
      "rect": {"llx": 72, "lly": 120, "urx": 272, "ury": 180},
      "border": {"width": 0.75}
    }
  ]
}

The line that sends it, in three languages

Form fields

A Field the Reader Types Into A Box the Reader Ticks A List the Reader Picks From Several Buttons, One Answer A Button the Reader Presses

Where to Go Next

Every JSON key of a request, in one page The other twenty-two things you can draw

See the Prices See the Examples