DrChrono API integration guide: REST API, webhooks and SMART on FHIR

The short answer

DrChrono lets you start building without asking: any account can create an API application (OAuth 2.0 authorization code) and test it. Each practice authorizes your app. Listing in the DrChrono Marketplace needs DrChrono's review. Certified FHIR access runs through a separate, questionnaire-gated path.

How access works

1. Create an API application in a DrChrono account and build in test mode.
2. The practice authorizes each connection through OAuth.
3. Marketplace distribution goes through DrChrono's partner review.
4. FHIR and SMART apps go through DrChrono's questionnaire; DrChrono registers the app and the practice's admin enables it in the app directory. DrChrono's certification page notes developer setup and monthly fees may apply for this path.

What the APIs cover

DrChrono's live API reference renders in the browser, so test against the sandbox rather than relying on static copies of the spec.

Our take

Easy to start, real scheduling endpoints, webhooks: DrChrono is a good EMR for a first integration. Plan for the marketplace review if you want distribution, and keep the FHIR path separate in your scope.

FAQ

Does DrChrono have an API?

Yes, a REST API (v4) with OAuth 2.0, covering appointments, patients, clinical data and billing, plus webhooks.

Do I need DrChrono's approval to use the API?

Not to build and test. Each practice authorizes your app, and marketplace listing requires DrChrono's review.

Does DrChrono support SMART on FHIR?

Yes, through a separate registration path run by DrChrono, after which practices enable the app in their app directory.

Sources

Public pages, accessed 11 Oct 2026: DrChrono API · DrChrono API docs v4 · DrChrono certification and API disclosures · DrChrono Marketplace