We often encounter this scenario: the integration is working, data is syncing — then on Friday evening a script starts sending requests in an endless loop, hits the limit, gets a QUERY_LIMIT_EXCEEDED error, and crashes. Or worse — it doesn't crash but immediately retries, making the situation worse. Bitrix24 API has strict rate limits, and any integration must account for them. Otherwise — data loss, desynchronization, application blocking. Our experience shows: proper rate-limiting configuration saves hours of debugging and prevents incidents. Our team has 10+ years of development experience on Bitrix24 and has implemented over 50 integrations, so we know all the pitfalls. This article covers Bitrix24 REST API limits, optimization methods, and specific scenarios we implement for clients. You will learn how to avoid typical mistakes and build a resilient integration.
Bitrix24 API limits overview
Bitrix24 applies limits at two levels:
| Type |
Limit |
Comment |
| Webhooks (incoming) |
2 requests per second |
Per webhook |
| Server applications (OAuth) |
2 requests per second |
Per application per portal |
| Daily limit |
10,000 requests per day |
For free plans. Commercial — higher |
| batch request |
50 commands per batch |
Counts as 1 API request |
According to Bitrix24 REST API documentation, the per-second limit is 2 requests. When the limit is exceeded, the API returns HTTP 503 with body {"error":"QUERY_LIMIT_EXCEEDED"}. Retry is recommended after 500ms — not immediately. The daily limit resets at 00:00 portal time. For marketplace applications, limits differ and depend on the developer subscription.
Using batch method to bypass limits
batch is the main tool for saving requests. One batch call contains up to 50 commands and counts as one request:
POST https://your-domain.bitrix24.by/rest/batch/
cmd[0]=crm.deal.list?filter[STAGE_ID]=WON
cmd[1]=crm.deal.list?filter[STAGE_ID]=LOSE
cmd[2]=crm.contact.list?filter[TYPE_ID]=CLIENT
Commands inside a batch run sequentially. You can use the results of previous commands via $result:
cmd[0]=crm.deal.get?id=123
cmd[1]=crm.contact.get?id=$result[0][CONTACT_ID]
Using batch requests is 50 times more efficient than individual calls. Instead of 50 separate requests (25 seconds at 2 req/sec) — one request in 1-2 seconds.
What is the best rate limiting strategy for your integration?
Comparison of limit management strategies helps you choose the right approach. Batch requests are 50 times more efficient than individual calls and the most impactful optimization.
| Strategy |
Complexity |
Reliability |
Applicability |
| Exponential backoff |
Low |
Medium |
Simple scenarios |
| Request queue |
Medium |
High |
High-load |
| Token bucket |
High |
High |
Distributed systems |
Exponential backoff — when receiving QUERY_LIMIT_EXCEEDED, retry with increasing delay: 500ms → 1s → 2s → 4s. Maximum 5 attempts, then log error.
Request queue — instead of direct API calls, requests are placed in a queue (Redis, RabbitMQ, DB). A worker processes the queue, respecting the 500ms interval between requests. This eliminates the situation where two processes simultaneously send requests and collectively exceed the limit.
Token bucket — a software counter: the application tracks the number of requests in the last second and blocks sending until a slot is free. Implemented via shared state (Redis) for distributed systems.
Also use time separation: heavy synchronizations (full deal export, catalog update) run at night when users are not using the API.
Choosing a limit management strategy
Strategy choice depends on load and architecture. For simple scenarios, exponential backoff is sufficient — it requires no additional services. If the integration is high-load (more than 10 requests per second total), use a request queue on Redis — it guarantees compliance even with concurrent requests. Token bucket fits distributed systems where multiple microservices access one portal.
How to check current API usage?
Current API call usage can be checked with the `app.info` method — it returns the number of remaining requests for the current period. For webhooks, there is no similar metric — you need to count on your side. In the B24 logs (Settings → Event Log), API errors including limit exceedances are recorded. We set an alert at 80% of the daily limit.Avoiding QUERY_LIMIT_EXCEEDED
Implementing proper rate limiting in Bitrix24 helps avoid QUERY_LIMIT_EXCEEDED errors and optimizes API limits usage. Avoiding these errors can save an estimated $2,000 per incident in lost productivity and debugging time.
Step-by-Step Implementation Guide
- Analyze your integration's request pattern.
- Group operations into batch requests using the
batch method.
- Implement exponential backoff retry logic with a maximum of 5 attempts.
- Set up monitoring and alerts at 80% of daily limit.
- Conduct load testing to verify compliance.
What's included in our integration optimization work
- Integration architecture considering rate limits: batch requests, queues, backoff
- Worker for sequential API request processing with speed control
- Migration from single requests to batch for bulk operations
- Monitoring of API limit usage and alerts when approaching thresholds
- Load distribution: background synchronizations during non-peak hours
- Diagnostics and fixing
QUERY_LIMIT_EXCEEDED errors
- Documentation of the configured integration
- Access to monitoring dashboards and training for your team
- Configuration of webhooks and OAuth application limits
- Performance testing and optimization report
Project evaluation is free. If you encounter QUERY_LIMIT_EXCEEDED errors or want to optimize your API integration, contact us. Our certified specialists have many years of experience with Bitrix24 and guarantee the stability of your integrations. Get a consultation — we'll help eliminate bottlenecks and prevent downtime.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
