Description #
This is the simplest implementation of the API services.
This section provides a practical example of a simple one-round signing process using the Signatus 2 API. It demonstrates how to create an envelope, configure a basic signing flow, and complete the signing process in a single round.
Streamlined 3-Step API Integration for Electronic Signatures. Integrate robust e-signature capabilities into your application with minimal effort. Our API-driven process involves three core interactions:
- POST /api/envelope: Programmatically create a new signature envelope, providing document binaries and relevant metadata.
- GET /sign/{processId}: Redirect the signer to our secure, user-friendly signing interface managed by Signatus
- GET /api/envelopeData/{envelopeId}: Securely download the completed envelope, including signed documents
Request example #
Create envelope dataText :
{
"processes": [
{
"documents": [
{
"reference": "file1"
},
{
"reference": "file2"
}
]
}
]
}HTTP- Click to view HTTP code snippet
POST /app/api/envelope HTTP/1.1
Host: signatus.ana.sk
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJJTGNWSnp4SFkyd1RDcGlLZU5Oa2VmbWZHa1ljUnBtQ1lMMUhsNG13Zm5VIn0.eyJleHAiOjE3NTM5NTQyMDksImlhdCI6MTc1Mzk1MzkwOSwianRpIjoiYzRmNjRmMTYtMGFjZS00MDkzLWEwOTMtZDY0YzUwMmVmNzU4IiwiaXNzIjoiaHR0cHM6Ly9vYXV0aC5hbmEuc2svcmVhbG1zL1NpZ25hdHVzIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6ImYzYmUxYTY2LTU1M2YtNGFlOC04OTUyLTY3OGQ4NTU2ZDAxYiIsInR5cCI6IkJlYXJlciIsImF6cCI6InNpZ25hdHVzIiwic2lkIjoiYTE1MmRkODgtZTJlNi00ZDc3LTk0MGUtNTBjMDNmN2MxZjVjIiwiYWNyIjoiMSIsImFsbG93ZWQtb3JpZ2lucyI6WyIvKiJdLCJyZWFsbV9hY2Nlc3MiOnsicm9sZXMiOlsiUk9MRV9QUk9YWSIsImRlZmF1bHQtcm9sZXMtc2lnbmF0dXMiLCJST0xFX1BPUlRBTCIsIlJPTEVfVVNFUiJdfSwicmVzb3VyY2VfYWNjZXNzIjp7ImFjY291bnQiOnsicm9sZXMiOlsibWFuYWdlLWFjY291bnQiLCJtYW5hZ2UtYWNjb3VudC1saW5rcyIsInZpZXctcHJvZmlsZSJdfX0sInNjb3BlIjoicGhvbmUgZ3JvdXBzIHRlbmFudGlkIHByb2ZpbGUgZW1haWwiLCJlbWFpbF92ZXJpZmllZCI6ZmFsc2UsInRlbmFudGlkIjoiZGVtbyIsIm5hbWUiOiJQYXZvbCBQdW5hIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiZGVtby5hcGkiLCJnaXZlbl9uYW1lIjoiUGF2b2wiLCJmYW1pbHlfbmFtZSI6IlB1bmEiLCJlbWFpbCI6InBhdm9sLnB1bmFAYW5hc29mdC5jb20ifQ.U9mzzxknxxUJyo-8OOzL-VaB7w4PP8ZWJpqv4DwK2DSHwSuduYE0P9gsOK8_UqczcViWcx8w_47CRiPAgVZVe3a0koNlNtZEe0X9qGL326MTPThcZBJwWwD47rTwkXpmZOuHP_KNi34dl2CfHPEGrvabpaMPQ7-2JlTGlE56PzC_HjjNbfc2wb-sJ77_hAnvtdFvlNjRg44q3pHdxYZZUUq7h-ZR-dbirLdeTSP_rB9VViqCTY21ksLIXflUB8_rzq9c7bXzQ1IYcccC4Q69w1AXMK0W08QyZ-9vbGuGtvvzKNcOzGvRkhlX6GM6IofVi9AsmHUagZfZdJjFB4ubRQ
Content-Length: 579
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="dataText"
{
"processes": [
{
"documents": [
{
"reference": "file1"
},
{
"reference": "file2"
}
]
}
]
}
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file1"; filename="Signatus2-API/Test.pdf"
Content-Type: application/pdf
(data)
------WebKitFormBoundary7MA4YWxkTrZu0gW
Content-Disposition: form-data; name="file2"; filename="Signatus2-API/Test2.pdf"
Content-Type: application/pdf
(data)
------WebKitFormBoundary7MA4YWxkTrZu0gW--
Create envelope response :
{
"id": "3f1e7805-840d-4005-91fd-c3c49b69d3d3",
"userId": "demo.api",
"state": "ready",
"envelopetypeid": 4,
"expirationtime": 1753970613145,
"extension": {},
"processes": [
{
"id": "12b91cf4-7ca8-4676-82a5-a3ceda369ecd",
"userId": "demo.api",
"envelopeid": "3f1e7805-840d-4005-91fd-c3c49b69d3d3",
"signer": "signer1",
"state": "ready",
"extension": {},
"sigtype": "bio",
"envelopetypeid": 4,
"tenant": "demo",
"rules": {}
}
],
"type": "inbox",
"product": [],
"contact": {},
"tenant": "demo",
"rules": {}
}Sequence diagram #
This sequence diagram illustrates the interaction between a Portal (initiating system), Signatus2, and a Signer (the end-user) during the process of creating, signing, and retrieving signed envelope.
Where :
- envelopeId = response.id
- processId = response.processes[0].id
