Skip to contentNew Learn why APIs are the future Read the article →

Open Dental API workflows

Open Dental API integration for custom workflows

Open Dental publishes a substantial API. Zatanna is for the workflow gap: the action that falls outside the endpoint you have, depends on office-specific session state, or still requires a portal path your product cannot reliably automate.

YYC W26 · Built for production request workflows
Classical engraving of a scholar studying at a desk, illustrating Zatanna's editorial law-meets-AI aesthetic

Access strategy

Use the official API where it fits. Scope the workflow gap separately.

The strongest integration architecture does not force every action through one access method. Keep published Open Dental resources for the data and operations they expose. Use Zatanna when the decisive workflow is missing, highly specific, or tied to request sequences behind the portal.

Existing access

Published Open Dental access

Open Dental documents Remote, Local, and Service API modes, office-level enablement, developer and customer keys, and a broad resource catalog.

  • Remote API setup requires the office's eConnector to be running.
  • Remote requests use both a developer key and an office-specific customer key.
  • List responses default to a hard limit of 100 items per request.
  • Remote throttling varies by permission tier, including one request per five seconds for read-all-only access.
Read the official Open Dental API documentation ↗

Workflow layer

Zatanna workflow access

Zatanna maps the underlying request flow for one required action and exposes it as a clean endpoint your product or agent can call.

  • Shape the endpoint around the product workflow, not a fixed object catalog.
  • Handle authentication, cookies, session refresh, and request sequencing beneath the endpoint.
  • Avoid maintaining screenshot-driven browser scripts for repeatable production work.
  • Detect and repair integration behavior when the underlying portal changes.

Workflow examples

Bring the blocked workflow, not a feature wish list

These are scoping patterns—not claims of prebuilt Open Dental endpoints. Start with the exact operation your product cannot complete reliably today.

01

Complete a multi-step office workflow

Package the request sequence behind a repeatable office task into one product-facing endpoint.

02

Reach data beyond the current endpoint shape

Return the fields and structure your agent needs when the published response does not match the downstream workflow.

03

Replace a brittle portal script

Move a production workflow off selectors, screenshots, and page timing without asking your agent to supervise a browser.

How Zatanna works

From portal path to production endpoint

01

Show the blocked action

Bring the exact portal workflow, software environment, and current failure mode. Zatanna scopes feasibility from the real request path.

02

Map the request flow

Zatanna reconstructs the calls, authentication state, session behavior, and sequencing underneath the workflow.

03

Call one endpoint

Your product or agent sends explicit inputs and receives a structured response. Zatanna monitors the integration beneath that contract.

Bring one blocked workflow. We'll turn it into a production API.

30-minute working session
FAQ

Common questions

No. Open Dental publishes and operates its own API. Zatanna is an independent workflow-access layer for actions that are not a clean fit for the published endpoint or that depend on portal request behavior.

Not by default. Use the official API for supported resources and operations. Add Zatanna for the workflow gap so your product does not have to fall back to brittle browser automation.

You show the required workflow once. Zatanna reconstructs the underlying network request flow, manages the necessary auth and session behavior, and exposes the action through a stable endpoint.

The endpoint is scoped around the workflow your product needs, including the inputs and structured response shape. Exact feasibility is confirmed during the workflow review.

Source notes

Vendor facts on this page come from the official documentation below. Zatanna does not claim vendor partnership or prebuilt endpoint coverage on these pages.