The SSI Group API
No API in any form: no developer portal, docs, SDKs, webhooks, or marketplace. All integration is sales-contracted EDI, moving X12 transactions (837, 835, 270/271, 276/277) in batch or real time, plus file uploads through the SSI Claims Direct portal and bespoke EHR bridges.
Frequently asked questions
The SSI Group scores F on the API Report Card. No API in any form: no developer portal, docs, SDKs, webhooks, or marketplace. All integration is sales-contracted EDI, moving X12 transactions (837, 835, 270/271, 276/277) in batch or real time, plus file uploads through the SSI Claims Direct portal and bespoke EHR bridges.
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.
The SSI Group (Mobile, AL; founded 1988) operates one of the largest hospital-focused claims clearinghouses in the US, plus RCM software for claims management (Claims Director), eligibility, denial management, remittance, claim status, and payer-side EDI, the EDI layer between hospital EHRs (Epic, MEDITECH, Oracle Health) and 2,600+ payers.
Healthcare / Clearinghouse, hospitals, health systems, physician groups, ASCs, LTC facilities, health plans.
~1/3 of the US hospital market; 2,600+ payer connections; ~1.4B EDI transactions/yr; historically $800B+ in billed claims annually.
Submitted 837 claims and scrub results, 835 ERAs/remits, eligibility responses, claim status, denial/rejection data, payer response analytics, the hospital revenue lifecycle.
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.