Contents
- The Short Answer: Who Can Get Access and What It Costs
- What the API Can and Cannot Do
- How to Actually Get Connected
- Three Automations Practices Want, and How to Reach Them
- When There Is No Connection: The Workaround and Its Risks
- Time to Build and Running Cost
- What Breaks
- Not Sure Which Route Fits Your Practice?
- Sources
- FAQ
The Short Answer: Who Can Get Access and What It Costs
Dentrix and Ascend by Dentrix share one integration route: the Henry Schein One API Exchange. Henry Schein One describes it as "open to all and simple to join, giving authorized integration vendors access to practices". The word that matters is vendors. The practice page tells you to "reach out to your preferred authorized vendors on our Approved Vendors list". Checked on henryscheinone.com on 17 November 2026.
| Route | Who it is for | Cost, as published |
|---|---|---|
| Use an authorized vendor's product | Any Dentrix or Ascend practice | The vendor's own subscription. The API cost is inside their price. |
| Become an authorized vendor (or hire one) | A software company, or a builder doing custom work | A program fee, a signed agreement and a security review. The fee amount is not published. |
| Legacy Dentrix Developer Program certification | Developers certifying a product against Dentrix | $2,500 one-time (Basic, read only), $5,000 (Plus, UI integration), $5,000 (Pro, read/write). Upgrades $1,250 to $2,500. The page refers to Dentrix G5. |
| A practice's own API key | Not offered | No published route |
Henry Schein One's own blog sums up the vendor side: to join, vendors must "pass a security test", "sign an agreement" and "pay a program fee". Other sites quote specific registration fees and monthly per-site royalties. We could not find those numbers on any Henry Schein One or Dentrix page on 17 November 2026, so we do not repeat them. Ask the API Exchange team for the current schedule through the vendor form on henryscheinone.com.
What the API Can and Cannot Do
Henry Schein One describes the API as a way for third-party vendors "to ask the Dentrix database for information (datapoints) they want to use in their software application and send data back to Dentrix or Ascend by Dentrix". It quotes "700 Endpoints" in one place and "1,000 endpoints" in another on the same page. The endpoint reference itself is given to vendors, not published.
| Question | Answer | Source of the answer |
|---|---|---|
| Can an authorized vendor read practice data? | Yes | Henry Schein One practice FAQ |
| Can it write data back? | Yes, per the FAQ wording | Which objects can be written is not public |
| Is there a public endpoint list? | No | Documentation is a vendor benefit |
| Does it cover both Dentrix and Ascend? | Yes | API Exchange pages |
| Can a practice connect any tool it likes? | Henry Schein One says to use authorized vendors only | It lists vendors that "may be utilizing an unauthorized connection" |
| Security requirement | SOC 2 Type II and OAuth 2.0 | The practice FAQ says vendors are held to both |
That last row is the real barrier for small custom builds. A freelancer or small agency is unlikely to hold a SOC 2 Type II report. So for most single practices, the realistic custom route is to build on top of an authorized vendor that already has access, not to get access yourself.
How to Actually Get Connected
If you are a practice:
- Open the authorized vendors page on henryscheinone.com and confirm the tool you want is listed.
- Scroll to the second list on the same page: vendors Henry Schein One says may be using an unauthorized connection. If your current or planned tool is there, ask it directly how it connects.
- Ask the authorized vendor whether its own product has an API or webhooks you can use. That is your automation hook.
- Sign a business associate agreement with every vendor that will touch patient data.
If you are the builder (or the vendor): Henry Schein One lists four stages: vendor contact, security review, set up (the integration is set up and tested), then active. You start with the form on the API Exchange vendors page. No timeline is published, and the fee is discussed with their team.
Plan for weeks, not days. That is our estimate, not a published figure: a security assessment and an agreement take time on both sides.
Three Automations Practices Want, and How to Reach Them
1. Recall and reactivation messages. Patients overdue for hygiene get a sequence of reminders, and the sequence stops when they book. Patient-communication tools on the authorized list are built for this. The custom part is usually the rules: who to skip, how many touches, when to hand over to a person.
2. Unscheduled treatment follow-up. Accepted but unbooked treatment plans are revenue sitting in a report. The logic is the same as our Open Dental unscheduled treatment follow-up build; only the data route differs.
3. New patient intake from the website. A web form or AI receptionist collects details and creates the patient record so the front desk is not retyping. On Dentrix that write needs an authorized connection.
Worked example: recall messages through an authorized vendor
An illustrative single-location practice with roughly 300 patients falling due for recall each month. It already pays an authorized patient-communication vendor.
- Step 1: confirm the vendor is on the authorized list and ask whether it exposes an API or webhooks for "recall due" or "appointment booked".
- Step 2: if it does, a small workflow sits on the vendor's API: it applies your rules (skip patients with open balances over a limit, or with a booked visit), and escalates non-responders after the third touch to a call list.
- Step 3: if it does not, use the vendor's built-in recall feature as is, and automate only the call list from a report export.
Cost: no Henry Schein One fee to you, the vendor's existing subscription, plus a one-off build. Compare that with Open Dental, where the practice itself turns API access on and adds a developer's key under Setup > Advanced Setup > API (per Open Dental's API setup page, checked 17 November 2026); our Open Dental API recall guide shows that route.
When There Is No Connection: The Workaround and Its Risks
If no authorized vendor does what you need, you still have safe options:
- Automate around Dentrix, not inside it. Missed-call text back, review requests and web enquiries can run without touching the practice management system at all. See missed call text back with n8n.
- Report exports with a person in the loop. A team member runs a report and drops it into a secure folder; the workflow does the rest. Slower, but nothing connects to the database.
- Ask Henry Schein One. If the job is valuable to many practices, a vendor may build it.
The risks of the shortcut. Tools that read the Dentrix database directly, or sync agents installed on the server, are exactly what Henry Schein One's unauthorized list is about. You risk breaking your support terms and a data path nobody vetted. Patient data adds HIPAA on top: any tool or builder handling protected health information needs a business associate agreement with you. We could not find a public Dentrix BAA page on 17 November 2026; ask your Henry Schein One account rep for theirs, and ask each vendor for its own. This is not legal advice.
Time to Build and Running Cost
Market-typical ranges for small-business automation in 2026, not a8gent prices:
- Using an authorized vendor's feature: days to set up, cost is the vendor's subscription.
- A custom workflow on an authorized vendor's API: roughly $2,000 to $6,000 one-off, 2 to 4 weeks, plus hosting at roughly $0 to $50 a month.
- Becoming an authorized vendor yourself: an unpublished program fee, a security review and an agreement. Rarely worth it for one practice.
- Automations around Dentrix (calls, reviews, web leads): roughly $1,000 to $4,000 one-off.
Our AI receptionist cost for dental practices page covers the phone side, and AI automation for dental practices lists the other workflows worth doing.
What Breaks
- A vendor loses authorized status. Your automation built on its API stops with it. Check the list every few months.
- Software upgrades. The legacy certification page says upgrades that affect the API require recertification. Expect integrations to need attention after major Dentrix updates.
- Duplicate messages. The vendor's built-in recall and your custom sequence both fire. Switch one off.
- Exports go stale. If a person forgets the weekly report, the workflow runs on old data. Alert on file age.
- Patient data in the wrong place. A spreadsheet in a personal drive with patient names is a breach risk. Keep exports in a system covered by a BAA.
Not Sure Which Route Fits Your Practice?
Send us the tools you already pay for and the job you want automated. In the free automation audit we check your vendors against the authorized list, tell you whether an existing product already covers the job, and scope a build only where it adds something. If it is worth doing, our automation services team builds it and hands it over with plain reports on what ran.
Sources
All checked on Henry Schein One and Dentrix sites on 17 November 2026.
- Henry Schein One API Exchange - "open to all", authorized vendors, endpoint counts, SOC 2 Type II and OAuth 2.0.
- API Exchange for Practices - the four onboarding stages and the practice FAQ.
- API Exchange Vendors - how vendors apply.
- Authorized and unauthorized vendors list
- Dentrix blog: Your Guide to API Integrations - security test, agreement and program fee.
- Dentrix Developer Program - legacy certification charges (Certification page).
- Open Dental: API setup - for the comparison only.
FAQ
- How much does the Dentrix API cost?
- Henry Schein One does not publish a price. Vendors join the API Exchange by passing a security review, signing an agreement and paying a program fee. A practice usually pays indirectly, through an authorized vendor's subscription. The legacy Dentrix Developer Program page lists one-time certification charges of $2,500 to $5,000, but it refers to Dentrix G5.
- Can my dental practice get its own Dentrix API key?
- Not through any route Henry Schein One publishes. Practices are told to work with vendors on the authorized list. A builder doing custom work would need to apply as a vendor and pass the security review.
- What is the Henry Schein One API Exchange?
- It is the integration program for Dentrix and Ascend by Dentrix. Authorized vendors connect through it to read practice data and send data back. Henry Schein One says it has over 140 authorized vendors.
- How do I know if a Dentrix add-on is authorized?
- Check the authorized vendors page on henryscheinone.com. The same page lists vendors Henry Schein One says may be using an unauthorized connection, and notes that list is not complete.
- Does the Dentrix API work with Ascend?
- Yes. The Henry Schein One API Exchange covers both Dentrix and Ascend by Dentrix.
- Can I automate Dentrix without the API?
- Partly. You can automate work around Dentrix, such as missed-call text back, review requests and web enquiries, and use report exports with a person in the loop. Tools that read the database directly may be unauthorized, and any tool touching patient data needs a business associate agreement.
- How long does it take to get Dentrix API access?
- Henry Schein One does not publish a timeline. Vendors go through contact, security review, setup and testing before going active. Plan for weeks rather than days.
If this resonated
Module 02 is the long version of this post.
Eval set, refusal pattern, kill switch. Build it in a weekend.
