Kipu API

Overview

Kipu is one of the most widely deployed EHR platforms in the residential addiction treatment market. Its customer base includes residential treatment centers, partial hospitalization programs, and intensive outpatient programs across the United States, and its feature set covers the complete workflow of addiction treatment: admission and intake documentation, individualized treatment planning, group and individual therapy session notes, medication administration records, and discharge planning. For AI clinical documentation tools and outcome tracking platforms that serve residential treatment centers, Kipu is a required integration across a significant portion of their target customer base.

No public API exists. Kipu is a closed web application, and the only mechanism for extracting structured data from the platform is manual CSV export by clinical staff. There is no developer portal, no webhook surface, and no published roadmap for a programmatic integration capability. The CSV export workflow that clinical staff rely on today produces files with inconsistent column structures across Kipu versions and facility configurations, requires staff time to generate, and creates data that is stale by the time it reaches any downstream tool that could act on it.

Addiction treatment records in the residential setting occupy the most sensitive position in the behavioral health compliance landscape. Kipu's clients include programs that provide medically supervised detoxification and intensive residential treatment, where clinical documentation includes detox protocols, medication orders, and crisis assessments alongside standard therapy notes. These records are protected under HIPAA, and those relating to substance use disorder treatment may fall under 42 CFR Part 2, which restricts disclosure more tightly than standard HIPAA rules. The compliance sensitivity that characterizes the residential treatment market is part of why Kipu's developer program has not materialized; it is also context that any tool working with Kipu data needs to take seriously. Integuru generates a production-ready HTTP API for Kipu using direct HTTP requests against the endpoints the Kipu web application uses internally. Integuru can be deployed in HIPAA-compliant environments; discuss your compliance requirements when you chat with us.

---

Why Teams Need This Integration

The residential addiction treatment market has one of the highest documentation burdens in behavioral health, and Kipu is the platform that a large share of those programs run on. The CSV-only data access model is not a temporary state; it is the constraint that every AI tool and analytics platform in this space has been working around for years.

AI clinical documentation and ambient scribing tools. Residential treatment documentation is intensive: admission assessments, daily progress notes, group therapy records, treatment plan reviews, and discharge summaries all carry payer-specific documentation requirements and accreditation standards. AI tools that help clinical staff draft and complete this documentation need get_clinical_notes to read existing note structures and treatment plan content, and create_treatment_note to push completed documentation back to the Kipu record. The CSV export workflow cannot support either direction. Without write-back capability, AI documentation tools produce output that clinical staff must manually copy into Kipu, which eliminates most of the time savings the product is built to deliver.

Outcome tracking and program performance platforms. Residential treatment programs are under increasing pressure from payers, state licensing bodies, and accrediting organizations to track and report treatment outcomes: substance use status at discharge and follow-up intervals, housing stability, employment engagement, and readmission rates. Platforms that automate this tracking need programmatic access to admission, clinical, and discharge data across a program's full client population. The manual CSV export process that Kipu requires creates data that is delayed, inconsistent across facilities, and staff-intensive to produce at the scale these tracking tools require.

Billing automation for residential treatment codes. Residential addiction treatment billing involves per-diem billing structures, prior authorization requirements that are specific to residential levels of care, and documentation standards that vary by payer and must be met before claims are processed. Billing automation platforms that serve this market need list_claims and get_claim_status to identify authorization issues, flag documentation gaps, and trigger resubmission workflows before claim deadlines pass. The CSV export workflow produces claim data that is days old by the time it reaches the billing tool, which is too slow for the denial management timelines that residential treatment billing requires.

Admissions and intake coordination tools. Residential treatment programs receive referrals from detox programs, hospitals, and outpatient providers and need to manage the admissions process with a level of speed and documentation rigor that manual data entry cannot sustain at scale. Admissions coordination tools that automate intake documentation and client record creation need create_client and list_appointments as live API calls. get_client_detail feeds these tools with the current client status and insurance verification data they need to confirm admissions without requiring staff to pull records manually from Kipu.

---

Behavioral Health Workflows This Integration Covers

The ten planned actions cover the clinical, administrative, and billing workflows that residential treatment programs running on Kipu require for programmatic integration:

• Client management: list_clients and get_client_detail surface the program's client roster with demographics, insurance data, and admission status. create_client supports admissions automation and referral intake workflows that need to write new client records into Kipu without manual data entry.
• Appointment and group session scheduling: list_appointments and create_appointment feed scheduling and care coordination tools with live individual and group session data. update_appointment_status tracks session completions and cancellations for attendance documentation and billing.
• Clinical documentation: get_clinical_notes retrieves progress note content, treatment plan data, discharge summaries, and provider signature status. create_treatment_note pushes completed documentation back to the client record, giving AI scribing and documentation tools the write access that the CSV export model cannot provide.
• Billing and claims: list_claims returns structured billing data with residential treatment procedure codes, payer information, and claim status. get_claim_status retrieves adjudication details for denial management workflows, replacing the delayed data that CSV exports deliver.

---

Adjacent Integrations

Integuru already covers the healthcare and EHR vertical in production across ambulatory platforms using the same direct HTTP authentication patterns that apply to Kipu. The DrChrono integration provides 4 live actions including patient creation and medication records. The eClinicalWorks integration covers 5 live actions across patient demographics, insurance data, and document management. The Modmed integration covers 21 live actions spanning claims, payments, insurance policies, and full patient management. Residential addiction treatment EHRs like Kipu share the same web-application authentication and session management patterns as ambulatory platforms; Integuru handles both with the same direct HTTP approach.