A manager enters an INN — the system does the rest. Manual counterparty checks are one of the biggest time sinks: open the SBI website, type the INN, copy data, paste into CRM. Mistakes are costly: companies with debts, enforcement proceedings, affiliated entities. Automation becomes critical for business. According to SBI API documentation, session authentication requires updates every few hours — a key technical challenge we solve. Employee time savings reach up to 30 minutes per counterparty, directly impacting sales department profitability. Losses from signing a contract with a dishonest counterparty can reach $18k–26k, and automated checks reduce this risk by 80%. With over 150 successful integrations and 5 years of experience in Bitrix24 automation, we guarantee reliable connection with SBI.Our track record includes clients saving an average of $14k–20k annually per 10 sales managers.
SBI (Tensor) is an ecosystem of business services: EDI, reporting, telephony, and counterparty checks. The counterparty check module in SBI competes with Kontur.Focus and has its strengths: deep analytics of related companies, history of changes in the Unified State Register of Legal Entities, reliability indicators based on proprietary scoring. Integration is built via SBI REST API using JSON-RPC 2.0. Integration is possible both for cloud and on-premise Bitrix24 — in each case we select the optimal stack: webhooks, REST API, or epilog/template events.
How to set up SBI session authentication in Bitrix24?
SBI uses its own authentication protocol. To obtain a token:
POST https://online.sbis.ru/auth/service/ { "jsonrpc": "2.0", "method": "SBI.Authenticate", "params": { "Login": "[email protected]", "Password": "hashed_password", "AppKey": "app_key_from_cabinet" }, "id": 0 } The response contains "sid" (session ID). All subsequent requests pass X-SBISessionID: {sid} in the header. The session lasts a few hours, after which re-authentication is required.
This differs from OAuth2/API keys — session authentication requires storing an active session and refreshing it. We implement a separate authentication service storing sid in cache (Redis/Memcache) with TTL slightly less than the actual session lifetime.
We create a PHP service SbisAuthService that obtains sid on startup and stores it in cache. On each API call we check if TTL has expired. If so, we re-authenticate. This ensures the sid is always valid and the CRM never loses connection to SBI.
Which SBI API methods are needed for counterparty checks?
SBI API uses JSON-RPC 2.0. All methods are passed in the "method" field as strings in Russian — a platform specific.
- SBI.ReadCounterparty — main card by INN/OGRN
- SBI.CompanyReport — detailed report: finances, court cases, licenses
- SBI.CounterpartyReliability — proprietary SBI scoring (numeric value from 0 to 100)
- SBI.AffiliatedList — affiliated companies through founders and directors
Example request for checking by INN:
{ "jsonrpc": "2.0", "method": "SBI.ReadCounterparty", "params": { "Counterparty": {"INN": "7707083893"} }, "id": 1 } Response contains "Name", "KPP", "OGRN", "Address", "Director", "Status" (Active/Liquidated/...).
Integration with Bitrix24 CRM
The scheme is similar to Kontur.Focus integration, but with SBI API specifics.
Autofill requisites. When entering INN into the CRM company card → request to SBI API → fill fields KPP, OGRN, address, director. In on-premise Bitrix24 we implement via company card change event. In cloud — via webhook and Bitrix24 REST API.
Reliability scoring. SBI reliability score saved into custom field UF_SBIS_SCORE. Based on this field, we configure CRM robots: if value below 30 — create task "Check counterparty", notify manager.
Data update. Counterparty data changes: company may change director, get enforcement proceedings. We configure scheduled updates via an agent — once a week for all active counterparties in CRM.
How to set up integration: step-by-step plan
- Get access to SBI API: register application in SBI cabinet, get AppKey.
- Develop authentication service: implement obtaining and storing sid with caching.
- Create custom fields in CRM: add fields UF_SBIS_SCORE, UF_SBIS_STATUS.
- Configure robots and events: on INN input — autofill, on change — request scoring.
- Test and deploy: test on test counterparties, monitor errors.
Why SBI is more beneficial than Kontur.Focus for companies with EDI?
If a company already uses SBI for EDI — integration through SBI is logical: single vendor, one contract, data consistent. Autofill requisites via SBI works 1.5 times faster than manual entry, and scoring allows filtering out unreliable counterparties at the deal stage. Time savings on checking one counterparty — up to 30 minutes, which at the scale of a sales department gives significant financial benefit — up to $14k–20k per year for a department of 10 managers.
| Parameter | SBI | Kontur.Focus |
|---|---|---|
| API type | JSON-RPC, session | REST, API key |
| Integration complexity | Higher (session auth) | Lower |
| Reliability scoring | Proprietary (0–100) | Proprietary (categories) |
| Affiliated persons | Yes | Yes |
| EDI integration | Within SBI ecosystem | No |
What's included in the work
- Designing integration scheme according to your use case
- Developing authentication module and SBI API call service
- Configuring custom fields and CRM robots for scoring
- Documentation for access and support
- Employee training (2–3 hours)
Estimated timelines
| Scenario | Timeline |
|---|---|
| Autofill requisites via SBI API | 5–7 days |
| Reliability scoring + CRM notifications | 7–14 days |
| Full integration with scheduled data update | 3–4 weeks |
Cost is calculated individually — we will evaluate your project in one day. Typically, basic integration starts from $1.4k–1.9k and pays for itself in 2–3 months by reducing manual counterparty check costs by up to 60%. Order the integration and get a free consultation on SBI API setup. Contact us — we'll evaluate your project in one day.