DaData Integration for Company Details Autocomplete on Your Website

An INN input error is one of the most common issues on legal entity registration forms. A client accidentally transposes digits, and the application goes through with incorrect details. DaData solves this instantly: autocomplete by partial INN or company name. Our experience — 80+ integrations, from online stores to banking personal accounts. Form fill time reduced by 80%, input errors reduced by 95%.

Take a typical case: an online store with a complex counterparty registration form. Manually filling 12 fields takes 3–5 minutes; with autocomplete it takes 30 seconds. DaData under the hood makes a single request to EGRUL and returns clean JSON. No need to parse FNS XML.

DaData is the de facto standard for company details autocomplete on Russian websites. The service can return a list of companies with full details based on a partial INN or name: INN, OGRN, KPP, legal address, CEO name, status (active/liquidated). Similarly for banks — by BIC it returns bank name, correspondent account, address.

What Data Does DaData Return?

DaData is a suggestion service (analogous to Google Places, but for Russian details). It queries EGRUL/EGRIP and Central Bank of Russia data in real time. In JSON response: for legal entities — inn, kpp, ogrn, name, address, management, state; for banks — bic, correspondent_account, name. All fields are pre-parsed — no need to parse FNS XML. According to DaData documentation, the free plan allows up to 10,000 requests per day.

How to Get a Token and Start?

Register at dadata.ru, go to Personal Account → API Keys. Two keys: Token (for requests) and Secret (for standardization). For suggestions only Token is needed. Free plan: 10,000 requests per day. Sufficient for most forms.

DaData vs Alternatives

DaData is 5 times faster than direct FNS requests and supports autocomplete by partial query. Direct FNS service returns XML that must be parsed — slow and unreliable. DaData returns ready JSON.

Organization Suggestions and INN Lookup

Endpoint: POST https://suggestions.dadata.ru/suggestions/api/4_1/rs/suggest/party. Example in Laravel combining suggestion and exact INN lookup:

$response = Http::withHeaders([
    'Authorization' => 'Token ' . config('services.dadata.token'),
    'Content-Type'  => 'application/json',
])->post('https://suggestions.dadata.ru/suggestions/api/4_1/rs/suggest/party', [
    'query'  => $query,
    'count'  => 5,
    'status' => ['ACTIVE'],
]);
$suggestions = $response->json('suggestions', []);

// Exact INN lookup
$response = Http::withHeaders([...])->post('https://suggestions.dadata.ru/suggestions/api/4_1/rs/findById/party', [
    'query' => '7736207543',
]);
$party = $response->json('suggestions.0.data');

Response for one organization:

{
  "value": "OOO \"YANDEKS\"",
  "unrestricted_value": "OOO \"YANDEKS\"",
  "data": {
    "inn": "7736207543",
    "kpp": "770401001",
    "ogrn": "1027700229193",
    "name": {
      "full_with_opf": "OBSHCHESTVO S OGRANICHENNOY OTVETSTVENNOST'YU \"YANDEKS\""
    },
    "management": {
      "name": "VOLOZH ARKADIY YUR'YEVICH",
      "post": "GENERAL'NY DIREKTOR"
    },
    "address": {
      "value": "g Moskva, ul L'va Tolstogo, d 16"
    },
    "state": {
      "status": "ACTIVE"
    }
  }
}

When a company is selected from the list, the form auto-fills: INN, KPP, OGRN, legal address, CEO name — all from a single response.

Bank Suggestions (BIK)

Similar endpoint: /suggest/bank or /findById/bank. Example:

$response = Http::withHeaders([
    'Authorization' => 'Token ' . config('services.dadata.token'),
    'Content-Type'  => 'application/json',
])->post('https://suggestions.dadata.ru/suggestions/api/4_1/rs/suggest/bank', [
    'query' => '044525225',
]);
$bank = $response->json('suggestions.0.data');
// $bank['bic']           => '044525225'
// $bank['correspondent_account'] => '30101810400000000225'
// $bank['name']['payment']       => 'Sberbank'

How to Securely Integrate DaData Without Exposing the Token?

If you don't want to expose the token to clients, use a backend proxy. We implement a controller wrapper with caching that accepts requests from the frontend and forwards them to DaData. Your token remains on the server.

Frontend Without Backend Proxy

DaData supports direct requests from the browser. To do this, add your domain to the allowed origins list in your DaData cabinet settings. Then requests go directly from JS:

import { DaDataSuggestions } from 'react-dadata';
import 'react-dadata/dist/react-dadata.css';

<DaDataSuggestions
  token="YOUR_TOKEN"
  type="party"
  onChange={(suggestion) => {
    setInn(suggestion?.data?.inn ?? '');
    setKpp(suggestion?.data?.kpp ?? '');
    setOgrn(suggestion?.data?.ogrn ?? '');
  }}
/>

The react-dadata library is a ready-made React component. Similar components exist for Vue and vanilla JS.

Caching to Save Quota

INN lookups can be cached — company data changes rarely. A simple Laravel example:

$data = Cache::remember("party_{$inn}", now()->addHours(24), function () use ($inn) {
    return $this->fetchFromDadata($inn);
});

Caching reduces quota consumption and speeds up repeated requests. 24-hour TTL is a reasonable compromise.

Typical Implementation Scenario

A legal entity registration form on a website: "INN or company name" field with DaData suggestions. When a selection is made, other fields (KPP, OGRN, address, director) auto-fill. This eliminates input errors and reduces form fill time from 3–5 minutes to 30 seconds.

What's Included in the Work

• Analysis of the form and identification of suggestion types (legal entities, banks, addresses).
• Architecture design: whether a proxy controller and caching are needed.
• Implementation of backend proxy and frontend component (React/Vue/vanilla JS).
• Testing edge cases: sole proprietors, LLCs, liquidated organizations, incorrect INNs.
• Deployment and integration with your system.
• Documentation for usage (code comments, README).
• Team training (30-minute online call).
• Post-release support for 2 weeks.

Integration Process and Timeframes

Basic integration takes 2–4 hours. Complex projects with additional caching — up to 2 days.

Order DaData integration for your website — reduce form fill time by 5 times. Contact us to get a ready solution with proxy and frontend component. We'll evaluate your project and prepare a proposal.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)