Integrate 1C-Bitrix with Dikidi Online Booking

A beauty salon or clinic uses Dikidi for appointments — clients book via the app, stylists see the schedule. The Bitrix website lives separately: service catalog, prices, promotions, but booking is only possible by phone or via the Dikidi widget. Integration is needed so that the site and booking system work as a single unit: up-to-date schedule on the site, booking without leaving for an external service, client data landing in CRM. Our team has completed over 50 integrations with external services for Bitrix — experience allows us to anticipate all nuances and guarantee stable data exchange.

Typical scenario: a client wants to book a haircut but only sees prices on the site. They have to either call or switch to Dikidi. On a call, the admin spends 5 minutes manually checking slots. Switching to Dikidi makes the user leave the site, and booking data doesn't reach CRM. Integration solves both problems: a booking form right on the site, synchronized schedule, client data automatically saved in Bitrix24.

We have integrated Dikidi with Bitrix websites over 15 times. In this article — the architecture of the solution, pitfalls, and what the business gets.

What is the Dikidi API?

Dikidi provides a REST API (documentation available via support) that allows management of services, staff, schedule, and bookings. Main endpoints:

• GET /api/v2/company/{id}/services — list of services with prices and duration
• GET /api/v2/company/{id}/masters — masters with schedule
• GET /api/v2/company/{id}/schedule — available slots for a specific master and service on a given date
• POST /api/v2/company/{id}/booking — create appointment (master, service, date, time, client data)
• GET /api/v2/company/{id}/booking/{id} — booking status

Authorization is via API key in the Authorization header. The key is issued when a plan with API access is activated. Restriction: not all Dikidi plans include API. On the basic plan, only the widget (iframe) is available. API is on 'Business' plan and above. Clarify before starting work.

Which integration option to choose?

If you need a quick solution — just embed the Dikidi iframe widget. The embed code is one line in the component template or page editor:

<iframe src="https://dikidi.net/widget/{company_id}" width="100%" height="700" title="Embedded content from dikidi.net"></iframe> 

This works in 10 minutes, but you lose UX control, the design is external, data doesn't reach CRM, and SEO value is zero. The widget is suitable as a temporary solution, but for a full-fledged business, a custom API integration is better. It gives full control over appearance, data transfer to CRM, and analytics capabilities.

Why choose custom integration?

Custom integration turns Dikidi into a schedule backend, and the booking form becomes part of the site. You control every user step, the design of each step, and can add your own fields (promo codes, booking notes). Appointment data syncs with Bitrix24 CRM, allowing managers to see the full client history, not just website bookings. Such integration pays off quickly: reducing slot selection time by 80% and eliminating double bookings.

How does custom integration with Dikidi work?

Architecture:

1. A daily cron script (CAgent) fetches the list of services and masters from Dikidi API and stores them in a highload block or infoblock. This ensures that the service catalog pages work without requesting Dikidi API on every hit.
2. Custom component custom:dikidi.booking on the service page:
   • Step 1: select master (data from HL-block)
   • Step 2: select date and time — AJAX request to Dikidi API /schedule (real-time; slots cannot be cached as they change every minute)
   • Step 3: client contact details
   • Step 4: confirmation — POST /booking
3. Response handling. On successful booking, Dikidi returns a booking_id. We save it in the HL-block DikidiBooking linked to the Bitrix user (if authenticated) and to the CRM record.

What does synchronization with Bitrix24 CRM provide?

Booking through the site creates a lead or deal in CRM:

• On booking confirmation — REST request crm.lead.add or crm.deal.add with data: client name, phone, service, master, date/time
• Lead source — 'Website booking (Dikidi)' (add to source dictionary via crm.status.add)
• In the deal UF field, we store the Dikidi booking_id for cross-reference

Reverse synchronization: if a manager cancels a deal in CRM, a webhook calls DELETE /booking/{id} on Dikidi API. Implemented via a CRM robot on the 'Cancelled' stage.

Webhook from Dikidi: how not to lose a single booking

Dikidi supports outgoing event notifications (if configured): new booking, cancellation, change. The endpoint on the Bitrix side is a PHP script at /local/tools/dikidi_webhook.php, which:

• Verifies request signature
• Creates or updates the record in the HL-block
• Creates a lead in CRM (if the booking was made through the Dikidi app, not the website)

This covers the reverse scenario: client booked via the Dikidi app — the site and CRM know about it.

What's included in the work

Implementation timelines

Dikidi is a closed ecosystem, and integration quality depends on API availability on your plan. We will assess your project for free — contact us for a consultation. Our over 8 years of experience in Bitrix development guarantees that the integration will work stably and without surprises. Order integration today — get a working prototype within a week.