How to connect Bitrix24 with 1C, your website and marketplaces via API: scenarios, webhooks and a data exchange architecture.
Bitrix24 integration lets you connect the CRM, 1C, the online store and
Automation eliminates manual work, reduces errors, and gives the business transparent analytics. Bitrix24 is not a standalone tool, but part of the ecosystem. In a typical company, data about customers, orders, payments, and products is stored in different places: CRM, 1C, the online store, marketplaces, and the delivery provider.
If these sources are not synchronized, chaos and manual work arise: the manager copies data from email into the CRM by hand, the accountant re-enters invoices, and the warehouse receives orders with a delay.
Bitrix integration with API helps solve several tasks: a single source of data.
The accounting system becomes the "source of truth" for products, prices and stock, while the CRM holds customers and interaction history.
API makes it possible to update data between them without duplication. Response speed.
When placing an order, the customer immediately sees how many units are in stock and when they will receive the parcel.
If data is pulled from 1C into the CRM and back automatically, no department wastes time. Reduced errors.
Manual data transfer makes errors easy.
Integration eliminates duplication and outdated data. Complete analytics.
Management receives reports from inquiry to cash:
Integration should follow business processes, not the other way around.
The business process management (BPM) concept says:
If you do not understand where operations start and end in Bitrix24 and neighboring systems, API exchange will turn into a set of "patches." Analysis and the "as-is" model
At the first stage, the current flow is described:
These steps are drawn in BPMN notation or as a simple table.
It is important to identify "bottlenecks": duplicated information, gaps and delays.
The "to-be" model and ownership boundaries
For example, in the new scheme, a lead is automatically created in the CRM after the form on the website is filled out.
The deal is immediately linked to the product item master from 1C.
The invoice is generated in the CRM but sent to accounting for posting; the payment status is returned, and logistics receives a task via API.
After the model is approved, describe which system each entity lives in:
This is important for correct synchronization.
The platform offers several ways to connect external applications:
This is the simplest option. In the admin panel, you create a unique URL that contains an access key. There are two types of webhooks: Incoming: allow an external system to call any REST API method. For example, a warehouse system can use the URL to create a new deal or update a deal with the provided ID. Outgoing (reverse): the CRM sends data when an event occurs. For example, when a lead is created, the system makes an HTTP request to a specified address and passes parameters. The advantage is simplicity.
The downside is that permissions are harder to control: the key gives access to everything defined in the webhook rules, and webhooks do not scale well for complex scenarios.
Bitrix24 provides a broad set of methods. With the REST API, you can work with deals, contacts, leads, tasks, documents, calendar, drive, payroll, CRM forms, "smart processes," and more. To access the REST API, you register an app in the Bitrix24 developer panel. You receive a client_id and client_secret. You set up OAuth. The app redirects the user to the authorization page, receives a code, and then an access_token and refresh_token.
Send requests to https://{portal_name}.bitrix24.ru/rest/{method}?auth={access_token}, passing JSON parameters. The REST API supports batch requests and reduces the number of network calls, which matters under heavy load.
For reactive scenarios in Bitrix24, you can subscribe to events: deal updates, contact updates, and invoice creation. Events are sent to the specified address (for example, a message broker) or through a WebSocket connection (Push & Pull). This makes it possible to react to changes immediately without polling.
This is not an API, but it is still an integration mechanism. In a CRM funnel or in Smart Processes, you can configure robots: when moving to the next stage, they call a webhook, send a request to 1C, generate a document in EDI, or send data to a chatbot.
Online store ↔ CRM ↔ warehouse ↔ delivery Diagram:
A CMS or e-commerce platform uses the API to create a deal with products, price, and contact details.
If needed, a lead is created or an existing contact is updated. On the "deal created" event, the CRM sends a message to the integration gateway.
The gateway creates a reservation in 1C or another inventory system and returns a response: "in stock / out of stock".
If the product is in stock, the CRM generates an invoice.
The invoice is registered and VAT is calculated automatically through the 1C API.
At the same time, the CRM uses the payment gateway API to send the customer to payment or display a QR code.
After payment, the payment system sends a webhook: payment completed, and the CRM updates the deal status.
The logistics service connects via REST API:
Statuses ("accepted", "in transit", "delivered") arrive in the CRM via
, and the manager sees what is happening. Key points: idempotency matters: if the delivery service accidentally sends a status twice, the CRM must not create duplicates. Asynchronous approach: reservation and dispatch to delivery may be delayed, but the customer should not have to "wait" for this operation. So we show the order number immediately, and delivery information is updated later.
Marketplaces (Wildberries, Ozon, Yandex Market) provide their own APIs. Integration is built in a similar way: marketplace services receive products, prices, and stock levels from 1C and CRM on a schedule or via API notifications, and export orders and shipment statuses back the other way. The CRM creates deals with the marketplace details, and commission calculations can happen in 1C.
Bitrix24 supports native telephony and chat widgets, but webhooks are used for specific PBXs or WhatsApp modules. When a call comes in, an external service checks the number in the CRM via API, creates a lead, adds a comment, and then attaches the call recording. This makes it possible to keep a complete contact history.
The CRM REST API lets you export data on deals, leads and tasks. It can be loaded into a Data Warehouse and used to build reports in Power BI or Tableau: for example, to analyze how fast deals move through the pipeline, shipments, payments and conversions from various channels.
Do not connect every system directly to every other one. Build an intermediary (integration gateway / API gateway) that accepts events from Bitrix24, validates them, and forwards them. Such a layer: provides scalability (new services can be added); controls errors; logs all calls in one place; allows one system to be replaced with another without rebuilding all connections.
All systems "understand" the same entities: customer, order, product. In the gateway, a unified structure is built (a JSON schema) that describes the fields, their types, and values. Each service knows how to convert its data into this format. This matters because 1C and Bitrix24 use different field names and different date formats.
It is critical to understand when speed is needed and when resilience matters: Synchronous for operations with an immediate result, where the user waits for the system to confirm, for example promo code checks or phone validation. Asynchronous for long-running processes (exporting closing documents, generating reports, sending to delivery). Queues and events are used for these. If one stage fails, the system retries or places the message into a "dead letter queue" for further analysis.
The integration processes personal data: full name, phone number, order. You need to encrypt transport (TLS); store access keys in secret stores; use the minimum required permissions (principle of least privilege); keep an audit log of who accessed what and when; comply with personal data law (Federal Law 152) and GDPR requirements.
You need to monitor what happens with requests: response time, error count, and statistics for successful and failed operations. Teams implement: Correlation IDs - unique identifiers that travel through all services so the full chain of actions can be traced. Metrics - average and maximum processing time, queue consumption rate, and number of retry attempts. Alerts - notifications if a service exceeds the timeout or the error count reaches a threshold.
Step 1: requirements gathering Which systems are being integrated? (CRM, 1C, website, marketplaces, payment gateways, delivery, BI)
Which data flows are needed? (deal creation, stock updates, payment status, delivery)
Who owns each process? (sales, warehouse, accounting) Step 2: analysis and modeling
Define the as-is and to-be models, and create process diagrams.
Identify integration points, "bottlenecks" and risks.
Step 3: choose the architecture Determine whether an intermediary (integration layer) is needed or whether webhooks are enough.
Develop a canonical data model and exchange format (JSON, XML).
Decide on the mode of operation: synchronous, asynchronous or hybrid. Step 4: development
Create an app in Bitrix24, obtain the keys (client_id, client_secret) and set up OAuth. Configure
for inbound/outbound calls and events. Build services to communicate with 1C, marketplaces and delivery providers. Implement a queue if one is needed.
Set up a test Bitrix24 portal. Create test records with edge cases (long names, different currencies, returns). Verify idempotency (a repeated call must not create duplicates). Run load testing for peak loads (for example, the "11.11 sale").
Run a pilot launch in a specific region or with a separate customer group. Set up monitoring and alerts. Prepare business users: train them, document instructions, and assign owners.
Track metrics, adjust processes, and update documentation. Keep API versions current, as Bitrix24 periodically releases new features. Add new scenarios: integration with marketing services, automatic discounts, and chatbots.
Lack of process design. If you integrate everything indiscriminately
, without understanding the business logic, we end up with a lot of chaotic calls.
First define the processes, then build the API connections. Unaccounted idempotency.
Calling a method again without idempotency can create duplicate payments or orders.
Always provide a unique operation key. There is no version control.
When the Bitrix24 API is updated, a method may change its behavior.
Use versioning: include the version in the URL and track updates. Polling instead of events.
Some integrators poll the API every 5 minutes to check whether anything has changed. This creates load. It is better to subscribe to events. They do not log.
When errors occur, it is important to know what data was sent, what the response was, and at which stage the issue happened. Without logs, it is impossible to find the error.
Secrets in public access. API keys and tokens are sometimes stored in code.
If the code falls into the wrong hands, the attacker can use the key to access the CRM. Store secrets in a vault.
Integrations can be assembled with no-code builders (Microsoft Power Automate, Make/Integromat, Zapier) that already work with Bitrix24.
This speeds up service integration without a developer. Event-Driven architecture.
Bitrix24 is evolving in this direction: new event types and WebSocket support are appearing. Hyperautomation.
Combining BPM, RPA (robots) and AI lets you automate not only data exchange but also decision-making. For example, a robot can automatically create a lead, run scoring, assign an owner and send a welcome email.
Bitrix24 is expanding the REST API:
This makes it possible to build even deeper integrations.
Integrating Bitrix24 with external APIs is the foundation for building a unified digital enterprise ecosystem.
It removes routine, speeds up processes, increases transparency, improves the customer experience and reduces costs.
But success is only possible with a sound approach: you must describe processes, design the architecture, follow security rules, track versions and build observability. Bitrix24 offers flexible tools:
for quick tasks, the REST API for full control, events for reactive schemes and built-in robots for simple automations. And a properly configured
and the canonical model make it possible to scale the solution without rewriting code for every new partner or service. And finally, it is important to remember: integrations are not a one-time task, but an ongoing development process. The company grows, new channels appear, regulators impose new requirements, and new CRM features are added. You need to prepare for change rather than try to freeze one configuration.
