DENTAL✦INTEGRATIONS · WHAT WE CAN CONNECT TO, AND WHAT WE CANNOT
Does it work with your practice software?
It is the first question every dentist asks us, and it has a real answer — a different one for Dentrix than for Open Dental than for Curve. Here is what each system actually publishes, with the page we read beside it, and what you get when yours publishes nothing at all.
+THE SHORT VERSION
Practice systems fall into three groups. Some publish API documentation anyone can read today. Some hold it behind an application and release it once the vendor approves you. Some publish neither, and the only route runs through the vendor. Which group yours is in decides whether a booking can be written into your schedule or arrives as a complete request your desk enters once — and we tell you which before you spend anything.
Every integration on this page is confirmed on the discovery call, against your system and your version, before it is promised. Book the call →
✦WHAT AN INTEGRATION ACTUALLY IS
Four questions, and the honest answer to each one.
"Integration" is used to mean almost anything in a sales meeting. These are the four things it has to mean before the word is worth anything to you.
What moves
A name, a phone number, an email, the reason for the visit, which slots are open, and the status of an appointment. That is the whole list. Not charts, not radiographs, not treatment plans, not insurance policies — no agent of ours reads a clinical record, and we do not ask for access to one.
Which direction it moves
Reading is seeing what your schedule already holds. Writing is putting something into it. Almost everything a practice actually wants — "can it book?" — is a write, and a write is the permission every system guards hardest. A vendor that will let you read but not write is common, and it is not the same offer.
Who switches it on
Your practice does, inside your own software or your own account, and your practice can switch it off again without asking us. Open Dental is the clearest example: two keys travel on every request — one issued to the developer, one generated for your practice specifically — and somebody at your office enables the API before either works.
What happens when it breaks
Connections do break — an update lands, a key expires, a server in the back office gets rebooted. We build every one so that a failure falls back to the same structured message your desk already knows how to handle, and so that you are told it happened rather than discovering it from a patient who never got a confirmation.
✦THE SYSTEMS · CHECKED 7 SEPTEMBER 2026
Every system here, with the page we read.
Each one earned its place by someone opening the linked page and reading it, on the date above. These are other companies' programmes and they change without telling us — so the link is there for you to check the same page yourself, not as decoration. A system we could not verify is not on this list at all.
Practice management systems
The system your schedule actually lives in.
Open Dental
Open Dental Software
A published REST API over the practice's own database, with patient and appointment resources and the full set of read and write methods. The most openly documented route in the list.
Who authorises it: two keys — one issued to the developer by Open Dental, one generated for your practice specifically — and somebody at your office turns the API on in your own setup. Open Dental's own specification also states that API developers should have a Business Associate Agreement in place with their clients.
Source: Open Dental Software — API Specification ↗ · API Setup ↗
Dentrix and Dentrix Ascend
Henry Schein One
One authorised-vendor programme, the API Exchange, covering both the desktop Dentrix and the cloud Dentrix Ascend. Vendors apply, and integrations run over OAuth 2.0.
Worth knowing: Henry Schein One publishes a list of applications it says are authorised for use with Dentrix and Dentrix Ascend, and separately names vendors it describes as using an unauthorised connection. If a supplier tells you they plug into your Dentrix, that page is the one to check them against.
Source: Henry Schein One — API Exchange ↗ · Authorized integrations ↗
Eaglesoft
Patterson Dental
Patterson Innovation Connection is Patterson's authorised route for third-party software that talks to Eaglesoft. Their page describes it as giving Eaglesoft customers a controlled and secure experience, and lists the vendors already inside it.
Who authorises it: Patterson. The technical documentation is not published openly; the page carries a route to become an authorised software vendor instead.
Source: Patterson Dental — Innovation Connection software providers ↗
Denticon
Planet DDS
A developer portal describing REST APIs across practice and patient resources, webhooks for changes, and bulk extracts. It lists creating and updating patients, seeing scheduling availability, and booking, confirming or cancelling appointments.
Who authorises it: Planet DDS, through their API programme. The portal documents what exists; it does not publish the enrolment route, so that part is a conversation with them.
Sensei Cloud
Carestream Dental
Carestream runs a developer programme for Sensei Cloud. Their page says they have created an API to integrate directly with Sensei Cloud, and that the documented API is made available for testing once a request form has been reviewed.
Who authorises it: Carestream, form first. Nothing technical is public before that — so if anyone tells you exactly what they will do inside your Sensei Cloud before the form has gone in, they are guessing.
Source: Sensei — Developer Program ↗
tab32
Dental practice software
tab32 announced an API for third-party developers covering patient management, appointment scheduling, insurance claims processing and treatment planning, with documentation and sample code for the developers it admits.
Being straight about this one: we could not reach a public developer portal from their site on the day we checked, only the announcement. So for tab32 the honest first step is a call to them, not a promise from us.
Curve Dental
Dental practice software
Curve publishes an integration and partner network — payments, patient communications, claims, marketing — and says it integrates with top industry partners to offer premium solutions. We found no public API documentation and no developer application route on it.
What that means for you: if you run Curve, the honest first step is asking Curve whether what you want is already on their list. We will make that call with you rather than describe a connection we cannot see documented.
The layer that sits beside it
Many practices already run something between the phones, the messages and the practice software. Where that is true, it is often the shorter route — and sometimes the only one.
NexHealth Synchronizer
NexHealth
A middle layer: one documented API that reaches a number of practice management systems, so the connection is built to NexHealth rather than to each system separately. Their getting-started guide covers creating appointments.
The trade-off, said out loud: it puts a third company between you and your schedule, with its own agreement and its own cost. That is sometimes worth it and sometimes not, and it is your decision with the numbers in front of you — not a free shortcut we quietly add.
Podium
Messaging and reviews
A developer platform for the messaging and reviews layer some practices already run. Applications are approved, then authorised over OAuth 2.0 by a Podium user at your practice.
Who authorises it: someone at your practice, from your own Podium account — which also means your practice can withdraw it without asking us.
Weave
Weave Communications
Weave announced in August 2025 that it is an authorised integration vendor in the Henry Schein One API Exchange, and that its features integrate with Dentrix and Dentrix Ascend. We found no open developer documentation for building against Weave itself.
What that means for you: if Weave already sits between your phones and your Dentrix, it is often the shortest honest path — and whether anything of ours can meet it there is Weave's decision, not ours to announce.
Source: Weave — authorized integration vendor announcement, 26 August 2025 ↗
The two we already use every day
These are not maybes. They are documented, we work in them now, and you own the accounts.
Google Business Profile APIs
The listing that decides whether a nearby patient finds you at all. Google documents managing locations, handling verifications, posts, a reviews interface for replies, and alerts about new reviews and changes to your location data.
Who authorises it: you do. The profile is yours, you grant access to it, and you revoke that access from your own Google account without asking us. It is one of the reasons we insist the profile stays in your name.
Source: Google — Business Profile APIs ↗
Google Calendar API
Reads free time and writes events, over HTTP. It is what puts a discovery call booked on this site into a real diary, with a title, a start, an end and the people invited — which is the smallest working example of everything described further up this page.
Who authorises it: granted per calendar, by the Google account that owns the calendar.
Source: Google — Calendar API overview ↗
Naming a system here says what that vendor publishes. It does not say we are a partner of theirs, or that anything of ours is approved, listed or certified by them — where a programme requires an application, that application is a step to be taken for your practice, and we will tell you plainly where we are in it. Nothing on this page is a description of your contract with your software vendor; that agreement governs what anyone may connect to your system, and it is worth reading before anyone does.
✕WHEN YOUR SYSTEM HAS NO ROUTE
The honest answer, not a workaround.
Plenty of practices run something with no documented API and no programme to apply to. That is a normal answer, and it does not stop the work — but what happens next has to be something we can actually deliver for years, not a trick that survives the first software update.
✕ WHAT WE WILL NOT DO INSTEAD
- Scrape your practice software's screens. It works until a version changes, and then it fails quietly, which is the worst way for anything touching a schedule to fail.
- Run a robot on a spare workstation to type into it. Same fragility, plus a machine in your office that nobody owns and everybody forgets.
- Ask for a staff member's login and hold it. That puts your patients' details somewhere nobody at your practice agreed to, under a name that belongs to a person who may leave.
- Call it an integration anyway. If there is no route, the word is not ours to use, whatever it costs us in the meeting.
+ WHAT YOU GET INSTEAD
- A complete request, not a lead. Name, number, email, the reason in the patient's own words, and the times they chose — in one message, in one place.
- Entered once, by your team. Seconds at the desk, and nobody has to phone the patient back to ask for something that was missed.
- The patient still gets an answer immediately. The confirmation, the reminder and the follow-up all run on our side, whether or not your system can be written to.
- The middle-layer option, priced honestly. If a service like NexHealth reaches your system, we will say so, tell you what it costs and what it adds to the picture, and let you decide.
- A revisit when your system changes. These programmes open up. If yours does, that is a conversation, not a new contract.
✓HOW YOURS GETS CONFIRMED
Before you commit, not after.
Which system, which version, whether it is on a server in your office or in the cloud, and anything already sitting beside it — a phone platform, a messaging tool, an online booking widget somebody set up years ago.
Against that vendor's current route, not against this page — this page is a snapshot of one day. If it needs an application, we say how long that typically takes and who has to approve it. If there is no route, you hear that in the same sentence.
What will be connected, in which direction, what happens if it stops, and what the alternative looks like if it never starts. Nothing is invoiced against a connection that has not been confirmed to exist.
Our infrastructure runs on Google Workspace and Google Cloud under signed Business Associate Agreements. Whatever moves between us and your systems moves under that, and no more of it moves than the job needs — see the privacy notice for what we hold and for how long.
✕WHAT WE WILL NOT CLAIM
The things we will not say to win the work.
Each of these is a line another agency will happily cross. Here is where we stand on it, in writing.
- A connection to a system that does not publish one.Where a vendor documents no route, we say so on the call and build the structured handoff instead — we do not scrape screens, drive your software with a robot, or hold a staff login.
- Being called a partner, an authorised vendor or a certified integration of anybody’s.Those words belong to the vendor who grants them. Where a programme needs an application, that is a step taken for your practice, and we tell you where it stands.
- Guaranteed rankings, appointments or revenue.Nobody can honestly promise what Google or a patient will do. We guarantee the work, and you watch what moved month by month.
- A proprietary dental platform.We build on tools you could run without us, and everything we build is yours.
- Universal PMS or EHR integration.Integrations are possible with any practice system that exposes an API — we confirm yours on the discovery call. Here is what each system publishes today.
- AI insurance verification or treatment-plan mining.No agent of ours reads a chart, checks a policy or suggests treatment.
- “SOC 2” or “HIPAA compliant” as a badge.Our infrastructure runs on Google Workspace and Google Cloud under signed Business Associate Agreements. We do not call that HIPAA compliance, because no vendor honestly can.
- Clinical or diagnostic AI.Every agent refuses clinical questions and hands to a person.
- A client quote without written permission.The practice we photograph is credited; nothing anyone said appears here until they say in writing that it may.
- An invented statistic.Every figure on this site is either counted from what we run, or carries the source it came from.
→TWENTY MINUTES, AND YOU LEAVE KNOWING
Tell us what you run. We will tell you what it can do.
Bring the name of your practice software and, if you know it, the version. You will get a straight answer on the call — including "no, and here is what we would do instead" — before anything is quoted.