Skip to content

  • Documentation
    • OKdokument API
    • SIGNATUS User Manual
  • Contact Us

1. API concept

  • Overview
  • 1.1 Supported web browsers
  • 1.2 Supported languages
  • 1.3 How to prepare document for signature
  • 1.4 How to use acrofields
  • 1.5 How to use pre-defined signature fields
  • 1.6 Document states
  • 1.7 Storing and deleting documents
  • 1.8 OKDokument API call list
  • 1.9 QR code
  • 1.10 Email and SMS
  • 1.11 Dictionary

2. Core API services

  • 2.1 Authorization
  • 2.2 Create signature request
  • 2.3 Open document
  • 2.4 Information about signing completion
  • 2.5 Result URL
  • 2.6 Download document
  • 2.7 Delete document

3. Additional API services

  • 3.1 List of the documents
  • 3.2 Document Info
  • 3.3 Update Signature Request ID
  • 3.4 Delete Signature Request ID
  • 3.5 Signature request Counter
  • 3.6 Upload document

4. Use cases

  • Overview
  • 4.1 Example 1: Simple one-round signing
  • 4.2 Example 2: One-round signing with redirect url
  • 4.3 Example 3: One-round signing with send info
  • 4.4 Example 4: Multi-Round Signing

5. Configuration of the signing process

  • Overview
  • 5.1 One-round signing with simple PDF
  • 5.2 Multi-round signing with simple PDF
  • 5.3  One-round signing with PDF with tags
  • 5.4 Multi-round signing with PDF with tags
  • 5.5 One-round signing with PDF with signature acrofields
  • 5.6 Multi-round signing with PDF with signature acrofields
  • 5.7 Accessing document after inserting OTP
  • 5.8 Sign document with OTP
  • 5.9 Email
  • 5.10 QR code
View Categories
  • Home
  • Documentation
  • OKdokument API
  • 5. Configuration of the signing process
  • 5.5 One-round signing with PDF with signature acrofields

5.5 One-round signing with PDF with signature acrofields

In this example the PDF document has already been inserted:

  • Signature acrofields
  • Other active elements, like
    • Text field
    • Date field
    • Check box

There is no need to set the state of the document to “tags” in filedata array, because the document already contains signature acrofields. The state of the document should be set to “tosgin”.

For this example, one-round signing there is no need to define which signature field should be available = they all are available.

OKdokument API provides functionality to pre-filled active elements. This is done via array fieldConfig. In our example values:

  • firstName, lastName – are pre-filled, signer can change them
  • date – is pre*filled, signer can’t change the value of the date
  • checkBox1 – is checked, signer can’t uncheck it

Note: name of the active elements must be the same as in the PDF (technical name of the acrofield)

{
    "signatureRequestId": "1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8",
    "expirationTime": "1702288000000",
    "sendInfoURL": "http://api.okdokument/info",
    "resulturl": "https://okdokument.com/",
    "rules": {
        "signAnywhereEnabled": false
     },
    "fieldConfig": [
        {
            "name": "firstName",
            "value": "Jozef",
            "readOnly": false
        },
        {
            "name": "lastName",
            "value": "Novák",
            "readOnly": false
        },
        {
            "name": "date",
            "value": "31.12.2022",
            "readOnly": true
        },
        {
            "name": "checkBox1",
            "value": "1",
            "readOnly": true
        }
    ],
    "filedata": {
        "content": "xyz_JVBERi0xLjc==",
        "state": "tosign"
    }
}
Updated on 21/03/2025
5.4 Multi-round signing with PDF with tags5.6 Multi-round signing with PDF with signature acrofields
  • Documentation
    • OKdokument API
    • SIGNATUS User Manual
  • Contact Us
Proudly powered by WordPress