Open Dental API
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.
Frequently asked questions
Open Dental scores F on Supergood's 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.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Open Dental is an open-source dental practice management software (PMS) used by general and specialty dental practices to run their entire clinical and business operation.
Vertical: Healthcare (dental practice management / dental EHR). Front desk staff use Open Dental to schedule appointments on a color-coded Appointments module, run insurance eligibility/benefits, send automated text reminders, collect copays, and post payments.
Open Dental is one of the top dental PMS vendors in the United States and one of the fastest-growing.
Yes, Open Dental is the single system of record for a dental practice.
Founded in 2003 by Dr. Jordan Sparks, a practicing dentist in Salem, Oregon, who started building the system from the back of his own dental practice, his staff doubled as office and support staff, taking developer calls between patients.
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. Bursty workloads trigger 429 Too Many Requests responses with Retry-After headers; requests for the same CustomerKey are processed strictly sequentially. Full sourced list under Sources below.
Common alternatives include Dentrix (Henry Schein One), Eaglesoft (Patterson Dental), Curve Dental, Dentrix Ascend (Henry Schein One), tab32, Denticon (Planet DDS). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Open Dental has partial MCP support. Open Dental has not published an MCP server, but a documented community server built on the Open Dental REST API exposes 14 tools for patients, appointments, and recalls and saw activity in mid 2026. It is not vendor-endorsed and is not listed in the official MCP registry.
Partially. MCP support for Open Dental exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.