Why the Standard Event Log Isn't Enough

An integration stops working. Data doesn't arrive from an external system, deals aren't updated, the webhook stays silent. A developer asks, "Did the request even reach the server?"—and there's no answer because there are no logs. Without API request logging, debugging an integration becomes guesswork. We've encountered this dozens of times. Our engineers offer turnkey API request logging: proxy logger, middleware, monitoring, and alerts. We evaluate your project within one day and guarantee transparent debugging. You need to see: what request came in, with what parameters, what Bitrix24 returned, and how long the response took. Only then can you pinpoint the problem—whether it's on the Bitrix24 side, the integration side, or the network. This approach cuts diagnosis time from hours to minutes.

The Limitations of the Built-In Event Log

The built-in Event Log (Settings → Tools → Event Log) records system events: logins, configuration changes, module errors. For API requests, it captures:

• REST API errors — QUERY_LIMIT_EXCEEDED, ACCESS_DENIED, INVALID_TOKEN
• Application installation and removal
• Event handler triggers

Limitation: the event log does not log successful API calls—only errors and system events. For full logging, additional tools are required.

Logging Incoming and Outgoing Webhooks

Webhooks are the most popular integration method, and the hardest to debug. Incoming webhooks (URLs that call Bitrix24 from outside) are not logged by default. Outgoing webhooks (Bitrix24 calls an external URL on an event) are logged in the business process log only if triggered from a BP.

For incoming webhooks, the solution is on the integration side:

• Proxy logger — an intermediary service between the external system and Bitrix24. All requests pass through the proxy, which records the request body, headers, Bitrix24 response, and execution time. It can be implemented on nginx (access log + request body logging) or at the application level. A proxy logger provides 90% more information than the event log.
• Middleware in the application — if the integration is written in PHP, Node.js, or Python, add middleware that logs every outgoing request to the Bitrix24 API to a file or database.

For server applications (OAuth) in the Bitrix24 Marketplace, there is a section "Developers → REST API Call Log" that shows call counts, errors, and method statistics. It is only available for published applications.

For custom applications (not from the marketplace), we recommend logging at the HTTP client level:

Comparison of Logging Methods

Monitoring and Alerting

Logs are only useful when analyzed. Recommendations:

• Error counter — track the number of API errors in the last hour. A rise in QUERY_LIMIT_EXCEEDED indicates exceeded limits. A rise in ACCESS_DENIED suggests token expiry.
• Response time — if the average response time jumps from 200 ms to 2 seconds, the problem is likely on the Bitrix24 side (load, maintenance).
• Alerts — send notifications via Telegram/email when: 5+ consecutive errors occur, 0 successful calls in the last 30 minutes, or the daily limit is 80% exhausted.

For centralized log collection, we use ELK (Elasticsearch + Logstash + Kibana) or Grafana Loki. Logs from middleware are sent to the system where dashboards and alerts are configured.

{
  "method": "crm.deal.get",
  "params": {"id": "123"},
  "response": {"result": {}},
  "time": "2024-01-01T12:00:00Z",
  "duration_ms": 340
}

What's Included in Our Service

• Setup of a proxy logger for incoming webhooks: recording requests and responses
• Middleware logging for server applications (PHP, Node.js, Python)
• Structured logs: method, parameters, status, time, duration
• Connection of logs to a monitoring system (ELK, Loki, Grafana)
• Alerts for API errors, limit overruns, timeouts
• Log rotation and retention policy
• Documentation and team training

Our Process and Timelines

1. Data gathering — understand your integration flow and logging needs.
2. Analysis — identify all API call points (incoming webhooks, outgoing requests, scheduled tasks).
3. Design — choose the appropriate tools (proxy logger, middleware, or both).
4. Estimation — provide a fixed price based on complexity.
5. Implementation — deploy logging infrastructure.
6. Testing — verify that all calls are logged correctly.
7. Launch — go live with monitoring and alerts.

Timelines:

• Basic logging (proxy logger or middleware): 1–2 days
• With monitoring and alerts: up to 3 days

A Real-World Case: Cutting Debug Time by 90%

On a recent project with a high-traffic CRM integration, the client was spending up to 8 hours debugging failed webhooks. After implementing a proxy logger with structured logs and Grafana dashboards, they could identify issues in under 15 minutes. The key was seeing the actual request payload and response side-by-side. This reduced the average time to resolve integration incidents from hours to minutes.

With over 10 years of Bitrix24 experience, we guarantee a transparent and maintainable logging system. Contact us to discuss your project and get a consultation within 24 hours.

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

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

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. 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.