Blooming Health
Blooming Health is an AI-powered, omnichannel care-management and community-engagement platform for healthcare and social-services organizations. It lets teams design multilingual care workflows across voice, SMS, and email in minutes — automating screening and needs assessments, service recommendations, outreach, appointment reminders, wellness check-ins, emergency broadcasts, closed-loop referral tracking, and Medicaid/SNAP recertification. The platform integrates with existing EHR/CRM systems and databases via FHIR, HL7, API, and SFTP, and is HIPAA compliant with encryption in transit and at rest, role-based access controls, audit trails, BAAs, and SOC 2 documentation available on request. Blooming Health is a healthcare portfolio company of Insight Partners. It exposes an enterprise integration surface but publishes no public developer portal or API reference.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Blooming Health the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Blooming Health scores 19.6/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Blooming Health
Each block below is one kind of artifact we hold for Blooming Health. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Blooming Health — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/blooming-health · machine-readable index on apis.io