Exym API
No public API. Exym's integration surface is vendor built EDI claims interfaces to state and county systems like IBHIS and Sage, plus e-prescribing and telehealth hookups wired up by the vendor. There is no developer portal, SDK, or webhook surface.
Frequently asked questions
Exym scores D on the API Report Card. No public API. Exym's integration surface is vendor built EDI claims interfaces to state and county systems like IBHIS and Sage, plus e-prescribing and telehealth hookups wired up by the vendor. There is no developer portal, SDK, or webhook surface.
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.
Exym is a 20+ year-old EHR for behavioral health agencies, dominant among Los Angeles County DMH/SAPC contracted providers, first EHR to integrate with LA DMH's IBHIS and interfaces with LA County's Sage system. Part of the KCare/Radicle Health (Alpine SG) family.
Healthcare / Behavioral Health, community behavioral health and SUD agencies billing county/Medi-Cal (CalAIM), especially LA County nonprofits (Didi Hirsch, Counseling4Kids, Amanecer).
"Thousands of clinicians" across 20+ years serving LA County agencies.
Clinical documentation, case management, county/Medi-Cal claims and billing, CalAIM compliance data, the system of record for agencies' county contracts.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.