SimplePractice API and Integration: What Is Possible in 2026, and How to Connect
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.
Updated November 2026
Short answer. SimplePractice does not publish a public, self-serve API. You can still connect to it in a few narrow ways: its partner program for health plans and employee assistance programs, calendar sync, reports and exports, its built-in e-prescribing, a formal partnership, and login-based automation. This guide explains what each route does, how to choose, how to go live and the mistakes to avoid. Every fact here comes from SimplePractice's own pages, the federal certified health IT list or SimplePractice's published terms.
Key takeaways
- We found no public SimplePractice API, developer portal or sandbox.
- SimplePractice is not on CHPL, the federal list of certified health IT, so there is no certified FHIR API to use.
- The official partner program connects health plans and EAPs to SimplePractice clinicians for booking.
- Calendar sync and exports are official and safe, but limited.
- SimplePractice's terms restrict bots and scripts. Get written permission and legal advice before any automation.
What is SimplePractice?
SimplePractice is a cloud practice management system and EHR for therapists, counselors and other private practice clinicians. It covers scheduling, client records, notes, telehealth, a client portal and billing, with e-prescribing as an add-on.
Does SimplePractice have an API?
Not a public one. We found no public API, developer portal, sandbox or API documentation from SimplePractice. Independent reviewers report the same.
There is one official API, and it is for partners. In 2022 SimplePractice announced an enterprise API for employee assistance programs (EAPs) and managed care organizations, to expand access to covered behavioral health care. This work now runs under SimpleConnect. In March 2026 SimplePractice announced a SimpleConnect partnership with Uprise Health, an EAP, so Uprise members can book with clinicians who use SimplePractice. It is not a general developer API.
We found no SimplePractice document that describes webhooks (automatic event messages to your system). Do not design around them unless SimplePractice confirms them to you in writing.
Is there a FHIR API?
No certified one. EHRs certified under the federal ONC program must offer a standard FHIR API for patient and population data. On November 3, 2026 we searched CHPL, the federal Certified Health IT Product List. It lists no product under SimplePractice, and no developer named SimplePractice or EngageSmart, the company that announced the 2022 API.
What is possible, and what is not
| Possible | Not possible through any official route we found |
|---|---|
| Health plan and EAP members booking with SimplePractice clinicians through SimpleConnect | A public API, developer portal or sandbox |
| SimplePractice appointments shown in Google, Outlook or Apple calendars | A certified FHIR API |
| Two-way calendar sync with Google | Reading clinical notes from your own software |
| Client, appointment and billing data in reports and exports | Writing to the client chart from your own software |
| E-prescribing inside SimplePractice, through DrFirst | A real-time feed of billing or clinical data |
The six ways to integrate with SimplePractice
1. SimpleConnect partner program
What it is: SimplePractice's official connection for health plans and EAPs, so their members can book with SimplePractice clinicians.
Pros: Official and supported, and already live with partners such as Uprise Health.
Cons: It is a partner program, not open access. SimplePractice decides who joins and what the connection covers.
Choose it if you are a health plan, EAP or employer program and want members to book with SimplePractice clinicians. Contact SimplePractice about SimpleConnect.
2. Calendar sync as an appointment feed
What it is: SimplePractice's own calendar sync. Basic sync shows SimplePractice appointments in Google, Outlook or Apple calendars, and Apple sync is one way. Advanced sync works with Google only. It shows personal Google events in SimplePractice, and the clinician can create and change SimplePractice events from Google. With the clinician's permission, your product reads that Google Calendar through Google's Calendar API.
Pros: Official, close to real time, and no build on the SimplePractice side.
Cons: Each clinician sets it up and grants access. You get appointments, not records. Appointments sync from 30 days before the sync date onward, and out-of-office blocks do not sync. Appointment details are health information, so use a Google account covered by a business associate agreement (BAA). Google signs BAAs for Google Workspace, not for personal Gmail accounts.
Choose it if your product needs a clinician's schedule, for example for reminders or availability.
3. Reports and exports
What it is: The reports and exports inside SimplePractice. Its help center describes these:
| Export | What it covers | Format |
|---|---|---|
| Data export (Settings, Practice, Data export) | Client information. It does not include appointments, and client contact details do not come out as CSV | Download |
| Client details report | Client contact details, including email | CSV or Excel |
| Appointment status report | Appointments | Report download |
| Payments, from the Billing page | Payments | CSV or QuickBooks |
| Analytics billing reports | Billing reports | CSV or Excel |
Pros: Official, and the widest view of the data without automation.
Cons: A person downloads them, so the data is not real time. The data is spread over several reports.
Choose it if you need analytics, billing reconciliation, a migration, or a regular report.
4. Built-in e-prescribing
What it is: ePrescribe is a SimplePractice add-on. Its help center names DrFirst as the e-prescribing partner. Prescribers of controlled substances receive a hard token for two-factor signing.
Pros: Nothing to build.
Cons: It works inside SimplePractice. Your own product cannot plug into it.
Choose it if the practice needs prescribing and nothing more.
5. A formal partnership with SimplePractice
What it is: A commercial agreement with SimplePractice, the way its e-prescribing and SimpleConnect partners work.
Pros: Supported and lasting. It is the only safe route to deeper data that we know of.
Cons: SimplePractice decides, and it takes time.
Choose it if you are a vendor with many shared customers and a long-term plan.
6. Login-based automation
What it is: Software that works through a user's SimplePractice login. It either drives the screens the way a person does, or it repeats the calls the web app makes. Some vendors sell this as an "unofficial API". Our guide to EHR automation without an API explains how these tools work.
Pros: It reaches almost any screen, for reading and writing.
Cons: SimplePractice's Terms of Service, December 2020 version, bar reverse engineering. They also bar launching automated programs or scripts, including bots. Read the current terms before you start. Automation breaks when screens change. It must handle multi-factor sign-in. And it puts a practice login in a third party's hands.
Choose it only when no official route meets the need. The practice must give written permission, and your counsel must review the current terms. Keep it away from core clinical workflows.
Pros and cons at a glance
| Route | Official | Real time | Data you get | Main risk |
|---|---|---|---|---|
| SimpleConnect | Yes | Yes | Member booking with clinicians | Partner program, not open access |
| Calendar sync | Yes | Close to real time | Appointments | Health information in Google without a BAA |
| Reports and exports | Yes | No | Clients, appointments, billing | Manual work |
| Built-in e-prescribing | Yes | Yes | Prescribing inside SimplePractice | No access for your product |
| Partnership | Yes | Depends on the deal | Depends on the deal | Slow, and not in your control |
| Login-based automation | No | Close to real time | Almost anything on screen | Terms breach, breakage, security |
Which route fits your use case?
These are our recommendations.
| You are building | Start with | Avoid |
|---|---|---|
| A health plan or EAP booking flow | SimpleConnect | Automating clinician calendars |
| Reminders or availability tools | Google Calendar sync under a BAA | Personal Gmail accounts |
| Practice analytics or billing reconciliation | Reports and exports | Promising live numbers |
| A migration off SimplePractice | Every report you need, checked record by record | Relying on one export |
| An AI scribe or notes tool | A workflow where the clinician reviews the note and adds it to SimplePractice, or a partnership | Writing into charts by automation without permission |
How to go live
- Write down the data and the direction. List what you need, how fresh it must be, and whether you read or write. This picks the route.
- Ask SimplePractice first. Ask in writing about SimpleConnect, a partnership and webhooks. Keep the answer.
- Sign BAAs with every party that touches client data, including Google Workspace for calendar sync and any automation vendor.
- Get the practice's written consent. Say what data you access, how, and how they turn it off.
- Pilot with one practice and one clinician. Compare your data with SimplePractice's own screens every day.
- Monitor every run. Alert when a sync stops, an export changes, or an automation step fails.
- Roll out practice by practice, with an offboarding step that removes access and data.
Mistakes to avoid
| Mistake | What goes wrong | How to avoid it |
|---|---|---|
| Believing an API or webhook exists because a vendor says so | You design around something you cannot get | Get SimplePractice's answer in writing |
| Syncing appointments to a personal Google account | Health information sits outside a BAA | Use Google Workspace under a BAA |
| Automating without permission | Terms breach and a damaged practice relationship | Written consent and legal review first |
| One shared login for automation | No audit trail, and one breach exposes every practice | One login per practice, with access logged |
| Matching clients across systems by name | The wrong person's record | Match on several identifiers and keep a review queue |
| Treating exports as live data | Decisions on old numbers | Show the export date on every report |
Security and compliance
- BAAs with everyone who handles client data.
- Minimum necessary: take only the fields your use case needs.
- 42 CFR Part 2: records of substance use disorder treatment programs carry extra consent rules. Check before you move them.
- Audit: log every access and change your product makes.
- Offboarding: delete data and revoke access when a practice leaves.
How Nirmitee helps
We integrate behavioral health EHRs, including EHRs without a public API. We pick the safest route for your use case first. See our behavioral health EHR integration services, or tell us what you need from SimplePractice.
Sources
- SimplePractice help center: Exporting client information through data exports, Getting started with calendar sync, ePrescribe, Annual financial activity report FAQs, Understanding your billing reports
- SimplePractice, Enterprise launches API, and EngageSmart investor news, 2022
- SimplePractice and Uprise Health, SimpleConnect partnership, March 2026
- ONC, Certified Health IT Product List, searched November 3, 2026
- SimplePractice Terms of Service, December 2020 version, third-party copy. Read the current terms on SimplePractice's site
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does SimplePractice have an API?
Does SimplePractice support webhooks?
Does SimplePractice have a FHIR API?
How do I get data out of SimplePractice?
Can I sync SimplePractice with Google Calendar?
Can I automate SimplePractice with a bot?
