Reads are free, writes need a contract, scheduling is elsewhere, and every practice goes live separately. What to plan for.
Originally published on Nirmitee.io: eClinicalWorks API and FHIR Guide (2026): Access, Limits, Writes, Scheduling
eClinicalWorks (eCW) is a cloud EHR for ambulatory practices, and many healthtech products need to connect to it. eCW does publish APIs. But what you can read, what you can write, and how you go live differ enough from other EHRs that it pays to plan before you build.
Here is the short version, based on eCW's own pages as checked by the source in September and October 2026. eCW updates its portal often, so re-check any detail you commit to.
Two developer programs, not one
eCW has two programs, and picking the wrong one wastes time:
- eClinicalWorks Connect if clinicians or practice staff use your app, or if your server reads practice data. This covers provider apps, backend and bulk data apps, and decision-support hooks.
- The healow Developer Portal if patients use your app, if you book appointments, or if you ship a remote monitoring device.
What is free, paid and missing
eCW's 90-entry API list, read 28 October 2026. Source: Nirmitee.io
eCW's API documentation lists 90 entries. On 28 October 2026, the source counted:
- 60 reads that are free and need no contract.
- 1 read flagged as paid (Encounter).
- 29 create, update and delete APIs that need a contract with eCW.
On cost, eCW says its certified FHIR APIs are available "at no cost at this time", and that it will give at least 30 days' notice of any future fees.
What the FHIR API does not give you matters just as much:
- Appointments and the daily schedule. There is no Appointment, Schedule or Slot resource for any app type. Booking runs on healow's older scheduling API under contract, and a provider's full daily schedule usually comes from an HL7 SIU feed.
- Claims and payments. Claim status and remittance come from your clearinghouse, not eCW's FHIR API.
- Insurance changes. Reading coverage is free; adding or changing it is contracted.
- Practice-specific fields. Custom visit types and fields often live in HL7 v2 messages rather than FHIR.
If your product depends on scheduling or writing data back, plan for a contract and a second integration route from day one. The original guide includes a decision flowchart for matching each workflow to the right route.
Going live is per practice
From sign-up to a live practice. Source: Nirmitee.io
Registering on eClinicalWorks Connect is self-service and takes five steps: sign up, register the app, test it, publish it, and connect each customer practice. The first four are yours. The fifth needs every practice's administrator, who enters your App Activation Code in eCW before you approve that practice on the portal.
So "live on eCW" is not one event. It happens one practice at a time, and your rollout plan needs each practice's admin in it.
Testing has gaps
eCW's sandbox supports apps launched from inside the EHR only. Standalone provider apps are tested with Postman, and eCW documents no public sandbox for backend or bulk apps, so most teams validate those flows with their first customer practice. Patient apps have their own healow sandbox with published test logins.
Budget for that first practice to double as your test site.
The rate limit is strict
Each practice gives your app a budget of 250 calls per minute. Exceed it and, in eCW's words, "all requests from that application will be blocked for the remainder of the minute." One busy practice can pause your whole integration for up to a minute.
The source suggests three habits: throttle per practice on your side, counting token requests as well as data calls; reuse tokens until shortly before they expire; and use bulk export for backfills.
Other details worth knowing early
- Every practice has its own base URL, so discover endpoints rather than hard-coding them.
- healow patient tokens lasted about five minutes in the source's test, with no refresh token for public apps, so patients may need to sign in again.
- There is no page called "eCW Marketplace". People usually mean eCW's App Gallery.
The full guide covers authentication, sandbox details and the complete API list, with primary sources for each fact.
Nirmitee.io builds eClinicalWorks integrations across FHIR, healow and HL7, including contracted write-back and scheduling. For every limit and step with its eCW source, read the original: eClinicalWorks API and FHIR Guide on Nirmitee.io.
Dinesh Thorat is Healthtech Growth Partner at Nirmitee.io.
Originally published at nirmitee.io.


Top comments (0)