Source connector

Bitrix24 connector

Bitrix24 integration for databases, warehouses and BI tools

CRM, contact center, and task automation suite. Datrise captures Bitrix24 entities such as leads, deals, contacts, companies, activities, and contact-center events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Bitrix24 REST API (CRM methods, unversioned) authenticates with OAuth 2.0, personal access token, incremental runs key on DATE_MODIFY, and Bitrix24 caps calls at Leaky bucket per Bitrix24 account: counter drains 2 requests/s with a 50-request burst threshold on most plans (Enterprise: 5/s and 250), HTTP 503 `QUERY_LIMIT_EXCEEDED` above it; one request must finish within 60 s; per-method `operating` execution-time budget over 10 one-minute buckets (HTTP 429 `OPERATION_TIME_LIMIT`, cloud limit value not published).

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `bitrix24_leads`) with a schema derived from the Bitrix24 API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Bitrix24 pipeline page, and join the waitlist to get the Bitrix24 connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Bitrix24 data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
leads	bitrix24_leads	Upsert by primary key, incremental on updated-at
deals	bitrix24_deals	Upsert by primary key, incremental on updated-at
contacts	bitrix24_contacts	Upsert by primary key, incremental on updated-at
companies	bitrix24_companies	Upsert by primary key, incremental on updated-at
activities	bitrix24_activities	Append-only, incremental by timestamp
contact-center events	bitrix24_contact_center_events	Append-only, incremental by timestamp

Bitrix24 API: setup facts for the connector

Verified against the vendor documentation on 2026-10-05. Unknown values are left blank rather than guessed.

API	Bitrix24 REST API (CRM methods, unversioned)
Authentication	OAuth 2.0, personal access token — Local and Marketplace applications use OAuth 2.0 against `https://oauth.bitrix.info/oauth/token/` (authorization code valid 30 seconds, `access_token` one hour, `refresh_token` 180 days); simple integrations instead call `https://<portal>/rest/<user_id>/<secret_code>/<method>` with an incoming webhook whose per-employee secret code is embedded in the URL and runs with that employee's permissions.
Pagination	offset — Every `.list` method returns a fixed page of 50 records and a `next` value to pass back as `start` (`start = (N-1) 50`); for large tables Bitrix24 recommends `start=-1` (skips the `total` count) with `order[ID]=ASC` and `filter[>ID]=<last id>` instead.
Rate limit	Leaky bucket per Bitrix24 account: counter drains 2 requests/s with a 50-request burst threshold on most plans (Enterprise: 5/s and 250), HTTP 503 `QUERY_LIMIT_EXCEEDED` above it; one request must finish within 60 s; per-method `operating` execution-time budget over 10 one-minute buckets (HTTP 429 `OPERATION_TIME_LIMIT`, cloud limit value not published)
Incremental cursor	DATE_MODIFY — Leads, deals, contacts and companies expose the read-only `datetime` field `DATE_MODIFY` and `*.list` filters accept the `>`/`>=` prefix on any field (`filter[>DATE_MODIFY]`); the newer `crm.item.list` names the same field `updatedTime` (ISO 8601 with offset).
Webhooks	Yes — Outgoing webhooks / `event.bind` handlers (e.g. `ONCRMDEALADD`, `ONCRMDEALUPDATE`, `ONCRMDEALDELETE`) plus `event.offline.*` queue
Bulk export	No
Deletes detectable	Yes — `ONCRM<ENTITY>DELETE` events (online handler or offline queue) carry only `data[FIELDS][ID]` of the deleted record; list methods have no deleted-record filter, so without event capture a delete is only visible as a missing ID on the next full pass.

Official API reference

What bites when replicating Bitrix24

Event payloads contain only `data[FIELDS][ID]`, never the changed fields, so every `ONCRMDEALUPDATE` costs a follow-up `crm.deal.get`; online events are also fire-and-forget (no retry if the handler errors or times out), so loss-free capture needs `event_type=offline` plus `event.offline.get`, which collapses 1,000 edits of one deal into a single queue row and holds reserved batches for 30 days.
`start>=0` makes the server compute `total` on every page, which Bitrix24 measured at 49.9 s versus 0.097 s on a 2-million-row table; paginate with `start=-1`, `order[ID]=ASC`, `filter[>ID]=<last id>` and stop when a page returns fewer than 50 items.
`batch` packs up to 50 sub-calls into one HTTP request (the 51st and later fail with `ERROR_BATCH_LENGTH_EXCEEDED`, nested `batch` is rejected with `ERROR_BATCH_METHOD_NOT_ALLOWED`); the outer call counts as one request against the 2/s leaky bucket but each nested list call is charged separately against the per-method `operating` time budget.
An incoming webhook's secret code is visible only to the employee who created it, and if an administrator edits that webhook the secret is regenerated and ownership moves to the administrator, so any stored `https://<portal>/rest/<user_id>/<secret_code>/` URL starts failing with HTTP 401 `INVALID_CREDENTIALS`; webhooks can also carry an expiration date after which calls return an authorization error.

Compare this against every other documented API

Popular destinations for Bitrix24

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Bitrix24 connector FAQ

What Bitrix24 data does the connector extract?: 6 objects: leads, deals, contacts, companies, activities and contact-center events. Each lands in its own table with types preserved; history-style objects (2: activities and contact-center events) load as append-only streams.
Is the Bitrix24 integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Bitrix24 data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Bitrix24 → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Bitrix24 pipeline with guided onboarding

Join the waitlist to get priority access for Bitrix24 integrations with guided setup, schema-aware mapping, and production-grade incremental sync.