Fast Integration with Bitrix24 Local Application
We often receive calls with the same pain: urgently need to connect Bitrix24 with an internal system — 1C, warehouse, or custom CRM — but publishing to Marketplace is unnecessary. The license is limited to one portal, external access partially restricted. We offer a solution: a Bitrix24 local application — it can be configured in 15 minutes and gives full REST API access without bureaucracy. Our engineers have 12+ years in the Bitrix ecosystem, having completed 50+ integration projects, guaranteeing reliability on heavily loaded portals. A local app integrates 50% faster than a Marketplace solution and costs from $1,000 for simple widgets. Saving on integration errors can reach $5,000 per project, and minimizing downtime saves $3,000 annually.
How to Develop a Local Application with OAuth?
- Register the application in portal settings (Applications → Developers → Other → Local Application).
- Choose authorization type: Server (OAuth) for backend or JavaScript (JS SDK) for UI-only.
- Set scopes (crm, task, user, etc.) – plan all rights in advance to avoid reinstallation.
- Develop the code: handle OAuth, implement REST calls, process events.
- Test and deploy: use ngrok for debugging, then move to production.
OAuth 2.0 Authorization Code flow: On first open, Bitrix24 passes AUTH_ID, REFRESH_ID, AUTH_EXPIRES in query string. The server saves the access token, and upon expiration (3600 seconds), refreshes it via POST to https://{domain}/oauth/token/. Refresh token lives 30 days, so cyclic refresh is essential. Libraries like bitrix24-api automate this. More details on Wikipedia. Additional information in official Bitrix24 docs.
How to Choose Between JavaScript and Server Application?
| Parameter |
JavaScript Application |
Server Application |
| Authorization |
Token from URL params/postMessage |
OAuth 2.0 Authorization Code |
| Server part |
Not required |
Required |
| Secret storage |
No secret |
client_secret on server |
| Background work |
No |
Yes (cron, queues) |
| Event subscription |
Via BX24.js |
Via event.bind REST |
| Use case |
UI widgets, dashboards |
Synchronization, automation |
JavaScript type builds an MVP in 1–3 days; server type takes 1–3 weeks for corporate integrations. A local app starts 2–3 times faster than a mass-market one due to no moderation.
Practical Code Examples
JavaScript-Type App minimal example:
<!DOCTYPE html>
<html>
<head>
<script src="//api.bitrix24.com/api/v1/"></script>
</head>
<body>
<div id="app"></div>
<script>
BX24.init(function() {
var auth = BX24.getAuth();
// auth.domain — portal domain
// auth.access_token — token for REST requests
BX24.callMethod('user.current', {}, function(result) {
if (result.error()) {
document.getElementById('app').innerHTML = 'Error: ' + result.error();
return;
}
var user = result.data();
document.getElementById('app').innerHTML = 'Hello, ' + user.NAME + '!';
});
BX24.fitWindow();
});
</script>
</body>
</html>
The JS SDK is loaded from Bitrix CDN; no direct portal connection needed.
Server-Type App OAuth callback in Node.js:
const express = require('express');
const axios = require('axios');
const app = express();
app.get('/', (req, res) => {
const { AUTH_ID, REFRESH_ID, AUTH_EXPIRES, DOMAIN, PLACEMENT } = req.query;
saveTokens({
domain: DOMAIN,
accessToken: AUTH_ID,
refreshToken: REFRESH_ID,
expiresIn: parseInt(AUTH_EXPIRES)
});
res.sendFile(__dirname + '/public/index.html');
});
app.post('/refresh', async (req, res) => {
const { refresh_token, domain } = req.body;
const response = await axios.post(
`https://${domain}/oauth/token/`,
new URLSearchParams({
grant_type: 'refresh_token',
client_id: process.env.CLIENT_ID,
client_secret: process.env.CLIENT_SECRET,
refresh_token
})
);
res.json(response.data);
});
Scope Selection and Limitations
Access scopes determine read/write permissions. Local apps request them at installation. Need new scope? User must reinstall (click update rights button). Plan rights in advance to avoid production disruption.
Expand full scope list
crm — deals, leads, contacts, companies
task — tasks and projects
user — portal users
disk — files and folders
calendar — calendar events
sonet_group — groups and workspaces
catalog — product catalog
sale — store and orders
telephony — calls and telephony
Limitations: Single-portal only, cannot be Marketplace published, portal domain change requires reconfig, no multiple redirect_uri support. For most internal integrations, these don't hinder. If scaling needed later, code transfers to mass-market version easily.
What's Included in Our Service
We deliver a turnkey local application with:
- Analysis: assessment of current processes and external systems
- Architecture: design (microservices or monolith) with performance targets (up to 1000 REST calls/min)
- Implementation: REST methods for sync, webhooks for event processing
- OAuth setup: secure token storage with auto-refresh
- Testing: live portal validation
- Documentation: API description, rights scheme, deployment guide
- Training: admin onboarding (2 hours session)
- Support: 3-month warranty, bug fixes within 24 hours
Pricing starts at $1,000 for simple widgets, $5,000–$15,000 for complex integrations. Average ROI: 200% within 6 months due to automation savings. A typical corporate integration costs around $7,500.
| Task |
Duration |
Cost Estimate |
| Local app setup + basic auth |
0.5–1 day |
$500–$1,000 |
| Simple widget (CRM read-only) |
1–3 days |
$1,000–$3,000 |
| Bi-directional system integration |
1–3 weeks |
$5,000–$10,000 |
| Full corporate application |
1–2 months |
$10,000–$20,000 |
Contact us for a free project assessment. We'll propose the optimal architecture and timeline. Our Bitrix24 developer team can also help with custom Bitrix24 applications and corporate Bitrix24 integrations.
1C-Bitrix Module Development and Setup
The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.
Why is init.php the worst place for business logic?
Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.
Standard Modules: Typical Problems and Solutions
Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.
e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.
Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.
Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.
Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.
How to Design Infoblocks for Performance?
We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.
Custom Module Development
Each module follows the structure /local/modules/vendor.modulename/:
-
install/index.php — setup class, create tables via $DB->RunSQLBatch()
-
lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
-
admin/ — administrative pages using CAdminList, CAdminForm
-
include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
- REST API endpoints via
\Bitrix\Rest\RestManager
The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.
Examples of implemented tasks:
- Campaign management — visual condition builder via
CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
- Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
- Booking system — real-time calendar, locking via
$DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook
Components and Composite Cache
Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.
Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.
What to Check Before Installing a Marketplace Module?
Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.
Migration to D7
When upgrading PHP or switching to a new edition — refactor outdated calls:
-
CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
-
CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
-
CModule::IncludeModule() → Bitrix\Main\Loader::includeModule()
Testing on staging, rollback via git on issues.
According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.
Comparison: Init.php vs Module
| Criterion |
Init.php |
Module with D7 ORM |
| Performance |
Executes on every hit |
Executes only on event |
| Testability |
No autoloading, tests impossible |
Full PHPUnit support |
| Maintainability |
Codebase grows uncontrollably |
Isolated structure, versioning |
| Migrations |
None |
Custom tables, managed via install |
| Caching |
Does not support auto-invalidation |
Tagged caching, event-based clearing |
Module Development Scope and Cost
What is included in module development?
- Technical specification and architectural plan
- Code following PSR-4 and Bitrix code style
- Unit tests (PHPUnit) for business logic
- Integration tests for events and REST API
- Installation, configuration, and API documentation
- Repository and documentation access
- Administrator training for module usage
- 6-month warranty support
Estimated timelines and complexity:
| Complexity |
Examples |
Timeline |
| Simple |
Callback widget, banner system, simple calculator |
3–5 days |
| Medium |
Booking system, product configurator, review module with moderation |
1–2 weeks |
| Complex |
Multi-regionality, custom loyalty program, ERP integration |
2–4 weeks |
| Enterprise |
Marketplace platform, complex business processes with multiple roles |
1–3 months |
Cost is calculated individually — contact us for a project estimate.
Module Testing
Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.
Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.
Practical Examples
Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.
Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.
Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.
We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.
