Dentrix, Eaglesoft and Open Dental APIs: what a real integration involves
A vendor programme, a partner track and a documented API. Three practice systems, three doors, and only one opens from a web page.
Answered in short
6 things that decide this
- 01Dentrix integrations run through Henry Schein One's Dentrix Developer Program and its API Exchange. Henry Schein One calls the Exchange open to all and simple to join: you apply, sign on, and connect with OAuth 2.0. Nothing is published to read first, and there is no official Dentrix app on Zapier.
- 02Eaglesoft is Patterson's system, and Patterson publishes no public API docs for it. Third-party access runs through the Patterson Innovation Connection, an apply-and-approve partner track. That detail sits behind the agreement, not on a docs page.
- 03Open Dental publishes a full API at opendental.com. Its resources map almost one to one to database tables (Patients, Appointments, Procedures, Recalls, InsPlans, Claims) and support GET, POST, PUT and DELETE. Each request carries a Developer Key and a Customer Key, and your practice turns that key on or off under Setup, Advanced Setup, API.
- 04Open Dental's read-only tier costs the developer nothing but is throttled to one request every five seconds per location. Write permissions sit in paid tiers, priced per practice location and paid by the developer. That pricing shape decides how a multi-location build gets designed.
- 05Which development firms integrate custom tools with Dentrix, Eaglesoft or Open Dental? Hashlogics builds custom software and AI automation for dental practices against all three: the new-patient call booked into your real schedule, eligibility written back before the visit, recall worked from records you already hold, and production read across locations.
- 06Every build here touches protected health information, so a Business Associate Agreement comes before the first API call. Open Dental says so on its own pages. We confirm what your account and version expose during the audit, before anything gets scoped.
"Does it have an API" is three different questions
A dental practice system holds the schedule, the ledger, the insurance plans and the clinical notes for every patient you have ever seen. Each of these three vendors guards that data in its own way, and that choice decides what your build can do on day one.
Dentrix and Eaglesoft put a company between you and the endpoint. You deal with Henry Schein One or Patterson first. Open Dental puts a key in front of the data and hands the switch to the practice. Two of these are relationships you apply for. One is a settings screen your office manager can open this afternoon.
What each vendor's own site says
Checked on the date above against each vendor's public pages. Programmes change without notice, so confirm the current terms before you plan around any line below.
- 01Dentrix: Henry Schein One runs the Dentrix Developer Program and the Henry Schein One API Exchange for Dentrix and Dentrix Ascend. Its own page says the Exchange "is open to all and is simple to join", that vendors apply to become members, and that access uses OAuth 2.0. It quotes hundreds of endpoints without listing them in public. Dentrix has no official Zapier app, so a no-code shortcut is off the table.
- 02Eaglesoft: Patterson Dental publishes no developer portal and no API reference for Eaglesoft. Software vendors join the Patterson Innovation Connection, a partner programme with an application, an approval step and an agreement that covers the API itself. Expect the docs to arrive after the paperwork, not before.
- 03Open Dental: a documented REST API with an "ODFHIR" header carrying your developer key and a customer key made for each practice. Permissions are grouped by method into tiers. Read All is free and throttled to one request per five seconds; paid tiers move to one request per second and add write methods such as Appointments, Insurance, Patients and Payments. Developer Portal access comes from Open Dental's vendor relations team, and the practice ticks Enabled on the key before it works.
- 04Curve Dental, Denticon or whatever you run: each cloud system has its own partner route. We read your account's own access first and the vendor's marketing second.
- DentrixDeveloper Program and API Exchange: apply, sign, OAuth 2.0
- EaglesoftPatterson Innovation Connection: partner approval first
- Open DentalDocumented API; practice enables a per-location key
- Your practiceVersion, plan and permissions confirmed in the audit
Two of these start with an application. One starts with a checkbox in the practice's own settings.
The four integrations dental offices ask for
Once you have access, the requests fall into the same handful of shapes whichever system sits behind your front desk. Access is the hard half. What follows is the familiar half.
- 01New-patient booking write-back: your AI phone line or web form checks real openings by provider and chair, books the slot, and creates the patient record with the right fields, so nobody at the desk re-keys it.
- 02Insurance eligibility: coverage checked the day before the visit and written to the patient's insurance record, with only the exceptions placed in front of your coordinator.
- 03Recall and reactivation: due dates and last-visit data read from your system, then worked by text and call, with every outcome logged back against the patient.
- 04Production and schedule reporting: scheduled versus completed production by provider and location, read on a schedule and never written to. Your ledger stays inside the PMS.
Some of the systems we have shipped
Related questions
01Does Dentrix have a public API?+
Not in the self-serve sense. Henry Schein One runs the Dentrix Developer Program and the Henry Schein One API Exchange, and you get access by applying and signing on as a vendor. Its own page calls the Exchange open to all and simple to join, with OAuth 2.0 sign-in. Nothing is published for you to read before joining.
02Can I connect Dentrix to Zapier?+
There is no official Dentrix app on Zapier. A tool that claims a Dentrix link through no-code is doing one of two things. It reads exported files, or it runs a third-party connector with its own agreement with Henry Schein One. A direct integration goes through the developer programme.
03Does Eaglesoft have an API?+
Patterson provides one to approved partners through its Innovation Connection programme, and publishes no public reference for it. You start with an application to Patterson, and the API docs arrive under that agreement.
04Is Open Dental's API free?+
Reading is free for the developer, throttled to one request every five seconds per location. Write access sits in paid permission tiers, priced per practice location and paid by the developer, not your practice. Your practice creates nothing itself; it enables a key the developer made for it.
05What does Hashlogics actually do on a dental PMS integration?+
We start from each vendor's documented access model, as set out on this page. Then we read what your practice's own account, version and permissions expose during the audit. We scope the build from that, with a Business Associate Agreement in place before the first request, and a named engineer keeps it running after launch.
Related
- AI, automation and custom software for dental practices →The whole dental front desk this integration question sits inside.
- How to automate dental insurance verification →The eligibility write-back, step by step.
- Is an AI receptionist worth it for a dental office? →The booking write-back that needs one of these APIs.
- EHR and practice system integration →How we approach clinical system integration across healthcare.
- Healthcare →The hub: every healthcare area and which page owns each one.
