Open Dental API Authorization

Status: Draft for legal review Document key: openDentalApiAuthorization Version: 2026-05-31 Use: Clinic onboarding before CustomerKey reveal or connection

By accepting this authorization, the clinic authorizes Happy Light Tech to connect Happy Light AI to the clinic's Open Dental environment for the purpose of providing AI receptionist, scheduling, appointment administration, follow-up, and related workflow support.

1. Open Dental Eligibility

Happy Light AI is currently designed and supported exclusively for US dental clinics using Open Dental as their practice management system. The clinic represents that it actively uses Open Dental for scheduling and appointment administration.

Happy Light AI does not currently support Dentrix, Eaglesoft, Curve, Denticon, or other practice management systems through this onboarding flow. A clinic that does not use Open Dental should not start onboarding checkout or request production activation unless Happy Light Tech separately confirms written support for that platform.

2. Authority

The person accepting this authorization represents that they are authorized by the clinic to configure Open Dental access and connect third-party software.

3. CustomerKey Handling

Happy Light Tech uses a platform-level Open Dental DeveloperKey and a branch-specific Open Dental CustomerKey. The raw CustomerKey should be stored in Google Secret Manager or another approved secure secret store.

The raw CustomerKey should not be emailed, logged, stored in browser local storage, or exposed in public documents. It may be revealed or copied through an explicit audited onboarding action for the authorized clinic user.

4. Permitted Read and Write Access

The clinic authorizes Happy Light AI to read, create, update, cancel, reschedule, and write administrative appointment-related data in Open Dental as configured by the clinic and required to provide the service. Permitted access may include:

• schedule availability;
• appointment types;
• operatories;
• provider or operatory schedule context;
• appointment creation, update, cancellation, and rescheduling context;
• patient matching context required for call handling;
• follow-up and booking status; and
• other administrative data required by the configured workflow.

This authorization does not permit destructive deletion of patient records, clinical records, financial records, or unrelated Open Dental data unless a separate written agreement and explicit product configuration authorize a specific destructive workflow.

5. Scheduling Boundaries

Happy Light AI should use clinic-configured schedule policy, office hours, operatories, appointment type, blockouts, and backend verification logic before creating appointments.

The AI should not guarantee availability before final Open Dental verification. If Open Dental is slow or unavailable, the request should become staff confirmation pending rather than presenting an unverified booking as final.

6. Clinic Responsibilities

The clinic is responsible for:

• ensuring Open Dental data is accurate;
• maintaining correct office hours, blockouts, operatories, providers, and appointment types;
• selecting or creating the Happy Light AI appointment type where required;
• maintaining a reserved non-PHI ghost patient record if required by the workflow;
• reviewing appointments, follow-ups, and staff alerts; and
• revoking access if the clinic stops using the service.

7. No Local Server Access

Happy Light AI does not require local server installation, remote desktop access, screen scraping, router changes, or firewall port opening for Open Dental integration.

8. Revocation

The clinic may revoke Open Dental access according to Open Dental and Happy Light Tech procedures. Revocation may disable scheduling features or cause service interruption.

9. Audit

Happy Light Tech should audit CustomerKey reveal/copy/connect events without logging the raw CustomerKey.