Who builds custom Dentrix integrations, and what one costs
Writing to on-premise Dentrix costs a developer $5,000 to register for read access and $5,000 again for write, plus a monthly royalty (Dentrix Developer Portal). That fee is why the list of builders is short and why nobody on it is cheap. This is who is on the list, what each one charges a practice, what the two integration programs allow, and the ACH integration we shipped into Dentrix Classic.
Custom Dentrix integrations come from three places: the product vendor, a listed integration partner, or a developer building for one practice. Prometheus builds the third kind, and our dental payment integration posts cleared ACH payments onto the Dentrix Classic ledger in production today. Our Done-for-You AI Implementation runs $5,000 to $35,000. Bolder Apps publishes $25,000 to $60,000 over 5 to 9 weeks (Bolder Apps). The program itself charges the developer $5,000 for read and $5,000 for write, plus a monthly royalty (Dentrix Developer Portal).
The two doors
Dentrix is two products with two integration programs, and the first thing to settle is which one you run. Dentrix, sometimes called Dentrix Classic or G7, is installed on a server in the practice. Dentrix Ascend is Henry Schein One's cloud product. They do not share a database, and an integration built for one does not run on the other.
| Dentrix (on-premise) | Dentrix Ascend (cloud) | |
|---|---|---|
| Program | Dentrix Developer Program | Dentrix Ascend API Exchange, launched July 2023 |
| How access works | API key and credentials issued after an application, a use-case review, and a signed Dentrix API Agreement; the integration runs on the practice's own machines | Cloud API behind OAuth 2.0; vendors must hold SOC 2 Type II and pass a security assessment |
| Published cost to the developer | $5,000 registration for read, $5,000 for write, plus a monthly royalty by API category | Not published on the Exchange pages |
| Who is in it | Integrated software vendors | More than 140 vendors, listed on the approved-vendor page |
Program facts from the Dentrix Developer Portal FAQ, the Henry Schein One API Exchange and its vendor page, and the Ascend API Exchange launch announcement (July 13, 2023).
Both doors have the same shape: apply, explain the use case, pass a review, sign, then build. Neither is self-serve. That is the first thing a practice should know when a vendor says it "integrates with Dentrix." The question is which program, and whether they are listed.
What the API exposes
The on-premise program's documented surface covers the parts of the chart an integration would need: appointment scheduling, patient demographics, clinical notes, financial records, insurance information, and referral data, reached through documented endpoints and stored procedures (Developer Portal). Read access and write access are licensed separately, which is why the registration fee is quoted per direction.
What that means in practice: a tool that only needs to read the schedule is a smaller integration than one that writes a payment onto a ledger, and the second kind carries more risk, more review, and more cost. Posting to the ledger is the write case, and it is the one where the integration has to prove it cannot post twice.
What does the Dentrix API cost?
The Developer Program's published structure is a one-time registration and set-up fee of $5,000 for read and $5,000 for write, and then a monthly royalty based on the API categories the vendor selects (Developer Portal FAQ). The Exchange pages for Ascend do not publish vendor pricing.
A vendor pays those fees to Henry Schein One and recovers them from practices. That is why an "integration surcharge" appears on so many dental AI plans, and why a vendor with a real Dentrix integration cannot be the cheapest option in the category. It is also why the surcharge is worth asking about: a vendor that charges for integration but is not listed in either program is charging for a workaround.
Who builds custom Dentrix integrations
Three kinds of builder, and one of them is us. Prometheus builds the piece that moves data between Dentrix and one other system a practice already runs, under the practice's rules: a payment processor, a lab, an in-house plan, a workflow specific to how the office works. A Dentrix job sits in the upper half of our $5,000 to $35,000 band, because writing to the ledger has to prove it cannot post the same payment twice.
| Builder | What they build | Published price | Timeline |
|---|---|---|---|
| Prometheus | A custom integration for one practice, between Dentrix and the system beside it | $5,000 to $35,000 | Fixed by scope before work starts |
| Bolder Apps | Custom Dentrix integration development, including roll-ups for groups | $25,000 to $60,000 | 5 to 9 weeks |
| The product vendor | A receptionist, scribe, or billing tool that writes to Dentrix as part of its subscription | Subscription, usually with an integration surcharge | Working on signup |
| A listed integration partner | Integrations built for other software companies, not for practices | Not published | Not published |
Bolder Apps publishes "$25K to $60K" and "5 to 9 weeks" on its Dentrix integration page, checked September 17, 2026. Product vendors are listed on the API Exchange vendor page. Our band is published on Services.
A product is the right answer when it covers the whole job, and a listed partner is the right answer when you are a software company rather than a practice. The custom build is rare because the program fees and the review make it expensive to do once. It is worth it when the gap costs the practice every month and no product is coming to close it.
What a custom Dentrix integration costs
Published bands for a single custom workflow put the version that connects modern tools with APIs at $5,000 to $8,000, and the version that reaches into a legacy system at $15,000 to $25,000 (Layer3 Labs, June 2026). Dentrix on-premise is the second case. Add the program's own fees if the builder is not already registered, and add maintenance: the practice management system updates, the other system updates, and someone has to own the exception queue.
Against that, the cost of the gap. A practice re-keying two hundred payments a month, or reconciling a lab's invoices by hand, or moving plan enrollments between two systems, can put a number on the hours. The build pays back when that number exceeds the build spread over the life of the workflow, and a practice can compute exactly when.
Name the gap before you name the vendor.
The ten questions ask about the work that crosses systems in a normal week. If the answer is a specific gap between Dentrix and something else, that is a build. If it is a phone or a chart, that is a product.
The one we built
Our dental payment integration is the third kind. The practice runs Dentrix Classic and wanted recurring patient payments moved to ACH, which is a fraction of card fees, without a migration and without a second administrative system. The gap was between the payment processor and the ledger: every cleared ACH payment had to reach the right patient account and post without a person re-keying it.
The system runs as a clinic-side service on the practice's Windows workstation. A cloud service carries only the opaque payment event needed to retrieve work. The clinic-side service matches each event to a local patient account or stops for staff, enters the payment into Dentrix through the existing interface, then reads the ledger back and records confirmation or a structured failure. Patient identity never leaves the clinic. Idempotency and deduplication controls mean a retry cannot post twice. Ambiguous matches and reversals enter an exception state that stays visible to the front desk.
It is deployed and running in production. Payment fees moved from ≈2.9% for traditional card processing to ≈0.7% on the ACH path. The productized version, built to run inside Dentrix Classic, is Chomp.
ACH vs credit card processing fees for a dental practice
This is the gap that sends most practices looking for a Dentrix integration in the first place. A smaller practice often pays 2.5 to 3.5 percent of card volume in processing fees, where practices with the volume to negotiate pay 1.8 to 2.2 percent (Private Dental Alliance), while an ACH payment costs $0.20 to $1.50 flat (Ramp). On recurring money, membership plans, payment plans, and orthodontic contracts, that spread is the whole case for a build. The full comparison, including what moving to ACH does not fix, is in ACH vs card processing fees for a dental practice.
Questions to ask any vendor
- Which program are you in, and can I find you on the list? Developer Program for Dentrix, API Exchange for Ascend. If neither, ask what the integration actually is.
- Read, write, or both? A schedule reader and a ledger writer are different integrations with different risks.
- What happens on a duplicate? A retry, a double webhook, a reconnect. The right answer names the control that stops a second post.
- What data leaves the practice, and what stays? One sentence. If it cannot be said in one, it has not been decided.
- What does the system refuse to do? The uncertain match, the reversal, the case that does not fit. Those go to a person or they go wrong.
- Who maintains it when Dentrix updates? A name and a monthly cost, or your own team and a plan.
An integration is a door someone built, with a lock they chose. Ask who holds the key.
What to hold on to
- Two doors, not one. The on-premise Developer Program for Dentrix, the API Exchange for Dentrix Ascend. An integration for one does not run on the other.
- Neither door is self-serve. Application, use-case review, security review, signed agreement. Vendors must hold SOC 2 Type II and use OAuth 2.0 on the Exchange.
- The fees explain the surcharge. Five thousand per direction to register, plus a monthly royalty. Real integrations cost the vendor money, and it reaches your plan.
- Two builders publish a price. Prometheus at $5,000 to $35,000, Bolder Apps at $25,000 to $60,000 over 5 to 9 weeks (Bolder Apps). Product vendors bundle it into a subscription; listed partners build for software companies, not practices.
- A custom build reaching into Dentrix is a low five-figure project. Worth it when the gap costs the practice every month. Ours posts ACH payments into Dentrix Classic and is running in production.
Questions owners ask us
Does Dentrix have an API?
Yes, two. On-premise Dentrix is integrated through the Dentrix Developer Program, which issues API credentials after an application, a use-case review, and a signed agreement. Dentrix Ascend, the cloud product, is integrated through the API Exchange, which requires SOC 2 Type II and OAuth 2.0. Neither is self-serve.
How much does the Dentrix API cost?
The Developer Program publishes a one-time registration and set-up fee of $5,000 for read access and $5,000 for write access, plus a monthly royalty based on the API categories selected (Developer Portal FAQ). Henry Schein One does not publish vendor pricing for the Ascend API Exchange on its Exchange pages.
Who builds custom integrations for Dentrix?
Prometheus does, for one practice at a time: our dental payment integration posts ACH payments into Dentrix Classic with patient matching kept on the clinic workstation, and it is running in production. Bolder Apps publishes $25,000 to $60,000 over 5 to 9 weeks (Bolder Apps). The other two routes are a product vendor that already writes to Dentrix, and a listed partner that builds for software companies.
How much does a custom Dentrix integration cost?
Published 2026 bands put a single custom workflow that reaches into a legacy system at $15,000 to $25,000 (Layer3 Labs), and on-premise Dentrix is that case. Add the program's registration fees if the builder is not already in it, and budget for maintenance when Dentrix or the other system updates.
What can a Dentrix integration read and write?
The documented surface covers appointment scheduling, patient demographics, clinical notes, financial records, insurance information, and referral data (Developer Portal). Read and write are licensed separately. Writing to the ledger is the higher-risk case and the integration has to prove it cannot post the same payment twice.
Is Dentrix Ascend the same as Dentrix for integrations?
No. Dentrix Ascend is the cloud product with its own API Exchange, launched in July 2023, and on-premise Dentrix has the Developer Program. They do not share a database. A vendor that integrates with one has not necessarily integrated with the other, so ask which.
Sources
Program facts and fees are quoted from Henry Schein One and the Dentrix Developer Portal; builder prices from each builder's own page; processing fees from the sources named beside them; the integration from our own record. Checked September 5, 2026, and rechecked September 17, 2026.
- Dentrix Developer Portal, "API Exchange Program FAQs". Application steps, credentials, the API surface, and the registration and royalty fees.
- Henry Schein One, API Exchange and its vendor page. SOC 2 Type II and OAuth 2.0 requirements, the security assessment, and the 140-plus vendor count.
- Henry Schein One, "Henry Schein One Launches Dentrix Ascend API Exchange". July 13, 2023.
- Layer3 Labs, "AI Consulting Rates and Pricing in 2026". Updated June 17, 2026. Custom workflow bands by integration type.
- Bolder Apps, "Dentrix Integration". Published price of $25K to $60K and a 5 to 9 week timeline, checked September 17, 2026.
- Private Dental Alliance, dental card processing costs and Ramp, "ACH processing fees". The card and ACH fee ranges.
- Dental payment integration and Chomp.