# Opendatabot + Krokul CRM

Yes. Krokul CRM integrates with Opendatabot. Krokul queries Opendatabot as soon as a manager enters the EDRPOU code of a company, and fills in the full name, address, director, business activity and registration state from the Unified State Register. For companies with open deals, Krokul watches the register for changes and writes them to the card feed. The setup runs on the Opendatabot API together with the Krokul API and webhooks.

**Status:** Via API and webhooks.

## What your team gets

### A new company by EDRPOU code

A manager enters an EDRPOU code in Krokul, Krokul checks the checksum and calls GET /full-company/{code}. The registry block fills the company card with the legal name, address, director name and main business activity. The manager does not copy details from the register by hand.

### Registration state before the contract is signed

The status field of the Opendatabot response shows whether the company is registered, being terminated or already terminated. Krokul shows this state on the company card and warns the manager when a contract or invoice is created for a company that is being terminated.

### A change of director reaches the feed

For companies with open deals, Krokul creates a POST /subscriptions subscription with the company type. On a schedule, Krokul reads GET /history, and each new change, such as a new director or address, appears as an entry in the company feed and a notification to the owner.

### The card updates from the register on request

The «Update from register» button on the company card repeats the /full-company request and shows which fields have changed. The manager decides what to accept, and the previous values stay in the card history.

## What moves between Opendatabot and Krokul

| Opendatabot | Krokul | Direction | When |
|---|---|---|---|
| EDRPOU code (/full-company/{code}) | Company EDRPOU field | Krokul → Opendatabot | A company is created, or «Update from register» |
| Registration data (registry: name, address, director, business activity) | Company card fields | Opendatabot → Krokul | In the reply to the request |
| Registration state (status) | Mark and warning on the company card | Opendatabot → Krokul | In the reply to the request |
| Monitoring subscription (POST /subscriptions) | Company with an open deal | Krokul → Opendatabot | When the company gets a deal |
| Change history (/history) | Entry in the company feed, notification | Opendatabot → Krokul | Polling on a schedule |

## How to connect today

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

1. Get an API key from Opendatabot with the Connect button on its API page, where test access is also available. In Krokul, issue an API key with scopes to read and write companies.
2. Subscribe a Krokul webhook to the `clientCompany.created` event and check the `x-crm-signature` header of every delivery against your secret.
3. On the event, call GET /full-company/{code} with the EDRPOU code of the new company and write the name, address and director to the card through `clientCompany/api-update`.
4. For monitoring, create a POST /subscriptions subscription with the company type, read GET /history on a schedule and add each change to the company feed through `activity/api-create` with the comment type.

### For integrators

Opendatabot publishes an OpenAPI specification for v3 with JSON responses. On the Krokul side, `clientCompany/api-create` rejects a duplicate by EDRPOU code with a 409 response, so autofill never creates a second card. The `clientCompany.created` event arrives as a signed webhook with a delivery log, and a sandbox with demo data lets you test the setup.

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

## Questions and answers

### Does Krokul check a company in the register by EDRPOU code?

Yes, through Opendatabot. Krokul checks the code checksum, then takes the data from the Unified State Register and fills in the company card.

### Which Opendatabot data goes into the company card?

Among other things, the /full-company method returns the full and short name, address, director, main business activity, registration state and founders. Krokul records the details and the state, and the rest is visible in Opendatabot.

### Will Krokul learn that a company has a new director?

Yes, for companies under monitoring. Krokul reads the Opendatabot change history regularly and writes every change to the company feed.

### What do I need to connect Opendatabot?

An Opendatabot API key. You agree the API access terms with Opendatabot itself.

## Limits

Access to the Opendatabot API is arranged with Opendatabot itself, which also gives test access. Opendatabot sends no webhooks, so Krokul fetches monitoring changes by polling the history on a schedule.

## Related services

- [Vchasno](https://krokul.com/en/integrations/vchasno/index.md)
- [Checkbox](https://krokul.com/en/integrations/checkbox/index.md)
- [PrivatBank](https://krokul.com/en/integrations/privatbank/index.md)

[Registers and procurement (Ukraine)](https://krokul.com/en/integrations/category/registers-ua/index.md)

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

Updated: 2026-10-15

---

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