Bitrix24 REST Development: None of the Ordinary

Why Bitrix24 REST Development Differs from Standard Software

Developing Bitrix24 REST apps is not like typical web development. The platform imposes strict OAuth 2.0 Bitrix24 flows, rate limits, and widget lifecycle policies. According to Bitrix24 REST API documentation (https://dev.1c-bitrix.com/rest_help/), over 700 methods are available, yet many developers underestimate the complexity of token management and error handling. Standard solutions do not address these challenges. Our team, certified by Bitrix and with 10+ years of experience, has built over 50 custom Bitrix24 REST apps for businesses across industries. We focus on Bitrix24 automation to streamline tasks.

Common Problems We Solve

A typical scenario: a sales manager views a deal but sees only manually entered fields. Meanwhile, the accounting system (e.g., 1C) holds years of history — credit limits, claims, orders. None of these details appear in CRM automatically. Switching tabs and copying IDs leads to time loss and data divergence. Many local entities rely on manual data entry, which delays decision-making by up to 2 days per deal.

Our Bitrix24 custom development solutions embed external data directly into Bitrix24 via widgets and the REST API. Every integration is unique. For one client (a wholesale distributor), we reduced data entry time by 80% — from 30 minutes per order to 5 minutes. Average annual savings exceed 200,000 rubles. This client saved 240,000 rubles annually. Our Bitrix24 API integration with 1C ensures real-time data sync.

How We Build Apps: A Step-by-Step Process

1. Discovery – We analyze your workflows and data sources. Duration: 1-2 days. Cost: free assessment.
2. Architecture design – We define OAuth scopes, API endpoints, and widget placement. We choose between mass-market and embedded app types.
3. Development – We code the app using PHP, JavaScript, and Redis for rate limit handling (2 req/sec per app). We implement a Redis-backed request queue with token bucket rate limiting and exponential backoff on QUERY_LIMIT_EXCEEDED.
4. Testing – We simulate 1000+ concurrent requests to ensure stability. We provide a test report.
5. Deployment – We install the app on your portal, configure OAuth, and migrate historical data from 1C.
6. Documentation & training – We deliver API docs, admin guides, and a 30-minute training session for your team.

Mass-Market vs Embedded Apps: Which Is Better?

Embedded apps are better than mass-market apps for internal use because they are 3x faster and half the cost. Mass-market apps are better for selling to multiple clients but require 50% more development effort. Bitrix24 embedded apps are ideal for automating one company's processes. Marketplace apps Bitrix24 serve a wider audience.

Pricing Tiers

Deliverables Included in Every Project

• Source code (PHP/JS) with Git repository
• OAuth client credentials (client_id, client_secret) set up on your portal
• REST API integration with up to 10 custom methods
• Widget (sidebar, detail, or 1-click action) — up to 3 widgets
• 1C synchronization Bitrix24 (bidirectional, daily cron job)
• Rate limit handling (Redis queue, auto-retry, batch requests)
• Documentation: technical overview, admin guide, user manual
• Training: 30-minute online session for up to 5 people
• Support: 6 months of bug fixes and minor updates

Get a Free Consultation

We'll assess your Bitrix24 workflow and propose a solution. No obligations. Typical project turnaround: 2-6 weeks. Turnkey pricing starts at 150,000 rubles for a basic app. CRM integration Bitrix24 with 1C synchronization can save you up to 500,000 rubles annually. Contact us today.

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

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:

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.