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
  • 2. Core API services
  • 2.4 Information about signing completion

2.4 Information about signing completion

OKdokument API is capable of calling Portal backend service about the completion of signing (button Submit or Cancel was clicked by the user). Service url (sendinfo) can by defined in /signatureRequest service. Information about the result of signing is in parameter state. API Server supports a content type format application/json.

The backed service provided by Portal application must be without any kind of authorization. Example can be found in the chapter 4.3 Example 3: One-round signing with send info.

Service specifications:

URLhttps://<host>/sendinfo
MethodPOST
Request bodyString in JSON format
ResponseHTTP 200 if successful

Request example:

POST /<path>/sendinfo HTTP/1.1
Host: <host>
Content-Type: application/json
Content-Length: 149
 
{
    “state”: “signed”,
    “id”: “y7Ki_u1mrUwijfb-o_S1JiphSsoXya8iypH380F”,
    “signatureRequestId”: “1d58a59e-e8f7-4d07-bb99-d3fa39cb58a8”
}

Updated on 25/07/2024
2.3 Open document2.5 Result URL
  • Documentation
    • Web App – OKdokument API
    • Signatus Mobile App
  • Contact Us
Proudly powered by WordPress