# Vchasno + Krokul CRM

Yes. Krokul CRM integrates with Vchasno and sends an invoice, act or contract from the deal card to Vchasno.EDO as a ready PDF. The document status (signed, rejected or waiting for the counterparty signature) comes back from Vchasno to Krokul. A signed document moves the deal to the next stage. The setup runs on the Krokul API and webhooks.

**Status:** Via API and webhooks.

## What your team gets

### An act from the deal goes to the counterparty in one click

A manager opens the act on the deal card and clicks «Send to Vchasno». Krokul builds a PDF from your template, names the file by the Vchasno rules with the recipient EDRPOU code and the document number, and uploads it with a POST /api/v2/documents request. Krokul stores the Vchasno document_id on the document.

### The signing status on the document card

Krokul regularly calls POST /api/v2/documents/statuses for documents waiting for a signature. Status 7008 means all signatures are collected. The document gets the «Signed» mark, and the deal moves to the stage you set in the settings. Krokul records a counterparty refusal (7006) in the deal feed and creates a task for the owner.

### You know in advance whether the client uses Vchasno

When a company with an EDRPOU code appears in Krokul, Krokul checks it with a POST /api/v2/check/company request. The is_registered field of the reply becomes a mark on the company card, and the manager knows before the contract whether the document can go electronically.

### Invoices after a won deal with no manual work

In the connection settings, you choose the document types that Krokul sends to Vchasno as soon as they are created. For B2B, this is usually an invoice after the deal moves to «won» and an act after the work is closed. Each sending appears in the sync log with its result.

## What moves between Vchasno and Krokul

| Vchasno | Krokul | Direction | When |
|---|---|---|---|
| Document (POST /api/v2/documents, PDF) | Invoice, act, contract from the deal | Krokul → Vchasno | A click on «Send to Vchasno», or automatically by document type |
| document_id | External key and link on the document | Vchasno → Krokul | Right after the upload |
| Document status (7000–7011) | Mark on the document, entry in the deal feed | Vchasno → Krokul | Polling /documents/statuses on a schedule |
| Status 7008, all signatures | Deal stage | Vchasno → Krokul | When the counterparty has signed |
| Status 7006, refusal | Task for the owner | Vchasno → Krokul | When the counterparty has rejected |
| Company check (check/company, is_registered) | Mark on the company card | Vchasno → Krokul | After a company with an EDRPOU code is created |

## How to connect today

### Your own flow through the Krokul API and webhooks

1. In Vchasno, turn on a plan with API access and create a user token.
2. In Krokul, issue an API key with scopes for deals and documents, and subscribe a webhook to `document.created` or `card.won`. The `x-crm-signature` header confirms each delivery, and you check it against your secret.
3. On the event, read the document through `document/api-read`, take the template from `document/api-print` (it returns HTML), turn it into a PDF and upload it to Vchasno with a POST /api/v2/documents request. Link the returned document_id to the Krokul document through `externalRef/api-upsert`.
4. Reread statuses with POST /api/v2/documents/statuses and write them to the deal feed through `activity/api-create`. On status 7008, move the deal on with a `card/api-updateStatus` call.

### For integrators

Documents, statuses and external keys are also available through the Krokul public API. The `document/api-read` route reads a document, and `externalRef/api-resolve` finds it in Krokul by document_id. The `document.created` and `card.won` webhooks are signed with HMAC-SHA256. You can redeliver an event from the delivery log. A sandbox with demo data and a separate API key lets you test the setup.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul have a Vchasno integration?

Yes. Krokul integrates with Vchasno through its API and webhooks. Documents from a deal go to Vchasno.EDO, the signing status comes back, and the deal moves on when the document is signed.

### How fast does Krokul learn that the counterparty has signed a document?

At the next poll. Vchasno sends no events, so Krokul rereads the statuses of documents waiting for a signature itself and stops once a document is signed or rejected.

### Where does the document PDF come from?

Krokul builds the PDF from the same template you print from the document card. The file goes to Vchasno with the name the Vchasno guide requires.

### What do I need to connect Vchasno?

A Vchasno plan with API access and a user token. The sender of the document in Vchasno is the company that owns the token.

## Limits

The parties sign the document in Vchasno, and Krokul only sends the file and follows the status. The Vchasno API sends no events, so Krokul rereads statuses on a schedule, and the Vchasno guide limits the exchange to ten requests per second per company and files to 15 MB.

## Related services

- [Checkbox](https://krokul.com/en/integrations/checkbox/index.md)
- [Opendatabot](https://krokul.com/en/integrations/opendatabot/index.md)
- [Nova Poshta](https://krokul.com/en/integrations/nova-poshta/index.md)

[Documents and fiscal (Ukraine)](https://krokul.com/en/integrations/category/documents-ua/index.md)

Vchasno is a trademark of its owner. Krokul is not affiliated with Vchasno.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs