Build on the Chairside API

OAuth2 authorization, 22 Graph API collections, standard scopes. Register your app and start building.

How It Works

Chairside uses a standard OAuth2 authorization flow so your application can access practice data on behalf of users. Here’s the process:

  1. Register your app — Create an OAuth2 client in the Chairside developer portal with your redirect URI and requested scopes.
  2. Redirect to authorize — Send users to the Chairside authorization endpoint. They log in and approve your requested permissions.
  3. Receive the code — After approval, Chairside redirects back to your app with an authorization code.
  4. Exchange for tokens — POST the code to the token endpoint to receive an access token and refresh token.
  5. Call the API — Use the access token in your Authorization header to make Graph API requests against any of the 22 collections.

Tokens are scoped per-practice and per-user, so your app only sees data the authorizing user has permission to access.

Code on screen
Analytics dashboard

What You Can Build

The API gives you access to the full clinical and operational dataset. Here are some ideas developers are already exploring:

  • AI diagnostics — Pull radiograph metadata and clinical notes to train or run diagnostic models
  • Analytics dashboards — Aggregate production, collections, and scheduling data across locations
  • Patient communication — Build appointment reminders, recall campaigns, and treatment follow-ups
  • Insurance automation — Read claims data and EOBs to streamline billing workflows
  • Accounting integrations — Sync ledger entries and payment data with QuickBooks, Xero, or your own system
  • Lab management — Connect lab orders and case tracking to external lab portals

If the data lives in Chairside, your app can read it — and in many cases, write it back.

22 API Collections

Every major entity in the system has its own Graph API collection with standard CRUD operations, filtering, and pagination:

Patients Appointments Providers Treatment Plans Clinical Notes Procedures Ledger Entries Insurance Claims Insurance Plans Payments Documents Imaging Prescriptions Lab Orders Referrals Recall Perio Charts Tooth Charts Forms Communications Audit Logs Practice Settings

Each collection supports GET, POST, PUT, and DELETE with consistent response formats and error codes.

Server infrastructure

The API Stays Open

Chairside’s license includes a supplemental term (Section 10.2) that guarantees the API remains open and accessible. This means:

  • No proprietary lock-in — Any application that works with the Chairside API today will continue to work. The API surface cannot be closed or restricted in derivative works.
  • Standard protocols — OAuth2, REST, and JSON are the foundation. No proprietary SDKs required, no vendor-specific authentication schemes.
  • License-enforced — This isn’t just a promise — it’s a legal obligation baked into the Apache 2.0 + Supplemental Terms license. Anyone who distributes Chairside must keep the API open.

Build with confidence. Your integration investment is protected by the license itself.

Start Building

Clone the repo, spin up the API, and make your first OAuth2 call in minutes.

View on GitHub Architecture Docs
HomeVendors & DSOsDevelopersPortabilityArchitectureGitHub