Signing files

• What formats are used to submit files for signature?
• How to pass information about the location of signatures when submitting files?
  • 1. Place signatures at the end of the document 
  • 2. Signature placement on the specified page and coordinates 
  • 3. Signature placement by Signature placement field - Placeholder

What formats are used to submit files for signature?

• In the current version, you can send via API in PDF, DOC, DOCX, XLS, XLSX, JPG, HTML.

• In the HTTP request, the files to be signed are passed in the format - multipart/form-data.

How to pass information about the location of signatures when submitting files?

Signature placement is handled when you send your documents for signature. If using Signi templates, the positions of the signatures are given by the template.

What are the options:

1. Placing signatures at the end of the document

2. Placing signatures on the specified page and coordinates

3. Signature placement according to Signature placement field - Placehoder

1. Place signatures at the end of the document 

The easiest way to place signatures in documents is for Signi to add a separate sheet to the final PDF document at the end of the document and place all signatures there. When the endpoint Create Contract 2.0 > From Document is called, one of the parameters in the settings section is "missing_positions": "append_to_the_end" . See also Example 2 - Placing signatures at the end of a document for more information.

Example of dynamic signature placement.

2. Signature placement on the specified page and coordinates 

When calling the Create Contract 2.0 > From Document endpoint, you can also specify exactly where to place the signature in the positions field for each person. This will typically cover forms where the place to sign is always the same.

• Specify the parameters X, Y, sign_proposer[position][x] sign_proposer[position][y] sign_proposer[position][page] and sign_negotiator[position][x] sign_negotiator[position][y] sign_negotiator[position][page]

• This is the distance of the upper left corner of the signature from the upper left corner of the document, taken to the dimensions of the document being uploaded in %, i.e. the value is between 0 and 100.

• Recommended size of signatures to upload to the signer's profile: from 2034 x 792 to 646 x 298.

• The location of each signatory and signature is specified separately, i.e. there can be any number of signatures on the document, e.g. for multiparty contracts or multiple signatory statutes.

• Conversely, for multiple entries in the positions field, the signature of one signatory is required in multiple places on one document. This is useful, for example, when multiple documents are merged in one PDF and the signer is required to sign on several of them.

3. Signature placement by Signature placement field - Placeholder

Another way to determine the location of signatures directly in the document is by inserting so-called signature location fields, called placeholders in English, at appropriate places in the document. The logic is similar to that of the fields in the templates for mass correspondence, except that values of the type [last name] are not replaced, but the signatures of specific people are replaced. See also Example 2 - Using C - Using signature fields / placeholders.

Field for placing a signature in a document uploaded to Signi.

In the description document

In the document to be signed, you must first place the signature placement field according to the following rules:

• The fields for the placement of individual signatures indicate the texts e.g. "signi-signature-0" , "signi-signature-1", "signi-signature-2", "signi-signature-3" etc. for the first, second and subsequent signature. The numbering of the signatures should correspond to the order in which the document is signed. The field for the first signatory is "signi-signature-0 .

• When calling through the API , unlike for placing signatures in the UI, it is not necessary to follow this naming convention. The field names are arbitrary, you just need to use the same names in the Signi API call afterwards. The only recommendation from Signi developers - don't use spaces, diacritics, special characters in field names, and use hyphens instead of underscores.

• The name text corresponds to the top left corner of the final embedded signature. Title text should appear in white in the document. While the text will remain in the final PDF, it will be overlaid on the signature.

• When placing signatures, it is assumed that the signature is about ⅓ of a page wide and about 16:9 tall . Therefore, it is advisable to insert a table with 2 or 3 columns in the document to place the text. The table should also be coloured white.

• It does not depend on the type of signature - Any type of signature can be inserted in the field for placement in the document - biometric, BankIS SIGN or signature with a certificate for example qualified signature.

• The signature field can be placed in multiple places in the document - One signer will then sign multiple times in the document.

• If a signature needs to be reduced, this can now be set as a workspace property in Signi, not for individual Signi API calls. Contact help@signi.com to set this up.

In JSON

Subsequently, in the signature scenario in JSON in the API call, the corresponding signature location fields are specified for specific people in the positions field in the anchor variable i.e. e.g. signi-signature-00 and signi-signature-02 , see Example 2 - Using C - Using signature fields / placeholders for an example of the full call.

{
        "is_proposer": false,
        "email": "zakaznik@seznam.cz",
        "contract_role": "sign",
        "person_type": "nature",
        "first_name": "John",
        "last_name": "Doe#2",
        "positions": [
          {
            "anchor": "signi-signature-0"
          } 
        ]
    }

Signature location field - placeholder assigned to a specific person in a JSON request to the Signi API.