Auto-Fill Contractor Requisites in Bitrix24 via Kontur.Focus API

Integrating 1C-Bitrix with Kontur.Focus

Imagine a manager enters a TIN in a CRM card. The system stays silent. They have to open the Kontur.Focus website. They copy the requisites manually. They check risks — 15 minutes per company. With our integration, it all happens in 2 seconds. That's 450 times faster. Our engineers, certified in 1C-Bitrix and with 8+ years of experience, implement this connection turnkey. We have completed 50+ successful integrations. From API setup to embedding into business processes.

Kontur.Focus is a contractor verification service: Unified State Register of Legal Entities/Individual Entrepreneurs, arbitration cases, financial statements, affiliated persons. Integration with 1C-Bitrix is needed where a manager enters a company's TIN into a CRM card or during legal entity registration on a website — and expects the system to automatically pull up requisites and signal risks. We offer a ready-made solution: you get automatic filling of requisites, risk analysis, and notifications — all within your familiar system.

How the Kontur.Focus API Works

Kontur.Focus provides a REST API. Authentication is via an API key in the request parameter ?key={api_key}.

Main methods:

• GET /api/req?req={inn_or_ogrn}&key={key} — search by TIN/OGRN, returns basic requisites
• GET /api/brief?inn={inn}&key={key} — short organization card: status, legal form, address, director
• GET /api/financials?inn={inn}&key={key} — financial indicators (revenue, profit for recent years)
• GET /api/risks?inn={inn}&key={key} — consolidated risk profile: negative signs, sanctions lists

The response is JSON. The status field contains ACTIVE, LIQUIDATING, LIQUIDATED, BANKRUPT. For CRM integration, this field is key: a deal with a liquidating company requires special attention.

Source: Kontur.Focus API documentation

How Auto-Fill of Requisites from Kontur.Focus Works in Bitrix24 CRM

The most common scenario: a manager enters a TIN in a CRM company card. The system queries Kontur.Focus. It automatically fills in KPP, OGRN, legal address, director's full name.

This is implemented via an event handler CRM::ON_BEFORE_COMPANY_UPDATE (on-premise Bitrix24) or via webhooks in cloud Bitrix24. When the TIN field changes, we trigger a request to Kontur.Focus and populate the card fields.

In cloud Bitrix24 via REST API:

// Hook on company change via BX24.callMethod BX24.callMethod('event.bind', { event: 'ONCRMUPDATECOMPANY', handler: 'https://your-app.ru/focus-handler/' // Replace with actual endpoint }); 

On the handler side: we get the TIN from the UF_INN or standard requisite field. We make a request to Focus. Then we update the company card via crm.company.update.

Risk Check and Notifications

Second scenario: contractor check before a deal. We attach a trigger in the Bitrix24 business process. When a deal moves to the "Contract" stage, the risk profile is automatically requested from Kontur.Focus.

If risks.negative_factors contains critical signs (mass address, disqualified director, enforcement proceedings for a large amount) — the deal gets a "requires verification" label. A task is created for the security department.

This is configured via CRM robots (Bitrix24 cloud) or business processes (on-premise). Condition: "if UF_FOCUS_RISK field > threshold value → create task → notify manager".

Why Request Caching Is Critical for Budget

Kontur.Focus is a paid API with a per-plan request limit. With a large CRM (1000+ companies) and frequent card updates, caching is mandatory. Exceeding the request limit leads to additional costs. Without caching, CRM performance degrades.

We cache request results in Redis or in the Bitrix table (\Bitrix\Main\Data\Cache). Cache TTL: 24 hours for basic requisites, 1 hour for status (status can change quickly during liquidation). For forced refresh — a button in the CRM card "Update data from Focus". This reduces API load and saves budget.

Integration During Legal Entity Registration on the Website

For 1C-Bitrix (not Bitrix24): a legal entity registration form. The user enters a TIN. An AJAX request goes to the website endpoint. It queries Kontur.Focus and returns requisites for auto-fill. After registration, we save the contractor status and risk assessment in user properties (b_uts_user).

What's Included in the Work

Timeline Estimates

The cost is calculated individually after analyzing your contractor verification business processes and CRM architecture. Basic integration starts at $1500. Order a turnkey integration with quality guarantee — contact us for a free evaluation. Typical savings: $1000 per month in reduced manual work.