# DrChrono integrations

> Call the DrChrono API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/drchrono-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

DrChrono is an electronic health record and practice management platform for medical practices. Tray.ai connects to DrChrono through the HTTP Connector, so your workflows can call the DrChrono API alongside the rest of your stack.

## Use cases

### Clinical

Read, create, update, and delete clinical in DrChrono from any Tray.ai workflow. The DrChrono API covers calls such as list allergies and create allergies.

- List allergies
- Create allergies
- Get allergies

### Practice management

Read, create, update, and delete practice management in DrChrono from any Tray.ai workflow. The DrChrono API covers calls such as list messages and create messages.

- List messages
- Create messages
- Get messages

### Billing

Read, create, update, and delete billing in DrChrono from any Tray.ai workflow. The DrChrono API covers calls such as list procedures and get procedures.

- List procedures
- Get procedures
- List transactions

### Administrative

Read administrative in DrChrono from any Tray.ai workflow. The DrChrono API covers calls such as list doctors and get doctors.

- List doctors
- Get doctors
- List users

## Challenges Tray.ai solves

### Keeping DrChrono credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store DrChrono credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the DrChrono API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the DrChrono API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to DrChrono?

Yes. Tray.ai connects to DrChrono through the HTTP Connector, which calls the DrChrono API directly. Any call the DrChrono API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with DrChrono?

The DrChrono API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated DrChrono connector?

DrChrono runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated DrChrono connector from the DrChrono API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/