The SSI Group API
The SSI Group operates one of the largest hospital-focused claims clearinghouses in the US — the EDI layer between hospital EHRs and more than 2,600 payers, processing claims, remittances, eligibility, and claim status at massive scale. But there is no public API, developer portal, or SDK: all integration is sales-contracted X12 EDI, portal file uploads, and bespoke EHR bridges. Supergood creates a managed SSI Group API so your systems can programmatically access claims, remits, denials, and eligibility data without an EDI project.
What is The SSI Group?
The SSI Group (Mobile, AL; founded 1988) operates one of the largest hospital-focused healthcare claims clearinghouses in the US, alongside revenue cycle software for claims management, denial management, prior authorization, real-time and pre-billing eligibility, remittance management, and claims analytics. Its clearinghouse connects providers "to thousands of commercial and government payers through a single platform," maintaining edits for more than 2,600 payers.
SSI is the EDI layer between hospital EHRs — Epic, MEDITECH, Oracle Health — and payers, processing HIPAA transactions including eligibility checks (270/271), claims submission (837P and 837I), electronic remittance advice (835), claim status inquiries (276/277), attachments (275), and authorizations (278). Roughly a third of US hospitals run claims through SSI, at a volume of over a billion EDI transactions per year.
Common data entities:
- Claims — submitted 837 claims with edit and scrub results
- Remittances — 835 ERAs and payment reconciliation data
- Eligibility — 270/271 real-time and pre-billing eligibility responses
- Claim status — 276/277 inquiries and payer responses
- Denials — rejection and denial detail with payer response analytics
The SSI Group Integration Challenge
- Zero public API surface — no developer portal, API docs, SDKs, webhooks, or integration marketplace exist anywhere on SSI's site.
- EDI-only integration — connectivity is X12 batch or real-time transactions (837, 835, 270/271, 276/277, 275, 278), all provisioned through sales contracts rather than self-serve access.
- Portal and file-upload workflows — offerings like SSI Claims Direct mean signing a contract and uploading 837 files through the SSI portal; corrections happen inside the platform UI.
- Bespoke EHR bridges — Epic, MEDITECH, and Oracle Health connectivity runs through custom-built web-services bridges, not a documented API anyone can adopt.
- Revenue-critical data behind the login — scrub results, denial detail, remit data, and payer response analytics for roughly a third of US hospitals live inside SSI's platform with no programmatic path out.
How Supergood Creates SSI Group APIs
Supergood builds and operates a managed, unofficial API on top of the SSI platform your organization already uses. Instead of standing up an X12 EDI pipeline or scraping portal screens by hand, your systems get clean REST endpoints backed by Supergood's automation layer, which securely drives SSI the same way an authorized billing analyst would.
- Automated authentication — handles SSI portal login, MFA, and session refresh so access never breaks on expired sessions
- Normalized JSON — claims, edit results, remits, eligibility responses, and denial detail returned as structured objects instead of raw X12
- Change monitoring — Supergood watches SSI's UI and workflows and adapts the API automatically when the platform changes
Use The SSI Group with AI agents: The SSI Group MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute call to walk through your SSI workflows, the claims and remit data you need, and your target systems. - Supergood Generates and Validates Your API
We build a production-ready SSI Group API scoped to your entities — claims, remittances, eligibility, denials — and validate it against your live account. - Deploy with Monitoring
Go live with 24/7 monitoring and continuous adaptation as SSI's platform evolves.
Potential API Endpoints
Authentication
/authenticateAuthenticate with your SSI credentials and establish a managed session (MFA handled automatically).
Claims
/claimsRetrieve submitted claims with edit and scrub results, ready for workqueue automation.
Claims
/submit_claimSubmit a claim for scrubbing and clearinghouse routing without hand-building 837 files.
Claims
/claim_statusPull claim status inquiries and payer responses (276/277) for in-flight claims.
Remittance
/remittancesRetrieve 835 ERAs and remittance detail for payment posting and reconciliation.
Eligibility
/eligibilityFetch real-time and pre-billing eligibility responses (270/271) for a patient and payer.
Use Cases
Automate claim status follow-up
- Pull status and payer responses for every in-flight claim - Prioritize follow-up work by dollar value and age - Eliminate manual portal checks across payers
Work denials faster
- Retrieve rejection and denial detail with edit-level context - Route denials to the right team automatically - Track appeal outcomes and payer response patterns
Streamline remittance posting
- Pull 835 ERA detail as structured JSON - Match remits to claims and flag variances - Feed reconciliation data to your ERP or data warehouse
Verify eligibility upstream
- Retrieve 270/271 eligibility responses programmatically - Catch coverage issues before claims go out - Reduce eligibility-related denials and rework
Technical Requirements
Authentication
Managed credential-based login with MFA support and automatic re-authentication
Connectivity
Cloud-hosted REST API — no X12 EDI pipeline, VPN, or clearinghouse contract changes required
Response format
Normalized JSON — X12 claim, remit, and eligibility data translated into structured objects
Rate limits
Managed throttling that mirrors normal user activity on the platform
Session management
Automatic session refresh, keep-alive, and recovery on expiry
Data freshness
On-demand pulls or scheduled syncs down to minute-level intervals
Security
Encrypted in transit and at rest; HIPAA-ready deployment with BAA available
Webhooks
Change-detection webhooks for new remits, claim status changes, and denials
Latency
Typically seconds for single-record reads
Throughput
Batch retrieval support for high-volume claim and remit sets
Reliability
24/7 monitoring with automatic retries and failure alerting
Adaptation
API automatically updated when SSI's UI or workflows change
Frequently asked questions
No. SSI publishes no developer portal, API docs, SDKs, or webhooks. Integration is sales-contracted EDI — X12 batch or real-time transactions, portal file uploads, and bespoke EHR web-services bridges. Supergood creates an unofficial, managed API on top of the SSI account you already have.
Submitted claims and edit/scrub results, 835 remittances, 270/271 eligibility responses, claim status and payer responses, and denial/rejection detail — returned as normalized JSON instead of raw X12 files.
No. Supergood translates SSI's claim, remit, and eligibility data into structured JSON, so your engineers work with a modern REST API rather than parsing 837/835 files or maintaining EDI tooling.
Supergood operates with your organization's authorized credentials, encrypts data in transit and at rest, and signs BAAs. Every request is scoped to your own SSI account, and access can be limited to specific transaction types.
Supergood continuously monitors SSI for UI and workflow changes and adapts the API automatically, so your integration keeps working without engineering effort on your side.