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
  • 4. Use cases
  • 4.4 Example 4: Multi-Round Signing

4.4 Example 4: Multi-Round Signing

Description

The following example shows how the OKdokument API can be used for multi-round signing. In Multi-round signing several signatories can sign at different places and at different times. Each round of signing represents different signature Request.

How it works

The input to the signing process is a PDF document, which contains signature acrofields. Therefore, there is no need to pre-process the document (search for tags and add acrofields).

As this is a two-round signing process, within the Create signature Request we define the allowedFields:SIGNATURE parameter, which tells about which signature field will be

available for the given signature round. This way we can ensure that the signatory signs in the right place. In this case, make a signature field named _SO1_ available.

After signing and confirming the document (or canceling the signing) by the first signer, OKdokument API redirects the signer to the resulturl with the appropriate state.

Before starting the next round of signing, the Portal can save a signed version of the document.

For the next round of signing it is again necessary to create a new signature Request where it is necessary to:

  • Change the status of the document to “tosign”, as the document was in the “signed” state after the first round of signing
  • Add a reference to the document ID. Since the signed document is in the temporary storage of the OKdokument API, it is not necessary to re-upload it.
  • Define available signature field – Signature on _SO2_

After signing and confirming the document (or canceling the signing) by the second signer, OKdokument API redirects the signer to the resulturl with the appropriate status.

In this way, it is possible to insert multiple signatures into a document remotely.

After signing with the last signer, the Portal downloads the finally signed document with the Download document service and then deletes it with the Delete document service.

Figure 20 Multi-round signing
Figure 21 Postman example 4
Updated on 25/07/2024
4.3 Example 3: One-round signing with send info
  • Documentation
    • Web App – OKdokument API
    • Signatus Mobile App
  • Contact Us
Proudly powered by WordPress