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
  • 1. API concept
  • Overview

Overview

The contents of this document serve primarily to software developers and architects. This document describes the basic functionality of OKdokument API and integration options.

In chapters 6 and 7, the different integration options are explained with practical examples that can be tested using postman collections.

OKdokument API works on a JSON REST interface in which the user is authenticated based on the API key. The API key allows the system to be integrated and to access OKdokument API.

In order to access OKdokument API, the API needs to be active.

In addition to the API key, it is also necessary to purchase “signature requests”. One signature Request represents the registration of a unique signatureRequestID through the API. Multiple signatures can be made within a signature Request.

The signing of the document itself happens directly via a web browser, independent of the platform. Signing documents can be done by any means available:

  • Mouse on PC
  • Finger on a touch device
  • Passive stylus
  • Active stylus

Before actually using OKdokument API, we recommend thinking about the following areas:

  1. In which processes will documents be signed digitally?
  2. Where and how is a new document created?
  3. Can the system that prepares the document for signature determine the exact signature placement? (1.3 How to prepare document for signature)
  4. In case of multiple signatures inside a document, will the signatories sign at the same time or at different times and places?
  5. How will the signatory access the url to sign the document? (portal, client zone, email, etc.)
  6. Where will the finalized document be archived? (DMS, CRM, filesystem other)
  7. How will the finalized document be delivered to the signers? (e-mail, client zone etc.)

OKdokument API uses the following services:

Basic API services

  • Create a signature Request
  • Open document
  • Download a document
  • Delete a document
  • Information on signing completion
  • Result URL

Additional API services

  • Document list
  • Update signature Request ID
  • Remove signature Request ID
  • signature Request counter
  • Send document
Updated on 25/07/2024
1.1 Supported web browsers
  • Documentation
    • OKdokument API
    • SIGNATUS User Manual
  • Contact Us
Proudly powered by WordPress