Cerbo API Integration Guide (2026)
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Cerbo is an EHR for functional, integrative and direct primary care practices. The Cerbo API is public. Cerbo publishes a REST API reference at docs.cer.bo, and its OpenAPI file lists 128 operations across patients, appointments, encounters, prescriptions, labs, billing and more.
This guide is for a product lead or buyer who has to connect a product to Cerbo EHR, and for the engineer who will build it. It covers how a clinic issues credentials and every documented group of endpoints. It also covers what the API can do with prescriptions, the limits Cerbo states, and what Cerbo leaves unpublished. If you want a team to build it, see our Cerbo integration service. Last checked: Nov 18, 2026.
Cerbo API at a glance
| Question | Short answer |
|---|---|
| Who grants access? | The clinic. A Superadmin creates an API user in Admin, Manage, Integrations, API User Management. |
| Who signs? | The clinic's Superadmin is responsible for the third party's compliance with Cerbo policies and HIPAA. Cerbo's MSA makes Providi the clinic's business associate. |
| Are there public documents? | Yes. A REST reference with an embedded OpenAPI file at docs.cer.bo. |
| Which routes exist? | REST API, webhooks, a delta endpoint, built-in HL7 ADT and DFT messages, and Cerbo's own partner integrations. |
| What does it cost? | Cerbo publishes per-provider prices but no API fee. |
| How long does it take? | Credential creation is self-serve for the clinic. Cerbo publishes no time for a sandbox request. |
| What is the biggest limit? | The API cannot sign or send a prescription. New prescriptions go to a review queue. |
What can you build with the Cerbo API?
Each use case points to a row in the read and write table in section 6 (rows R1 to R13). Cerbo publishes no build times, so this guide gives no build estimate. Build complexity is our own rating.
1. Book Cerbo appointments from your own website or app
- Who it is for: booking widgets, patient apps and practice websites.
- The value: patients book in your interface and the visit lands on the Cerbo calendar with a reminder.
- Build complexity: medium.
- How well it works: well.
GET /appointments/availabilityreturns open times,POST /appointmentsbooks, and the reminder endpoints add an email or SMS reminder. See row R2.
2. Send intake forms and questionnaires into the chart
- Who it is for: intake tools, functional medicine assessment tools and patient apps.
- The value: answers reach the chart instead of sitting in email.
- Build complexity: low to medium.
- How well it works: well.
POST /patients/{patient_id}/questionnairesposts a questionnaire, and documents can be added through the portal queue. See rows R7 and R8.
3. Let patients ask for a refill from your app
- Who it is for: patient apps, membership and direct primary care platforms.
- The value: a refill request reaches the clinic's review queue without a phone call.
- Build complexity: low.
- How well it works: partly.
POST /patients/{patient_id}/rxs/refillqueues the request. The prescriber still reviews and sends it inside Cerbo. See row R4.
4. Show a patient's medication list in another product
- Who it is for: care management tools, pharmacies working with the clinic, and patient apps.
- The value: the patient and care team see current medicines and supplements in one place.
- Build complexity: low.
- How well it works: well.
GET /patients/{patient_id}/rxsand the supplements endpoints return the list, and the delta endpoint tracks changes. See row R4.
5. Push device and home readings into vitals
- Who it is for: remote monitoring and connected device companies.
- The value: weight, blood pressure and custom readings arrive in the chart for the provider to review.
- Build complexity: low to medium.
- How well it works: well. Cerbo has POST endpoints for height, weight, blood pressure and custom vitals. See row R6.
6. Send signed visits to a billing platform
- Who it is for: billing companies and claims platforms.
- The value: each signed encounter becomes a claim without retyping.
- Build complexity: medium.
- How well it works: well. Cerbo's help center shows a DFT claim built from four GET calls after a
soap.modifiedwebhook. Cerbo also has built-in HL7 ADT and DFT options. See rows R3 and R9.
7. Sync patients and visits into a CRM or reporting tool
- Who it is for: CRM, analytics and practice growth tools.
- The value: marketing and reporting work from current patient and visit data.
- Build complexity: medium.
- How well it works: well. Read patients and appointments once, then use
GET /delta/{resource_type}for what changed, a week at a time. See rows R1, R2 and R13.
8. Build research data sets with patient identifiers removed
- Who it is for: research groups and outcome analytics companies.
- The value: outcome data without names or street addresses.
- Build complexity: medium.
- How well it works: partly. The extended details endpoint has an
anonymizeflag, but Cerbo warns the data can still identify a patient, and custom questionnaire answers are not scrubbed. See row R1.
The eight Cerbo use cases compared
| Use case | Who it is for | Complexity |
|---|---|---|
| 1. Book appointments from your site | Booking widgets, patient apps | Medium |
| 2. Send intake forms into the chart | Intake and assessment tools | Low to medium |
| 3. Refill requests from your app | Patient apps, DPC platforms | Low |
| 4. Show the medication list | Care management, patient apps | Low |
| 5. Push device readings into vitals | Remote monitoring | Low to medium |
| 6. Send signed visits to billing | Billing and claims platforms | Medium |
| 7. Sync to a CRM or reporting tool | CRM and analytics | Medium |
| 8. Research data sets | Research and analytics | Medium |
How do you get access to the Cerbo API?
The clinic grants access. A Superadmin in the clinic's Cerbo account creates an API user, picks a permission profile and generates a secret key.
API users
In Admin, Manage, Integrations, the Superadmin opens API User Management and adds a user. The form asks for a nickname, a username that starts with pk_, a permission profile and a contact email. It also asks for a short description of the use, including any third-party APIs involved. The secret key is shown once, so copy it before you save. API credentials are separate from staff logins and cannot sign in to the app.
What the clinic signs up to
Cerbo states the Superadmin is responsible for the third party complying with Cerbo policies and HIPAA, and for any breach by the third party. API use falls under Cerbo's MSA and EULA. Expect the clinic to ask you for a business associate agreement before it creates the user.
If you sell to many clinics
Cerbo publishes no partner program or vendor sign-up. Each clinic creates its own API user, and each clinic has its own base URL. Plan to store one set of credentials and one subdomain per clinic.
Sandbox
Cerbo asks integrators to request a sandbox before production, and some code samples use sandbox.md-hq.com. Cerbo does not publish how to request one or who approves it.
What does Cerbo API access give you?
Access opens the endpoints the API user's permission profile allows, on the clinic's own subdomain.
| Stage | What you get |
|---|---|
| Sandbox (on request) | A test environment, host shown in samples as sandbox.md-hq.com. |
| Clinic API user | Basic auth credentials on https://{tenant}.md-hq.com/api/v1, limited by permission profile. |
| Optional IP lock | On request, the connection only accepts calls from your static IP. |
| Webhooks | Event notices to your HTTPS endpoint, set up by a Superadmin. |
What are the ways to integrate with Cerbo?
Cerbo documents five routes, and most products use the REST API with webhooks or deltas.
| Route | What it does | When it fits |
|---|---|---|
| REST API | 128 operations on clinic data. | Most product integrations. |
| Webhooks | Real-time event notices, no retries. | You need to react fast, for example to a signed note. |
| Delta endpoint | Created, modified and removed records for 13 resource types, up to a week per call. | Scheduled sync where speed is less important. |
| HL7 ADT and DFT | Built-in messages to third parties, mostly billing. | Billing platforms that already take HL7. |
| Cerbo partner integrations | 55+ integrations, including labs, Fullscript, Keragon and Hint. | The partner you need is already on Cerbo's list. |
No FHIR interface is documented in the API.
What can you read and write with the Cerbo API?
Each row gives example methods and paths from the OpenAPI file, relative to https://{tenant}.md-hq.com/api/v1.
| Row | Group | Read | Write |
|---|---|---|---|
| R1 | Patients | GET /patients, GET /patients/search, GET /patients/{patient_id} | POST /patients, PATCH /patients/{patient_id}, DELETE /patients/{patient_id} (archives) |
| R2 | Appointments | GET /appointments, GET /appointments/availability | POST /appointments, PATCH and DELETE /appointments/{appointment_id}, email and SMS reminders |
| R3 | Encounters | GET /patients/{patient_id}/encounters, GET /encounters/{encounter_id} | POST /encounters, DELETE /encounters/{encounter_id} |
| R4 | Prescriptions and supplements | GET /patients/{patient_id}/rxs, GET /drugs/search/{term} | Queue only: POST /patients/{patient_id}/rxs, POST .../rxs/refill. Discontinue: PATCH .../rxs/{pt_rx_id}/discontinue |
| R5 | Allergies, history, vaccines, labs, orders | GET .../allergies, /pmh, /vaccines, /lab_results, /orders | None |
| R6 | Vitals and health maintenance | GET .../vitals/bp, /weight, /height, /{vital_id} | POST on the same paths |
| R7 | Documents and images | GET .../documents, GET /documents/{document_id}/content | POST .../documents via the portal queue |
| R8 | Questionnaires | GET /patients/{patient_id}/questionnaires | POST /patients/{patient_id}/questionnaires |
| R9 | Charges, invoices, subscriptions | GET /charges, GET /charge_master, GET .../invoices | None |
| R10 | Messages and portal | GET .../portal/secure_messages | POST .../portal/secure_messages, POST .../emails/send, POST .../portal/invite |
| R11 | Tasks, tags, users, inventory | GET /tasks, GET /users, GET /inventory | POST and PATCH /tasks, tags, inventory |
| R12 | Quest orders | GET /patients/{patient_id}/partners/quest/orders | None |
| R13 | Deltas | GET /delta/{resource_type} | None |
What can the Cerbo API do with prescriptions?
The Cerbo API can read prescriptions, queue a new one or a refill for clinic review, and mark one discontinued. It cannot create a signed prescription, edit one, delete one, or send one to a pharmacy.
The path is /patients/{patient_id}/rxs, and the prescription group has five operations.
| Method and path | What it does |
|---|---|
GET /patients/{patient_id}/rxs | Lists the patient's prescriptions. Dates are UTC. |
GET /patients/{patient_id}/rxs/{medication_prescribed_id} | Returns one prescription. |
POST /patients/{patient_id}/rxs | Cerbo's summary reads "Post a new patient prescription via the portal queue". |
POST /patients/{patient_id}/rxs/refill | Queues a refill request for an existing prescription. |
PATCH /patients/{pt_id}/rxs/{pt_rx_id}/discontinue | Marks it discontinued. The record stays in history. |
The enqueue flag on the POST is true by default. Cerbo's docs say the drug goes into "the active patient portal queue so that the clinic is notified and can review the proposed addition." Cerbo does not document what enqueue=false does.
Sending to a pharmacy happens inside Cerbo, over the Surescripts network, after each prescriber completes ID proofing and eRx registration. GET /patients/{patient_id}/pharmacies returns the patient's pharmacies with their NCPDP id. Adding or removing a pharmacy through the API returns 501.
What happens inside Cerbo, outside the API
Prescription signing and sending, EPCS two-factor sign-off, webhook set-up and API user creation all happen in the Cerbo app.
What is not possible with the Cerbo API?
Prescribing, clinical writes and billing writes stay inside Cerbo, and FHIR is not offered.
| Not in the Cerbo API | What to do instead |
|---|---|
| Sign or send a prescription to a pharmacy | Queue it with POST .../rxs. The prescriber sends it in Cerbo over Surescripts. |
| Edit or delete a prescription | Discontinue it with a reason. |
| Add or remove a patient pharmacy | Returns 501. The clinic sets it in Cerbo. |
| Write allergies, history, lab results or orders | Read only. Send data as a document or questionnaire for review. |
| Write charges or invoices | Read only. Use Cerbo's built-in billing or HL7 routes. |
| FHIR | Not documented. Map from the REST JSON. |
| Webhook retries | None. Run a delta catch-up after any outage. |
| A vendor-wide key | Each clinic creates its own API user. |
What are the Cerbo API limits?
Cerbo states that rate limits differ by endpoint and publishes no numbers. It says single-threaded requests almost never trigger a lock, except on credential validation and email endpoints.
| What | Limit Cerbo states |
|---|---|
| Rate limit | Per endpoint, not published. Some responses document an X-Rate-Limit header, "calls per hour allowed by the user". |
| Threads | Avoid multi-threaded requests. |
| Bulk transfers | Off-peak, after 5 PM Pacific and before 8 AM Eastern. |
| Page size | Default 100, max 100, with offset and has_more. |
| Delta window | Up to one week per call. |
| Webhooks | No retries. HTTPS with a valid certificate. |
How much does Cerbo integration cost?
Cerbo publishes its EHR prices but no API fee. The Prescribing Provider plan is listed at $281 a month full-time and $174 part-time, with eRx, eFax and EPCS included. The pricing page lists no API fee, and no fee is published for a sandbox or for vendors.
Ask Cerbo whether API access is included in every plan, and whether a sandbox has a fee.
How long does a Cerbo integration take?
Cerbo publishes no timeline for an integration. The clinic can create an API user straight away in its admin screen. Cerbo publishes no wait time for a sandbox or an IP lock request. For e-prescribing inside Cerbo, ID proofing takes about 5 minutes and EPCS token set-up about 15. A hardware token ships in 5 to 7 business days.
How do you build a Cerbo API integration, step by step?
The build runs in four stages: credentials, reference data, writes, and change tracking.
Stage 1. Get the clinic's credentials
Ask the clinic's Superadmin for an API user with the narrowest permission profile that works. If your server has a static IP, ask for an IP lock too. Send the credentials as Basic auth from your server only.
Stage 2. Load reference data
Read appointment types, encounter types, users and facilities, and use GET /drugs/search/{term} for drug ids before any prescription call.
Stage 3. Write the record
For a prescription request, search the drug, then queue it. This request is Cerbo's own sample from the docs, with credentials replaced by CREDS.
curl -H "Authorization: Basic CREDS" \
--data '{"drug_id": "214322","notes":"Takes in the AM with food and water"}' \
-X POST https://subdomain.md-hq.com/api/v1/patients/1/rxs?enqueue=true
Cerbo documents a bare 200 for this call, with no response body. To stop a medication, Cerbo's sample is:
curl -H "Authorization: Basic CREDS" \
--data '{"discontinued_reason":"Patient experiencing adverse side effects","discontinued_date":"2024-01-15T14:30:00Z"}' \
-X PATCH https://subdomain.md-hq.com/api/v1/patients/123/rxs/456/discontinue
The documented 200 response has these fields. The values shown are Cerbo's own examples and ids from the sample path.
{
"object": "medication_prescribed",
"id": 456,
"drug_id": 214322,
"drug_name": "...",
"status": "Discontinued",
"discontinued_date": "2024-01-15T14:30:00Z",
"discontinued_reason": "Patient experiencing adverse side effects"
}
Stage 4. Track changes
Register a webhook for the events you need, and fetch the full object on each notice, because webhook payloads are thin. Because webhooks are not retried, run GET /delta/{resource_type} on a schedule to catch anything missed.
Which Cerbo API quirks should you know?
These come from Cerbo's own pages. Check each one for your account with Cerbo.
Two hosts, one product
Docs live at docs.cer.bo, but every API call goes to the clinic's subdomain on md-hq.com.
Auth schemes disagree
The prose says Basic auth, but the OpenAPI file also declares OAuth2 with a placeholder example.com URL and an api_key header. Use Basic.
No PUT
All updates are PATCH, and Cerbo asks you to avoid PATCH calls that change nothing.
Most responses have no schema
Most operations document a bare 200 "Successful response".
Path names change
Some paths use patient_id, others pt_id, for the same patient id.
Queue writes look like patient actions
New prescriptions, documents, images, supplements and secure messages go through the patient portal queue.
Queued requests can be deleted
DELETE /patients/{pt_id}/portal/enqueued/{queue_request_id} removes one.
Webhooks are unsigned
Add your own authorization header and an IP allowlist.
Webhook help is marked deprecated
The older help article is titled "DEPRECATED--Cerbo Webhooks", and the API docs list no event names.
Anonymize is not de-identification
Cerbo warns anonymized data can still identify a patient.
One refill location
A prescriber can receive Surescripts refill requests in only one system at a time.
Cerbo and OptiMantra share a parent
The MSA names CerboOM, LLC, using the brand Providi, as the parent of Cerbo and OptiMantra. It lists a "CerboOM API" among its Services, but does not say how that API relates to docs.cer.bo.
What should you check before you sign with Cerbo?
Check the BAA chain, the permission profile and the sandbox before the first call.
Security and compliance, as Cerbo states them
- Under the MSA, Providi is the clinic's business associate under HIPAA.
- The clinic's Superadmin carries responsibility for the third party.
- Webhooks and API responses carry PHI.
Rules for your side
Keep credentials on the server, never in a browser or mobile app. Use one API user per clinic and use, with the narrowest profile. Do not put credentials in support tickets. When the integration stops, disable the API user.
Testing
Request a sandbox before production. Agree on test patients with the clinic before any write in production, because writes such as a prescription queue item notify clinic staff.
Questions to ask Cerbo before you sign
- How do we request a sandbox, and is there a fee?
- Is API access included in every plan?
- What are the rate limits for the endpoints we will use?
- What does
enqueue=falsedo onPOST /rxs? - Is there a partner program for vendors serving many clinics?
- Which webhook events exist today, and where are they listed?
- What is the "CerboOM API" in the MSA, and is it the docs.cer.bo API?
- Will response schemas be added to the OpenAPI file?
What is the next step for a Cerbo integration?
Planning a Cerbo integration? We scope the endpoints, the credential set-up and the build with you. Start at our Cerbo integration service or our EHR integration services.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Cerbo have an API?
How do I get Cerbo API credentials?
Can the Cerbo API send a prescription to a pharmacy?
Can I update or delete a prescription through the Cerbo API?
Does Cerbo have a sandbox?
What is the Cerbo API rate limit?
Does Cerbo support webhooks?
Does Cerbo support FHIR or HL7?
Is there a Cerbo partner program for software vendors?
How are Cerbo and OptiMantra related?


