Sandata API
A real-time EVV REST API exists, but it serves states and EVV vendors under contract, not a public program. Specs are distributed as state-specific PDF user guides, auth is Basic, and batches cap at 5,000 records. No developer portal, self-serve signup, or SDKs.
Frequently asked questions
Sandata scores F on Supergood's API Report Card. A real-time EVV REST API exists, but it serves states and EVV vendors under contract, not a public program. Specs are distributed as state-specific PDF user guides, auth is Basic, and batches cap at 5,000 records. No developer portal, self-serve signup, or SDKs.
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. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Sandata is a homecare-ecosystem software provider best known for pioneering Electronic Visit Verification (EVV).
Healthcare / EHR (Homecare), Typically for home-care and I/DD agencies, caregivers, MCOs, and state Medicaid programs needing EVV compliance and agency management. Caregivers clock in/out via the mobile app to verify visits; agencies manage scheduling, billing/claims, payroll, and compliance; states/MCOs receive EVV data through Sandata's aggregator for Medicaid reimbursement and fraud detection.
Invented EVV ~40 years ago; holds 20+ state Medicaid EVV aggregator contracts and is the most-implemented EVV vendor. HITRUST/SOC compliant. Recently acquired by HHAeXchange, consolidating it among the dominant homecare platforms.
Yes, Visit verification records, caregiver/patient schedules, billing/claims, and Medicaid reimbursement data. This is the financial and compliance system of record for homecare agencies and state programs.
~40+ years old (EVV pioneered 1994; company older). Legacy architecture reflected in 'DOS-feel' UX complaints; modernizing via the Fuse platform. Acquired by HHAeXchange.
API access/specs are per-state, contract-gated PDFs rather than a self-serve portal. Third-party EVV integrations (e.g. Axxess) require state/Sandata-specific setup. Full sourced list under Sources below.
Common alternatives include HHAeXchange (parent), Axxess, CareSmartz360, Tellus / Netsmart, AlayaCare. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Sandata MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Sandata doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.