Kipu Health API
Roughly 41 APIs exist, but keys are issued only to Kipu clients or developers working with one. There is no self-serve developer portal and no public SDKs; access starts with a request process tied to the client relationship.
Frequently asked questions
Kipu Health scores F on Supergood's API Report Card. Roughly 41 APIs exist, but keys are issued only to Kipu clients or developers working with one. There is no self-serve developer portal and no public SDKs; access starts with a request process tied to the client relationship.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Kipu Health is a cloud-based EMR/EHR purpose-built for behavioral health, substance-use-disorder (SUD), and addiction-treatment providers. It covers clinical documentation, patient management, e-MAR/medication administration, treatment planning, CRM, and revenue-cycle/billing ("billing sweeps").
Healthcare / Behavioral Health EHR, Typically for addiction-treatment centers, SUD residential programs, mental-health clinics, and specialty behavioral-health providers. Clinicians document progress notes, run treatment plans and medication administration, manage admissions/census, and bill payers through Kipu's RCM tooling. It is the operational backbone of a treatment center.
Widely regarded as a leading EMR for SUD/behavioral treatment centers; strong Capterra footprint and recognized brand in the niche. "Nearly one million messages" exchanged via its interfaces, per vendor materials.
Yes, patient clinical records, treatment plans, medication administration, census/admissions, and billing/RCM data. This is the treatment center's system-of-record.
~13 years old, founded ~2012. Cloud-based and actively developed, but users report performance lag and workflow gaps.
Integration limitations / lack of automatic data sync between modules. Access gated behind client/partner relationship and API-key request process. Full sourced list under Sources below.
Common alternatives include BestNotes, Sunwave Health, Lightning Step, Ritten, AZZLY. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Kipu Health has partial MCP support. Kipu offers no official MCP server, but a community project on npm and GitHub wraps the Kipu EMR API with over 100 tools and documented setup. It is a single-author effort with minimal adoption and no visible activity since late 2025.
Partially. MCP support for Kipu Health exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.