Dental Group CRMby The Goodstack Company Discuss a workflow

PMS integration guide

Dental API access: Open Dental, Dentrix, Ascend, Denticon and CareStack

Start with the exact practice-management product and one action. Compare native and intermediary access, then record who can authorize each operation and what still needs testing.

Start with the exact product and one action

A group evaluating a CRM or communication tool needs a specific answer: can this integration read or change the required record in our version of the practice-management system, and what does access cost?

We reviewed the public vendor sources below on October 7, 2026. These are published terms and capabilities, not integrations we have delivered or tested. Confirm current terms in writing before committing to a project. An API's existence does not establish access for your organization.

Access comparison · Open Dental · Dentrix desktop · Dentrix Ascend · Denticon · CareStack · Intermediaries · Feasibility checklist

Access comparison

All rows reviewed October 7, 2026. Published amounts are in USD and are API program charges, separate from implementation work and the practice's software subscription.

Product and official documentationAccess prerequisitesPublished cost basisRead/write evidence and unresolved scope
Open Dental setup and permissionsDeveloper enrollment, developer/customer keys; office enables accessMonthly tiers per location; details belowPublic permission and method lists. Check version, mode and required fields.
Dentrix desktop FAQProgram approval and local component for cloud connectionsRead/write setup and category royaltiesLocal API; exact methods and version support need confirmation.
Dentrix Ascend FAQApproved application, agreement and sandbox accessSetup, monthly location fee and overagesRemote REST read/write access described; confirm permissions.
Denticon portal and resourcesAccount and vendor-approved access need confirmationNo price found on the reviewed pagesPublic read/write descriptions; endpoint entitlements remain unverified.
CareStack portalSignup; confirm approval, credentials and location authorizationRegistration, minimum, location fee and overagesPublic read/write descriptions; exact endpoint access needs confirmation.

Open Dental

The developer setup instructions describe enrollment and a developer key paired with a customer key. The practice enables the API. Remote mode requires a running eConnector. Confirm the mode before deciding where integration code will run.

The permissions page publishes these monthly tiers per location:

  • Read All: free, throttled to one request every five seconds.
  • $15: Comm, Documents, InsuranceSimple, Setup and Queries; one request per second.
  • $30: all permissions except Payments, PayPlans and Special.
  • $35: all permissions except Special.

Charges begin when a key is assigned and enabled, and stop when disabled. Confirm special permissions and how your locations map to billing before estimating a group total.

The API specification documents resources and HTTP methods; availability depends on the method and version. An omitted field in an update is left unchanged. Check a read, a write, a correction and a failed request for your workflow. The similarly named API Fees page concerns fee records inside the PMS; API access prices appear on the permissions page.

Dentrix desktop

The official FAQ describes a local API. A cloud application needs a local component. It lists $5,000 setup for read and $5,000 for write, plus monthly royalties by category. Obtain a written scope and quote; this is not a complete location budget. We have not tested the gated tools.

Dentrix Ascend

Ascend is a separate cloud product and access program. The vendor FAQ describes application review, agreement and sandbox access. Published charges are $5,000 setup, then $47 per location per month including 30,000 calls and 3 GB. Overages are $0.0018 per call and $1 per GB. Confirm endpoints, production approval and organization permissions before estimating a sync.

Denticon

The Planet DDS portal describes patient creation and updates, appointment booking and changes, financial reads, REST, webhooks and batch extracts. The resource index is a starting point for requesting detailed endpoint access; its publicly readable response did not expose that catalog in this review.

We verified those public descriptions, not detailed endpoint entitlements. We found no fee schedule or complete onboarding requirements on these pages. Ask for approval steps, a location quote, limits and the exact write permissions needed. A resource category is not proof that every desired field can be changed.

CareStack

The official developer portal describes patient creation and updates, accounting summaries, communication and documents. It offers REST APIs, webhooks and scheduled extracts.

Published pricing is $5,000 registration, a $100 monthly minimum, and $60 per location per month for 10,000 transactions. Additional transactions cost $0.004 each. Confirm how the minimum and location charges combine, what counts as a transaction, and which resources your account can use. Signup is available, but production approval and endpoint-level access were not verified in this review.

An intermediary is a separate access path

NexHealth's API introduction describes one API connecting multiple health-record systems, with a developer account, test key and sandbox. That is an intermediary, separate from joining a PMS vendor's native API program. The introduction does not provide a complete production or per-location quote.

Ask about the exact PMS version, connector method, read/write coverage, connection ownership, production approval and failed synchronization. Native vendor charges must not be assumed to be included in or replaced by the intermediary's price.

For Open Dental specifically, read its third-party integration status and warnings. That page includes concerns about NexHealth. Resolve this vendor position directly; a generic connector claim does not establish an approved integration. We have not independently tested either company's integration claims.

A feasibility checklist for one workflow

Before selecting software, name one action. Keep patient details out of the initial assessment. Copy the following fields into your project notes and complete one record for each operation, splitting reads from writes:

  • Product and edition: exact PMS name, version/build or cloud edition, and affected locations. Do not shorten Dentrix desktop and Dentrix Ascend to the same product name.
  • Action and owner: who needs the result, what triggers it and which system holds the authoritative record.
  • Access owner and method: the practice administrator who can authorize access; native API or named intermediary; local, remote or other documented connection mode.
  • Read scope: record type, minimum fields and location boundary. Add the endpoint, method, documentation link and supported version.
  • Write scope: exact create/update action and fields, or “none required.” Record its permission separately from read access.
  • Prerequisites and cost: account approval, keys, local components, agreements and a dated quote covering setup, minimums, locations and overages. Record who can revoke access. Do not put keys in the worksheet.
  • Evidence and test status: documented, access confirmed, tested in the stated environment, or unknown. Include test date, expected result and actual result; a documentation link cannot fill in a test result.
  • Failure and reconciliation: duplicate request, denied permission, unavailable connection, stale read and interrupted write. Name the person who investigates an uncertain result before retrying.

A completed example with deliberate unknowns

Synthetic demonstration: invented records. A fictional two-location group wants a coordinator to see whether a referred appointment is recorded, while keeping appointment changes in the PMS. No real practice or patient is shown, no practitioner has reviewed this example, and no API request was run for it.

Feasibility fieldExample entry
Product, access method and ownerOpen Dental, Remote API; office version unknown. Group IT requests access and each office administrator confirms authorization. eConnector availability is unknown.
Required readAppointment status and the minimum identifiers needed to match the administrative referral. The permission list includes Appointments GET. Exact response fields, matching rules and office version support remain to be checked.
Required writeNone for this first scope. A coordinator changes the follow-up owner in the proposed workflow layer; this does not authorize appointment edits in the PMS.
Evidence and environmentVendor documentation reviewed; office access unconfirmed; approved synthetic test environment not yet agreed; read and write tests not run.
Acceptance check to runRead a known synthetic appointment, change it through the approved PMS workflow, and confirm the next read reflects that change. Check revoked access and an unavailable connection too.
Failure routeIf the read fails, show “status unavailable” with the last successful check time. The coordinator verifies status through the office's approved process; an old value must not silently become a current answer.

The result is a scoped question for the access owner. The feasibility test is still outstanding. A documented read, permission to perform it and a successful test are three different pieces of evidence. Leave the implementation decision open until the required pieces exist.

For a referral project, use the cross-location referral audit to decide which acknowledgment or status is actually missing before requesting more fields.

Configuring the existing PMS may solve the problem. If a separate workflow layer is justified, the chart, schedule and ledger need clear ownership. Our CRM versus PMS worksheet helps draw that boundary.

Our experience and the limits of this guide

This is our first dental work. We build custom software and therefore benefit when a buyer chooses a build. We have no partnership or endorsement from the vendors listed here. Published access is not a compliance determination or delivery promise. We have not read every gated document, obtained production access or tested these products through this review.

Discuss one group workflow

We start with one workflow and a few of your people, on your own data.

Discuss a group workflow