Skip to content

  • Documentation
    • Web App – OKdokument API
    • Signatus Mobile App
  • 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

6. Examples

  • Postman examples
View Categories
  • Home
  • Documentation
  • Web App - OKdokument API
  • 5. Configuration of the signing process
  • 5.6 Multi-round signing with PDF with signature acrofields

5.6 Multi-round signing with PDF with signature acrofields

In multi-round signing with PDF with acrofields (and other active elements) we can also define available signature acrofields. Within the registration of new signature Request we use parameter allowedFields:SIGNATURE, in example value _sigAcrofield1_.

It is possible pre-fill the other active elements, like in example before.

{
    "signatureRequestId": "1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8",
    "expirationTime": "1702288000000",
    "sendInfoURL": "http://api.okdokument/info",
    "resulturl": "https://okdokument.com/",
    "allowedFields": {
        "SIGNATURE": "_sigAcrofield1_"
    },
    "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"
    }
}

For the next round of signature, the same rules as for PDF with tags. Portal has to:

  • Register new signatureRequestId – if generated by OKdokument API it will be new random value, if pre-filled by Portal, new ID must be used
  • Reference to document ID – signed document from the first round of signing is stored in internal OKdokument API storage. Use document ID as a reference of the document (filedata with document content is not needed)
  • Change state – after signing the document in the first round, the document changes the state to “signed”. It is needed to change the document state to “tosign” in order to sign the document in the next round of signing
  • Change allowedFields:SIGNATURE to value _sigAcrofield2_

After first round of signing are all active elements in the PDF (not signature acrofields) unavailable for further editing. That’s because any changes to the document after first signature are not allowed. That’s why in the second signature Request there is no need to fill/use the parameter fieldConfig.

{
    "signatureRequestId": "1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8",
    "expirationTime": "1702288000000",
    "sendInfoURL": "http://api.okdokument/info",
    "resulturl": "https://okdokument.com/",
    "allowedFields": {
        "SIGNATURE": "_sigAcrofield2_"
    },
    "rules": {
        "signAnywhereEnabled": false
     },
    "id": "y7Ki_u1mrUwijfb-o_S1JiphSsoXya8iypH380F",
    "changeState": "tosign"
}
Updated on 21/03/2025
5.5 One-round signing with PDF with signature acrofields5.7 Accessing document after inserting OTP
  • Documentation
    • Web App – OKdokument API
    • Signatus Mobile App
  • Contact Us
Proudly powered by WordPress