For dental technology products, DSO platforms and integration leads
Connect your dental product to the practice management systems your customers run. We compare the access route for Dentrix, Eaglesoft, Open Dental and Curve Dental, then build one application contract with an adapter per system, tested office by office.
Discuss my dental integrationFor dental software companies and DSO technology teams. Updated October 17, 2026.
Henry Schein One API Exchange
Patterson Innovation Connection
Developer key and per-office customer key
API key on request from Curve Account Management
Illustrative workflow · scope tailored to your environment
The short answer
All four have a route, but only Open Dental publishes self-serve API documentation and pricing. Dentrix access runs through Henry Schein One's API Exchange, Eaglesoft through Patterson's Innovation Connection program, and Curve Dental through a request to Curve's Account Management team. None of the other three offers a self-serve key, so plan the vendor approval alongside the engineering.
Read our dental practice management API guideStart with the real problem
A dental product usually needs the same few actions everywhere: read the schedule, book or move an appointment, match a patient, post a payment or form. The systems differ in hosting, in who grants access and in how long approval takes. Teams that build for one system first often find the second needs a different access plan, not just a new adapter.
Your starting point
Your receptionist or booking product needs live schedules and confirmed appointments across several dental systems.
Your product sends reminders, collects forms or takes payments and must keep records in step in each system.
A group runs offices on more than one system and needs a combined view or a migration plan.
The Engineering Engagement
Workstreams are selected around your priorities. Each comes with an output your team can inspect, test and own.
List the systems your customers run, prepare the Dentrix and Eaglesoft partner applications and the Curve access request, and set up Open Dental developer and customer keys. Track approvals as a dependency in the plan.
Define the schedule, appointment, patient and payment objects your product uses once, then map each system to it. Record the actions a system does not support so the product hides them.
Build booking, patient matching, forms and payment posting per system. Confirm each write only after the practice system accepts it.
Enable each office, verify its configuration and monitor failed requests. Hand staff the context to resolve exceptions.
Compare your options
What each vendor publishes about third-party access, as read on October 17, 2026. Confirm current terms with the vendor before you plan a release.
| System | Hosting | Access route | Public developer documentation | Our page |
|---|---|---|---|---|
| Dentrix and Dentrix Ascend (Henry Schein One) | Dentrix is installed in the practice; Dentrix Ascend is cloud-based | Henry Schein One API Exchange application and agreement | Portal for approved vendors; Ascend Public API described as over 700 REST endpoints | Dentrix integration services |
| Eaglesoft (Patterson Dental) | Installed in the practice | Patterson Innovation Connection program for third-party vendors | Not published openly; provided through the program | Covered on this page |
| Open Dental | Installed in the practice, with remote and local API modes | Developer key plus a customer key each office enables | Published API documentation, permissions and pricing | Open Dental API integration |
| Curve Dental | Cloud-based | API access requested from Curve Account Management | We found no public self-serve developer portal | Covered on this page |
Hosting and access statements come from each vendor's own pages listed under sources. Practice software versions and partner terms change; we recheck them at the start of every project.
Expertise is in the decisions
Rank systems by your customers' offices and by approval lead time. Open Dental can usually start while access requests for the others are under review.
Dental API intermediaries cover several systems at once. Compare coverage, recurring fees, data latency and support ownership with direct access for your workflow.
Read approval does not establish write approval. Confirm each action per system and design recovery for ambiguous responses.
Development cost depends on operations, mappings, customer configurations and failure handling. Vendor charges and onboarding lead time are assessed separately from engineering effort.
This service page describes work we can scope. It does not establish a vendor partnership, a marketplace listing, a pre-approved connector or a completed deployment for your customer.
Production permissions, commercial terms and clinical sign-off remain with the appropriate customer and vendor owners. We identify these dependencies during discovery.
From discussion to delivery
Agree the users, data, actions and access dependencies. Return a supported-operation map and an estimate with assumptions.
Build the selected connection and test ordinary requests and failures with authorized test data. Label sandbox results separately from production evidence.
Validate the agreed workflow in the customer environment, assign support ownership and complete the approved cutover.
We agree the scope, dependencies, acceptance criteria and commercial model before implementation. Your existing team can stay involved throughout.
Find the right starting point ↗Open Dental publishes its API documentation, permissions and pricing. Dentrix and Eaglesoft give access through vendor partner programs, and Curve Dental issues API access on request through its Account Management team. Each needs vendor agreement first.
Patterson Dental offers integration with Eaglesoft to third-party software vendors through the Patterson Innovation Connection program. Technical documentation is provided through the program, not published openly, so plan for an application and approval.
Curve Dental lists integration partners for payments, patient engagement, reputation and other categories. Curve's support center directs API access requests to its Account Management team. We found no public self-serve developer portal, so plan for Curve to confirm eligibility and terms.
Yes. See our Dentrix integration services and Open Dental API integration pages for system-specific access, scope and questions.
Sometimes. An intermediary can cover several systems faster, at a recurring cost and with its own coverage limits. We compare it with direct access against your actual workflow.
We estimate after confirming the systems, operations, data mappings and office rollout. The proposal separates engineering work, vendor or intermediary charges and dependencies that affect delivery.
We can plan work and identify dependencies, but the rollout date depends on vendor approval, office configuration and acceptance. We agree milestones after the access review.
A useful first conversation
Tell us what exists today, who uses it and where the workflow breaks. We’ll discuss the scope, access dependencies and the next practical step.
A product overview and a de-identified workflow are enough to start. No patient records or credentials are needed.
These are independent reference sources, not endorsements. Applicability, platform access and current requirements are confirmed for your project.
