Authorized, and you can check it
Open Dental publishes a vendor register with four tiers. We are listed as Authorized, meaning we use the API.
Yes. Open Dental publishes a fully documented REST API with endpoints for appointment availability, booking, rescheduling, breaking and confirming, available in three deployment modes.
Open Dental publishes a full REST API with documented endpoints for finding open slots, booking, rescheduling, breaking and confirming appointments. GetHelpdesk.AI is listed on Open Dental's own vendor page as an Authorized integration, meaning we write through the API rather than into the database.
Open Dental is a Windows server-based practice management system, first released in 2003 and still developed by Open Dental Software, Inc.
A published API with documented scheduling endpoints, and a vendor register that lets you verify what any supplier actually does with your data.
Open Dental publishes a vendor register with four tiers. We are listed as Authorized, meaning we use the API.
Open Dental encodes provider time and assistant time in a procedure's time pattern.
The Local API and API Service run entirely inside your network and are not throttled.
Open Dental users report having to look a patient up office by office, with no single search.
There is a documented endpoint for your short-notice list.
A cancellation and a no-show are different things in Open Dental.
Two keys, three possible routes, and your own scheduling rules. No database access at any point.
Start setupThe API authenticates with a developer key and a customer key specific to your practice.
Local API on a workstation, API Service on your database server, or Remote through your eConnector.
Your operatories, providers, appointment types and their time patterns, plus blockouts. This is what stops the AI offering a slot your schedule would refuse.
Your number does not change. Start with overflow or after-hours, review the transcripts, then hand over as much of the line as you want.
Exactly what is read, written and escalated. Anything marked partial is confirmed during setup against your own Open Dental configuration.
| Action | Supported | Notes |
|---|---|---|
| Find open appointment slots | Yes | The documented Slots endpoint, filtered by provider, operatory and required length. |
| Book a new appointment | Yes | Written during the call against patient, operatory and time. |
| Reschedule an appointment | Yes | A documented update against the existing appointment. |
| Cancel or mark a no-show | Yes | Uses the Break endpoint with the correct break type, and can send the patient to the Unscheduled List. |
| Confirm an appointment | Yes | A dedicated endpoint with real confirmation statuses rather than a note in a field. |
| Work the ASAP list | Yes | There is a documented endpoint for your short-notice list. |
| Run without an internet connection | Yes | The Local API and API Service are internal to your network and are not throttled. |
| Write directly to the database | No | Never. Open Dental classifies direct database writes as dangerous, and that is the whole point of the Authorized tier. |
Availability is queried by provider, operatory and appointment length rather than guessed from a grid.
Provider time and non-provider time are respected, so the schedule stays realistic.
Cancellations and missed appointments are recorded as what they actually were.
Local, service and remote routes with automatic fallback, so one failure does not stop bookings.
Fixes the per-office search limitation reviewers report, at least for anyone calling your line.
The full conversation plus a summary, without anyone taking notes.
Listed as Authorized on Open Dental's public vendor register.
Slots, book, reschedule, break, confirm and ASAP.
Local, service or remote, whichever is reachable.
The ASAP list, actually worked
An 11am crown cancels. The ASAP list already holds the patients who wanted an earlier slot, but nobody has time to call them.
The ASAP list was a list of people we felt guilty about not calling.
Per-office lookup, solved on the call
A patient of your second location calls the first. Because lookup is per-office, staff often cannot find them without switching context.
Finding a patient should not depend on guessing which office they belong to.
Local and service routes
The connection goes down. Cloud-only integrations stop being able to see the schedule at all.
We are on a rural connection. Anything that depends on the internet being up is a gamble.
Still not sure how it would work on your schedule? We will walk through your own Open Dental setup on the call.
Ask us directlyYes, and it is the most open in dentistry. Open Dental publishes its full API specification publicly with no login required, covering appointment availability, booking, rescheduling, breaking and confirming.
Yes. Open Dental maintains a public register classifying third-party vendors, and GetHelpdesk.AI is listed under Authorized — its definition being that the vendor uses the Open Dental API, which Open Dental calls the approved method of writing to the database.
No, and this is widely reported incorrectly. Open Dental changed its licence from GPL to proprietary at version 24.4, with source code available only to certain large customers under a non-disclosure agreement.
No. Open Dental encodes each procedure's provider time and non-provider time as a time pattern, and the AI books against that shape rather than assuming a uniform block.
Yes, which is unusual. The Local API runs inside Open Dental on a workstation and the API Service runs on your database server — both are internal to your network, need no internet, and are not rate limited.
The integration is included in your GetHelpdesk.AI plan at no extra cost.
Open Dental publishes a public register of third-party vendors and classifies each one by how it connects. The distinction that matters is Authorized, meaning the vendor writes through the documented API, versus tools that write straight into the database. GetHelpdesk.AI is listed as Authorized. For front desk automation specifically, look for a vendor that covers the whole call rather than one step of it: finding a real open slot, booking it, rescheduling, breaking and confirming.
Ask three questions that have checkable answers. Is the vendor listed as Authorized on Open Dental's own vendor register, or only claiming an integration? Does it write appointments through the API, or scrape and type them in? And does it book against the procedure's time pattern, or assume every appointment is a uniform block? Reviews are worth reading, but the vendor register is the one claim you can verify yourself in under a minute.
Hear the AI answer a call on your own Open Dental schedule. Fifteen minutes, no phone-system change, no commitment.