The API Report CardAPI Index
Open Dental

Open Dental API

Dental Practice Management · opendental.com

A documented REST API covers 100+ resource types, but production needs an Open Dental license, a signed BAA per practice, and negotiated pricing for write tiers. Read-only keys are throttled to one request per 5 seconds, and each office must run a local eConnector service.

Last verified: July 2026Healthcare
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublicly documented REST API with 100+ resource types plus a FHIR interface; gating and throttling are access issues, not existence.
AccessFAILNeeds an Open Dental license, a signed BAA per practice, and negotiated pricing for higher permission tiers.
CoverageGOOD100+ resource types cover patients, appointments, procedures, treatment plans, claims, payments, providers, and documents.
AuthFAILStatic Developer Key plus per-customer CustomerKey issued via the portal; key-based only, with no OAuth flow.
Docs & DXFAILDeveloper phone support is explicitly very limited; the community API forum is the official escalation path.
StabilityMIXEDEvery office must run a local eConnector service; connectivity outages or crashes sever the whole integration.
Supergood: Open Dental has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Open Dental scores F on the API Report Card. A documented REST API covers 100+ resource types, but production needs an Open Dental license, a signed BAA per practice, and negotiated pricing for write tiers. Read-only keys are throttled to one request per 5 seconds, and each office must run a local eConnector service.

Tried to integrate with Open Dental?
SOURCES
Read-only API developers (ApiReadAll only) are throttled to one request per 5 seconds per customer, and that interval includes execution time, making bulk reads painfully slow opendental.com
Bursty workloads trigger 429 Too Many Requests responses with Retry-After headers; requests for the same CustomerKey are processed strictly sequentially opendental.com
Remote API depends on an eConnector service running at every dental office, office connectivity outages, Windows reboots, or eConnector crashes break the entire integration opendental.com
Pricing for higher-tier API permissions and write access is not publicly disclosed and is negotiated per developer with Open Dental opendental.com
Phone support for API developers is explicitly very limited; the official escalation path is a community forum opendental.com
FHIR interface lags the primary REST API in coverage and is positioned as legacy / medical-interop only, not a viable replacement opendental.com
Open Dental Cloud freezes and glitches multiple times per day, forcing staff to close and reopen the app between patients and calls capterra.com
UI feels dated and click-heavy versus modern cloud competitors; sheets and forms are difficult to build, and zoom rendering is jagged/pixelated softwareadvice.com
Cannot open two windows simultaneously inside a single session, breaking common multi-tasking workflows g2.com
No included training on accounting, billing, or claims; training and one-off support requests are billed at additional hourly rates softwarefinder.com
Remote/cloud access runs slowly compared with on-premise installs, especially over consumer broadband trustradius.com
Limited out-of-the-box patient engagement (recall, marketing, online booking) compared to Curve and Denticon, practices typically bolt on RevenueWell, Weave, or Yapi getapp.com
Customer support quality is inconsistent, some users praise it, others report unresolved tickets and frequent cache-clearing workarounds capterra.com