Summary and recommendation
Spring Health does not expose a public REST API, SCIM 2.0 endpoint, OAuth application registration, or developer portal.
No API credentials, sandbox environment, or webhook system has been publicly documented.
The platform is absent from Okta, Entra ID, Google Workspace, and OneLogin SCIM integration catalogs.
All integration capability must be confirmed directly with Spring Health's enterprise implementation team - data here is sparse by necessity, not omission.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No publicly documented webhook system found. Spring Health typically receives member eligibility data via secure file-based feeds (e.g., SFTP eligibility files) negotiated during employer onboarding, not via a self-serve webhook API.
Alternative event strategy: Eligibility management is handled through employer-negotiated SFTP file feeds or HR platform integrations arranged via Spring Health's implementation team.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No publicly documented SCIM 2.0 endpoint found.
- Spring Health does not appear in Okta, Entra ID, Google Workspace, or OneLogin integration catalogs as a SCIM-enabled app.
- User provisioning is handled via employer eligibility file feeds, not SCIM.
Common scenarios
The only documented integration pattern is periodic SFTP-based eligibility file feeds, negotiated during employer onboarding.
There are no publicly documented real-time provisioning scenarios, event-driven deprovisioning hooks, or identity graph synchronization paths.
Any attempt to build automated lifecycle management against Spring Health should be scoped as a file-exchange workflow rather than an API-driven one, with cadence and format agreed contractually with Spring Health's implementation team.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The absence of a SCIM endpoint or REST API means Spring Health cannot participate in a standard identity graph - there is no mechanism to push user state changes from an IdP or IGA platform in real time.
SFTP eligibility files introduce lag between an HR system of record and Spring Health's member roster, creating a window where terminated employees may retain active benefit access. No rate limit headers, retry semantics, or pagination contracts exist to document because no API surface is exposed.
Engineers building automated offboarding pipelines should treat Spring Health as an out-of-band exception requiring manual or scheduled file-based reconciliation until the vendor confirms otherwise.
Automate Spring Health workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
