Installing CryptoPro CSP on every laptop, distributing tokens, chasing browser plug-in bugs after updates—every manager knows this pain. On average, a company spends 2-3 days signing a single document via courier, while cloud signing reduces it to 3-5 minutes. A typical company processes 50 to 200 documents per month—each requiring 2 to 4 hours of manual work. By switching to cloud signing, you can save $3,000 to $12,000 per month in labor costs alone. We offer a different path: cloud electronic signature services. They remove the dependency on a specific workplace and allow flexible signing flows with multiple participants, including counterparties. Savings on a single document reach 95%—from $2.50 per document traditionally to $0.10 with cloud signing. Order a turnkey integration in 2–3 weeks—contact us for a consultation.
Which e-signature service to choose for Bitrix24?
| Service | Signature Type | API | Best For |
|---|---|---|---|
| Kontur.Diadoc | QES, UNS | REST | Legally binding EDI with Russian counterparties, roaming between operators |
| SBIS | QES, UNS | REST | EDI + accounting, convenient for companies already in the Tensor ecosystem |
| CryptoPro DSS | QES | REST | Cloud signing without local CSP—key stored on server |
| DocuSign | AES, QES (eIDAS) | REST | International document flow, working with foreign partners |
For formalized documents (UPI, invoices) with Russian counterparties—Diadoc or SBIS. For internal signing without tokens—CryptoPro DSS. For international contracts—DocuSign. Cloud signing via API is 3 times faster than traditional—no need to wait for a courier or scan papers.
How is Bitrix24 integration with e-signature services structured?
The overall scheme is the same for all services; only the API differs:
- The document is generated in Bitrix24 via the document generator (
crm.documentgenerator). - A handler extracts the file via Bitrix24 REST API and passes it to the e-signature service.
- The service starts the signing flow—notifies signers.
- Signers work in the e-signature service interface (or mobile app).
- A webhook from the service reports completion.
- The signed document + signature file are uploaded back to Bitrix24.
The connecting link is a server-side handler (webhook receiver). In a simple case—a PHP script on a hosting. For reliable operation under high load—a task queue via Redis or RabbitMQ with guaranteed delivery and retries on errors. According to our data, implementing integration reduces the overall deal closing cycle by 30–40%.
Integration with Kontur.Diadoc: full cycle
Diadoc is the largest EDI operator in Russia, and it's the one most often linked with Bitrix24. REST API is available at https://api.kontur.ru/diadoc/v1/. Let's examine the implementation in detail.
Authentication
Two-stage: first POST /Authenticate with login/password or certificate, then the obtained token is passed in the Authorization: DiadocAuth ddauth_api_client_id={client_id}, ddauth_token={token} header. The token lives for 1 hour. In middleware, we cache it and refresh automatically 5 minutes before expiration—otherwise requests will start failing with 401 in the middle of the workday.
Sending a document for signature
- Get the file from Bitrix24:
crm.documentgenerator.document.get. - Identify the organization box:
GET /GetMyOrganizations. - Find the counterparty in Diadoc:
GET /GetCounteragent?myOrgId={id}&counteragentOrgId={id}. - For formalized documents (UPI, act, invoice)—
POST /GenerateTitleXml, Diadoc requires XML in Federal Tax Service format. - Send:
POST /PostMessagewith the attached document and type.
For non-formalized documents (contracts, supplementary agreements) XML is not needed—the file is passed as is.
Tracking status
Diadoc supports two mechanisms:
- Polling—
GET /GetDocflowEvents?afterEventId={id}—get events after a given ID. - Webhook subscriptions—notifications when status changes via partner access.
In practice, Diadoc webhooks can be delayed by minutes under peak loads. A reliable scheme: webhook as a trigger for immediate check, polling every 5 minutes as a fallback. This way events are not lost and the API is not overloaded with unnecessary requests.
Retrieving the signed document
GET /GetMessage?boxId={boxId}&messageId={msgId}&entityId={entityId}
The response contains all versions of the document, signatures of each party, and timestamps. We extract the signed version and signature file (.sig), upload to Bitrix24 via disk.file.upload, and attach to the deal.
Rejection of signature
The counterparty can request clarification or reject the document. Diadoc forwards the event with a comment. The handler creates a task for the manager in Bitrix24 (tasks.task.add) with the rejection text and moves the deal back to the revision stage via crm.deal.update.
Signing flows with multiple participants
Real document flow is not a single signature. Typical scenarios:
Sequential signing: your side signs first, then the counterparty. Order is strictly fixed.
Parallel signing: both sides sign a reconciliation statement independently.
Signing with internal approval: before the manager signs, the document is approved by a lawyer and CFO. Approval uses UNS (Unqualified Electronic Signature), final signature uses QES. In a typical project, up to 5–7 approval stages are defined.
In service APIs, a flow is described by a set of steps with participants, action type, and order:
{
"document_id": "doc-456",
"workflow": [
{"step": 1, "action": "approve", "participants": ["[email protected]"], "type": "sequential"},
{"step": 2, "action": "sign", "participants": ["[email protected]"], "type": "sequential"},
{"step": 3, "action": "sign", "participants": ["[email protected]"], "type": "sequential"}
]
}
What is stored in Bitrix24 after signing?
After the cycle ends, the CRM should contain:
- Original document (PDF)
- Detached signature file (.sig)—CAdES or XAdES
- Signing protocol—who, when, with which certificate
Files are uploaded to Bitrix24.Disk in the structure Signed documents / [Year] / [Month] / [Deal number]. Custom fields of the deal record the signing date, document number in the EDI system, and status.
Why is cloud signing more profitable than traditional?
Cloud signing via API reduces signing time from 2–3 days to 3–5 minutes, cuts labor costs by 80%, and does not require installing CryptoPro CSP on every computer. With typical monthly volumes of 50–200 documents, the cost savings range from $2,500 to $10,000 per month.
Notifications and pipeline automation
Each document status change in the e-signature service is reflected in Bitrix24:
- Notification in chat (
im.notify.system.add)—to the responsible manager - Deal stage movement (
crm.deal.update)—automatically when both sides sign - Comment in timeline (
crm.timeline.comment.add)—with event details - Task on rejection (
tasks.task.add)—to the manager for document revision
The manager does not track statuses manually—the system itself notifies and moves the deal through the pipeline.
What is included in the work when ordering integration?
- Requirement analysis and service selection
- API key setup and test environment configuration
- Development of handlers for sending and receiving webhooks
- Integration of the "Send for signature" button in the deal card
- Creation of scripts for multi-user flows
- Full testing with real documents and counterparties
- Documentation preparation and user training
- Technical support for 30 days after launch
Implementation stages
| Stage | What we do | Timeline |
|---|---|---|
| Requirement analysis | Service selection, API comparison, legal aspects | 2–3 days |
| Service setup | Obtain API keys, register boxes, test environment | 1–2 days |
| Handler development | Document sending, webhook reception, status mapping, task queue | 5–7 days |
| CRM integration | "Send for signature" button in deal card, pipeline automation | 3–4 days |
| Signing flows | Approval chains, parallel and sequential branches | 2–3 days |
| Testing | Full cycle with test counterparty, rejections, re-sends, edge cases | 3–5 days |
Cloud electronic signature through an external service removes dependency on a specific computer. A manager sends a document from the deal card, the counterparty signs in the EDI operator interface, and the signed version automatically returns to CRM. No tokens on each workstation, no scanner, no waiting for a courier. Get a consultation for your project—we will assess the scope of work in one day.