Skip to content

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

  • Authorization
  • Create signature request
  • Upload
  • Open document
  • Information about signing completion
  • Result URL
  • Download document
  • Delete document
  • Rules
  • Document fields configuration
  • Integration Resources & API Documentation

3. Additional API services

  • List of the documents
  • Document Info
  • Update Signature Request
  • Delete Signature Request
  • Signature Request Counter
  • 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
  • 2. Core API services
  • Authorization

Authorization

To ensure the integrity and security of our data, all programmatic requests (except service Open document)must be authenticated using an API Key.


Overview #

Our API uses a custom header-based authentication scheme. Every request to a protected endpoint must include a valid API Key. This key identifies the calling application (the “Principal”) and determines the scope of permissions granted to that caller.

Implementing the API Key #

To authenticate, you must include your key in the x-api-key header of every HTTP request.

Example of x-api-key: 9668716b6_1f40fc92da241684750979ee6cf582f2d5d7d28e18335de05abc54d0560e0f5302860c652bf08d560252a

Updated on 07/05/2026
Create signature request
Table of Contents
  • Overview
  • Implementing the API Key
  • Documentation
    • Mobile App – Signatus
    • Web App – Signatus 2 API
    • Web App – OKdokument API
    • Web App – OKdokument
  • Contact Us
Proudly powered by WordPress