Integrations

What Dentolize connects to

A clinic system that does not talk to anything becomes another place to type the same thing twice. These are the connections that remove work rather than add a logo to a page.

WhatsApp BusinessConfirmations, reminders, campaignsConnected
ZATCAPhase 2 clearance with QRConnected
NPHIESEligibility and claimsConnected
Google CalendarTwo-way sync per doctorConnected
Google DriveAutomatic file backupAvailable
Payment gatewaysmada, Visa, Apple PayConnected
X-ray imagingSensors and scanners write straight to the chartConnected
Public APIBuild on your clinic dataAvailable

The ones that remove daily work

Integration is only worth having where it removes a repeated human action. These are the connections clinics notice within a week.

  • WhatsApp Business for confirmations, reminders, recalls and campaigns
  • Payment gateways for mada, Visa, Mastercard and Apple Pay
  • X-ray imaging, so sensors and scanners write straight to the chart
  • Google Calendar, two-way per doctor, for people who live in their own calendar
  • Google Drive for automatic document and image backup

The ones required by where you operate

In Saudi Arabia two of these are not optional, and both are the kind of integration that has to be inside the invoicing and claims flow rather than beside it.

  • ZATCA phase two clearance and reporting on every invoice
  • NPHIES for eligibility, pre-authorisation and claims
  • Insurance company price lists applied per policy
  • Dental laboratories, with cases and statuses tracked both ways

The public API, for everything else

No vendor will ever build the one connection your clinic specifically needs. The API is how that gets built without waiting for us.

  • REST API over patients, appointments, invoices and treatments
  • Authentication per integration, revocable independently
  • Webhooks on the events worth reacting to
  • Rate limits and logs, so an integration failing is visible

Read the API reference

Who integrations serve

Most integrations are invisible when they work, which is the point.

Front desk

Sends and takes payment without opening a second system.

Owners

Meets local requirements without a separate compliance process.

Technical teams

Builds what is specific to this clinic against the API.

By hand, and with Dentolize

Every missing integration is a person re-typing something that already exists.

Doing it by hand

  • Reminders sent manually
  • Invoices formatted for ZATCA separately
  • Insurance checked by phone
  • X-rays saved to a folder
  • No way to connect anything else

With Dentolize

  • WhatsApp reminders on a rule
  • Cleared as part of issuing them
  • Eligibility through NPHIES from the record
  • Images written to the patient chart
  • A public API with webhooks
Questions

Integrations — frequently asked

Does Dentolize have an API?

Yes, a REST API over patients, appointments, invoices and treatments, with webhooks and per-integration credentials that can be revoked independently.

Does it integrate with WhatsApp?

Yes, through WhatsApp Business, for confirmations, reminders, recalls, feedback and campaigns.

Can X-ray images go into the patient chart?

Yes. Sensors and scanners write to the chart directly rather than to a folder somebody has to attach later.

Which payment gateways are supported?

Gateways covering mada, Visa, Mastercard and Apple Pay; which are available depends on your country and provider.

Does it sync with Google Calendar?

Yes, two-way and per doctor, for clinicians who work from their own calendar.

See Integrations on your own clinic

Thirty minutes on how your clinic actually runs, not a generic slideshow. We will call you within 24 hours.

Book a demo WhatsApp