DrChrono API
DrChrono by EverHealth is a cloud-based EHR and practice management platform that combines clinical documentation, scheduling, medical billing, telehealth, and patient engagement for independent medical practices. An API lets you programmatically pull patients, appointments, clinical notes, documents, and billing line items—and push updates like new appointments, charges, and uploaded chart documents back into DrChrono.
What is DrChrono?
DrChrono by EverHealth is a cloud-based electronic health record and practice management platform that integrates clinical documentation, scheduling, billing, and patient engagement tools for independent medical practices. Practices use DrChrono to document encounters, run real-time appointment scheduling with automated reminders, verify insurance eligibility, process claims and denials, conduct telehealth visits, and collect patient payments—serving specialties from family medicine and pediatrics to psychiatry and counseling across solo and multi-location clinics.
Core product areas include:
- EHR (clinical documentation, charting, and clinical notes)
- Practice Management (scheduling, calendar, and appointment reminders)
- Medical Billing / Revenue Cycle Management (claims, eligibility, denial management)
- OnPatient Patient Portal (secure messaging, digital forms, online intake)
- Telehealth (secure virtual visits) and Patient Check-in
Common data entities:
- Patients, Demographics, Insurances, Eligibility
- Appointments, Breaks, Schedules, Appointment Profiles
- Clinical Notes, Problems, Medications, Allergies, Lab Orders/Results
- Documents, Line Items, Procedures, Diagnoses, Billing Profiles
The DrChrono Integration Challenge
DrChrono publishes a public OAuth 2.0 REST API, but building reliable production automation on top of it still has real friction:
- OAuth 2.0 app registration: Each integration needs a registered application, redirect-URI flow, and per-provider consent before any data can be accessed
- Short-lived tokens: Access tokens expire after 48 hours and must be refreshed with refresh tokens, so headless jobs need durable token lifecycle handling
- Mandatory pagination: Listing endpoints like /api/patients are paginated and require iterating next pointers; the standard page size caps at 250 records
- API versioning: Behavior varies by version, pinned per application or via the X-DRC-API-Version header, so integrations drift as DrChrono ships new versions
- Permission-scoped access: Tokens only see data the granting provider can access, so multi-provider practices require careful scope and account mapping
- Mixed payload handling: Nested clinical objects are JSON while chart-document uploads use multipart, and some resources expose separate bulk endpoints (up to 1000 rows) for large exports
How Supergood Creates DrChrono APIs
Supergood wraps DrChrono's OAuth 2.0 REST API—and the authenticated web surfaces behind it—to deliver a resilient, normalized API layer for your practice, handling token lifecycle, pagination, and versioning so you integrate once.
- Manages the full OAuth 2.0 flow, 48-hour access tokens, and automatic refresh-token rotation
- Transparently iterates paginated and bulk endpoints so you receive complete result sets without managing next pointers
- Normalizes responses across patients, appointments, clinical notes, documents, and billing line items into consistent objects
- Pins and adapts to DrChrono API versions and per-provider permission scopes to keep access compliant
Use DrChrono with AI agents: DrChrono MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your DrChrono modules, provider accounts, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready DrChrono adapter tailored to your practice's resources and permission scopes.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as DrChrono evolves its API versions.
API Endpoints
Authentication
/authenticateComplete the DrChrono OAuth 2.0 flow and obtain access and refresh tokens for downstream calls.
Patient Operations
/patientsList and filter patients by name, gender, and date of birth across a paginated result set.
Scheduling
/appointmentsRetrieve appointments and breaks from a provider's calendar with date and status filters.
Scheduling
/create_appointmentCreate a new appointment on a doctor's calendar with patient, office, and exam-room details.
Clinical
/clinical_notesAccess raw clinical notes, problems, medications, and lab data for an encounter.
Billing
/create_line_itemPost billing line items, procedures, and diagnoses against an appointment for claims processing.
Use Cases
Sync patient and appointment data to your stack
- Pull patients, demographics, and insurance records into a central warehouse - Stream appointment and check-in events to downstream analytics and reminder tools - Reconcile provider schedules across multi-location practices
Automate clinical documentation workflows
- Export clinical notes, problems, medications, and lab results for reporting and quality measures - Upload chart documents and intake forms back into the patient record - Surface new encounter data to care-coordination and population-health tools
Streamline billing and revenue cycle
- Push line items, procedures, and diagnoses into DrChrono for claims processing - Pull eligibility, claim status, and denials into RCM dashboards - Reconcile payments and patient balances against external billing systems
Power patient engagement and telehealth
- Sync OnPatient portal messages, digital forms, and intake responses - Trigger appointment reminders and telehealth links from external scheduling tools - Keep patient contact and consent data consistent across systems
Technical Specifications
Authentication
OAuth 2.0 authorization-code flow with 48-hour access tokens and managed refresh-token rotation
Connectivity
DrChrono REST API (v4) plus authenticated web surfaces where endpoints are not exposed
Response format
Normalized JSON across patients, appointments, clinical notes, documents, and line items
Rate limits
Adaptive throttling tuned to DrChrono's per-application limits to avoid carrier-side blocks
Session management
Automatic token refresh, credential rotation, and per-provider scope handling
Data freshness
Near real-time pulls for patients, appointments, and clinical notes with optional scheduled syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned controls, and audit logging
Webhooks
Event-style callbacks for appointment changes, check-ins, and clinical-note updates
Latency
Sub-second reads on cached entities; multi-second writes when posting appointments and line items
Throughput
Horizontally scaled workers that iterate paginated (250) and bulk (1000) endpoints for large exports
Reliability
Retry, backoff, and idempotency handling for appointment and billing writes
Adaptation
Continuous monitoring of DrChrono API versions and X-DRC-API-Version changes for configuration drift
Frequently asked questions
Yes. Supergood manages the full OAuth 2.0 authorization-code flow, 48-hour access tokens, and refresh-token rotation, and falls back to authenticated web surfaces for data not exposed through the REST API.
Supergood transparently iterates DrChrono's paginated listing endpoints (capped at 250 rows) and uses bulk endpoints (up to 1000 rows) where available, so you receive complete result sets without managing next pointers.
Yes. Tokens only see data the granting provider can access, so Supergood maps provider accounts and permission scopes to give you consistent access across multi-provider and multi-location practices.
Supergood pins the API version per integration and monitors X-DRC-API-Version behavior, adapting the adapter automatically as DrChrono ships new versions so your integration doesn't break.
Yes. The normalized API covers reads of patients, appointments, clinical notes, and documents, plus writes such as creating appointments, uploading chart documents, and posting billing line items.