Patients
Core record, care network, files, contacts, families, referral sources, billing state, and search.
The API exposes clinical, operational, communications, billing, AI, export, and realtime primitives so teams can build reliable tools around the EMR instead of scraping the UI.
curl https://api.bebraver.com/v1/patients?pageSize=25 \
-H "Authorization: Bearer $BRAVER_TOKEN"
{
"count": 125,
"data": [
{
"id": "pat_01J...",
"firstName": "Avery",
"status": "active",
"nextAppointmentAt": "2026-07-09T18:30:00Z"
}
],
"page": 1,
"pageSize": 25
}Resource coverage
Start with patients and scheduling, then layer in clinical work, communications, operations, exports, AI processing, and realtime event handling as your integration gets deeper.
Core record, care network, files, contacts, families, referral sources, billing state, and search.
Appointments, appointment types, slots, unavailable blocks, reminders, attendance, history, and operations metrics.
Treatment notes, approved notes, templates, rulesets, diagnosis codes, forms, measures, and assessment review.
Conversations, managed phone numbers, message templates, patient emails, voice, recordings, and voicemails.
Tasks, queues, teams, automations, outreach events, exports, organization features, and staff scheduling.
AI prompt templates, processing jobs, context files, text extraction, local events, and websocket updates.
Integration rules
Braver keeps API shapes boring on purpose: explicit resources, scoped actions, paginated lists, and event streams that AI agents and internal tools can safely consume.
Bearer-token authentication for server-to-server integrations.
OpenAPI 3.1 contracts for SDK generation and review.
Paginated list responses with explicit count, page, and pageSize fields.
Event and websocket surfaces for automation and AI workflow sync.