API Exchange Program FAQs

The Dentrix API Program is for software developers who already have or plan to create software that integrates with current versions of Dentrix. It offers a channel for Henry Schein ONE to provide Dentrix development tools to software developers and work with them to deliver shared value to our common customers.

Fill out the form on Henry Schein ONE’s API page and click “Submit.”

After submitting an application, you’ll receive a confirmation email that it’s been received. The team reviews the application and will set up a meeting to review your use case and next steps. If approved, the Dentrix API Agreement is sent to be signed before receiving the API key.

API Exchange Vendors | Henry Schein One

Members receive:

  • API key and credentials for Dentrix API
  • API documentation
  • Sample code and development tools
  • Access to the Developer Program Knowledge Base
  • Access to latest Dentrix software (for testing) and product manuals
  • Dentrix product support for install/config issues
Yes, DENTRIX API PROGRAM members can download and install the latest versions of Dentrix from our portal Downloads page.

The Dentrix API Program offers the following API categories:

  • Read API List — Provides read-only access to supported table views, stored procedures, and DLL functions.
  • Write API List — Provides approved write access to supported table views, stored procedures, and DLL functions.
  • Scheduling API — Provides access to scheduling and appointment-related functionality. Not available to non-commercial participants.
  • Claims Summary API — Provides access to summarized claims data for practice level reporting and integration purposes.

Dentrix is an on-premise application, and the Dentrix API is designed for on-premise integrations. This means your team is responsible for building and then deploying your application locally within each office environment.

A typical integration flow looks like this:

  1. Your signed application authenticates using the RegisterUser function, which allows GetConnectionString to return the credentials needed for ODBC access.
  2. Your application then uses the API and/or ODBC connection to query Dentrix data.
  3. From there, you determine how the data is used or transferred (for example, syncing it to a cloud-based system).
Yes. However, because the Dentrix API runs locally, the API member must install a local desktop application or service to securely communicate with the cloud-based application using industry’s best practices.
No. The License Agreement prohibits transferring, selling, distributing, disclosing, sublicensing, or lending the API key; violations result in termination of the agreement and access.

The focus of the program is to provide API access to third-party developers. We’re here to confirm your access setup, point you to the right endpoints, and help interpret API errors. We don’t build or debug your app code, but we can validate that the platform side (auth, connectivity, and API behavior) is working as expected.

Common languages like C#, C++, Java, etc., via password-protected ODBC connection.
API queries can be run from any Dentrix server or workstation.
DENTRIX API PROGRAM provides an alternate JDBC driver that is available for download from the Resource Center > Downloads page. We do not develop that driver but have not had any issues.
No, there is no HL7 interface supported.
Two costs: a one-time registration and set-up fee ($5,000 READ, $5,000 WRITE) and a monthly royalty fee based on API categories selected. No start-up pricing, or access prior to joining the program. There is a singular pricing model that applies to all.
Yes — usage charges apply regardless of usage type.
Certain software types (e.g., patient financing, credit card processing, insurance claim processing) or non-commercial API accounts aren’t allowed in the program or marketplace.
Commercial memberships do not require renewal—the contract remains active unless canceled with 60 days’ notice. Non-commercial memberships are billed annually on the original start date unless canceled.
No trial option exists; however, the full list of API functions is published on the FAQ.
Henry Schein ONE does not share or divulge what it considers to be intellectual property (IP) of Dentrix.
No, Henry Schein ONE does not share or divulge the data dictionary or schema.
  1. Login at the Dentrix API Portal: https://ddp.dentrix.com/
  2. Go to Resources > Support Ticket
  3. Submit the Support ticket form choosing a Dentrix Category
The Dentrix Ascend API Program is for software developers who already have or plan to create software that integrates with Dentrix Ascend. It provides a channel for Henry Schein ONE to offer Dentrix Ascend development tools and collaborate to deliver value to shared customers.

Click the “Sign Up” link:

API Exchange Vendors | Henry Schein One

After you submit an application, you’ll receive a confirmation email that it has been received for review. The team reviews the application and will set up a meeting to review your use case and next steps. If approved, the Agreement is sent to be signed before proceeding with your initial Sandbox Access to begin development and testing.

Members receive:

  • API key and credentials to access the Dentrix Ascend API
  • API documentation
  • Sample code and other API development tools
  • Initial Access to a Dentrix Ascend sandbox for development & testing. (60 Days)
  • Dentrix Ascend product support for installation and configuration issues
Yes — the sandbox will always have the latest version of Dentrix Ascend and the latest documentation.

There is currently one type of API available through the Dentrix Ascend Developer Program. The Dentrix Ascend data API provides a library of functions that read and write data from the Dentrix Ascend database. After signing an agreement, you receive portal access to available endpoints across: Clinical, Schedule, Treatment, Insurance, Financial, Patient, and General categories.

Reference link: Public API

Dentrix Ascend is a cloud-based platform, so integrations are fully remote and do not require on-premise deployment. A typical flow looks like this:

  • Your application authenticates using API credentials (API key and organization context).
  • Your app makes HTTPS requests to Ascend API endpoints to retrieve or update data (e.g., patients, appointments, procedures).
  • You implement your own logic for syncing, storing, or acting on that data within your system (e.g., triggering workflows, analytics, or patient communications).
  • Optionally, you can subscribe to Streaming API events to receive near real-time updates instead of relying solely on polling.
  • Deployment: No local installation required; integrations run externally against cloud endpoints.
  • Access Method: RESTful HTTPS API instead of ODBC/database access.
  • Authentication: API key-based vs local user registration and connection strings.
  • Data Flow: Designed around API calls and event-driven patterns rather than direct database queries.
  • Scalability: One integration can support multiple locations without per-office installs.
No. The Developer Agreement prohibits transferring, selling, distributing, disclosing, leasing, syndicating, sub-syndicating, lending, or sublicensing the Dentrix Ascend API (including the API key) or redistributing data retrieved through the API to unauthorized parties. Violations result in termination of the agreement, API key, and access privileges.
The Dentrix Ascend API is accessed through REST API endpoints, with POST and GET requests sent/returned in JSON format.
No — Dentrix Ascend does not currently provide or support an HL7 interface.
  • A one-time $5,000 registration and set-up fee
  • A monthly $47 fee for each Dentrix Ascend Location, which includes 30K calls and 3GB data per location/per month
  • Overage charges for excess usage at $0.0018/call and $1.00/GB data
No — there currently is no application certification process available to API members.
Currently there are two programs: Dentrix and Dentrix Ascend.
No. Henry Schein ONE does not perform Beta testing for third-party products. You can do your own internal testing in your sandbox.
No. Henry Schein ONE does not make customer lists available to any third parties. You will be added to our API website as an approved vendor.
No — due to the volume of products/services being sold, it isn’t feasible for FSCs and other Dentrix Ascend sales reps to promote/sell members’ applications. Henry Schein ONE does not ensure traction in sales channels; introduction and product training in sales channels are reserved for highest-level partnerships.
No. The only fees members pay are their initial registration fee and monthly access fees.
No. Henry Schein ONE does not share or divulge what it considers to be Dentrix Ascend intellectual property (IP).
The Dentrix Ascend API documentation here contains the available schemas.