Sandata API
Sandata provides EVV and homecare management solutions used by providers and state Medicaid programs to ensure that in-home and community-based services are delivered and documented as required by the 21st Century Cures Act. This page is an independent design exercise that asks what a well-designed Sandata API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Sandata API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Sandata product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is Sandata?
Sandata provides EVV and homecare management solutions used by providers and state Medicaid programs to ensure that in-home and community-based services are delivered and documented as required by the 21st Century Cures Act. Sandata’s products span mobile and telephony EVV, scheduling, visit documentation, exception handling, authorization tracking, and connections to Medicaid/MCO reimbursement channels.
Core product areas include:
- Electronic Visit Verification (mobile app, telephony, aggregator connections)
- Scheduling and visit management
- Patient/client and caregiver/provider rosters
- Payer authorizations and service codes
- Exception handling and compliance reporting
- Export and billing support for Medicaid/MCO claims
An API for a platform like this would naturally organize around its core data entities:
- Clients/Members (patients)
- Caregivers/Providers (aides, nurses, staff)
- Visits (EVV check-in/out, service codes, tasks)
- Authorizations (payer, service code, units, validity dates)
- Payers/MCOs and service programs
- Schedules and assignments
- Exceptions (late/missing events, GPS mismatch, overlapping visits)
- Claims (837P/I line items referencing verified visits)
- Remittances (835 summaries for reconciliation)
The Sandata Integration Challenge
Organizations rely on Sandata daily, but turning portal-based EVV workflows into automated pipelines is hard:
- State- and payer-specific rules: Each Medicaid program/MCO may require distinct service codes, modifiers, and EVV validation logic
- Strong enterprise security: MFA and network controls complicate headless automation
- Portal-first delivery: Key EVV and exception handling lives in web apps or batch exports, not unified public APIs
- File interfaces and timing windows: SFTP/EDI feeds, batching constraints, and daily submission windows must be respected
- Compliance nuances: Visit edits require compliant reason codes and audit trails, and data retention rules vary by jurisdiction
What a Sandata API Could Look Like
If Sandata exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Sandata: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/sessionsWould establish a session using credentials. MFA challenges (SMS, email, TOTP) would need first-class support. Would return a short-lived auth token.
Authorizations
/authorizationsWould retrieve payer/member service authorizations with allowed units, service codes, and date ranges. Use this to validate scheduling and claim eligibility.
EVV Visits
/evv/visitsWould create or update an EVV visit record with check-in/out events, service details, and verification metadata. Supports compliant edit reason codes.
Claims
/claimsWould assemble an 837P/I claim from verified visits.
Use Cases
EHR-to-EVV Synchronization
- Push patient and caregiver rosters from your EHR into Sandata - Create visits automatically from your scheduling system with correct service codes and modifiers - Maintain a single source of truth for demographics and eligibility
Authorization-Aware Scheduling and Eligibility
- Validate authorizations before scheduling or visit creation - Track remaining authorized units and prevent over-utilization - Surface program-specific rules to care coordinators
EVV Exception Resolution
- Pull exception queues and route issues (e.g., late arrival, missing check-out, GPS mismatch) to staff for resolution - Apply compliant reason codes on visit edits with audit trails - Escalate unresolved exceptions prior to claim submission
Claims Generation and Reimbursement Automation
- Bundle verified visits into 837P/I claims with payer-specific formatting - Submit via the configured channel (state portal, MCO gateway, or clearinghouse) - Track claim statuses and reconcile remittances alongside EVV evidence
Audit and Compliance
- Export complete visit packets with timestamps, locations, signatures, and reason codes - Maintain machine-readable audit trails aligned to state/MCO requirements - Prove EVV coverage and claim provenance during reviews
Technical Requirements
Authentication
Would require username/password with MFA (SMS, email, TOTP); supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination
Rate limits
Tuned for enterprise throughput while honoring licensing and usage controls
Session management
Would need automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of visits, authorizations, and claim artifacts
Security
Encrypted transport, scoped tokens, and audit logging; respects Sandata entitlements and compliance requirements
Webhooks
Optional asynchronous delivery for exceptions, claim generation, and remittance updates
Latency
Design target: sub-second responses for list/detail queries
Throughput
Design target: designed for high-volume EVV and batch claims pipelines
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Versioning
Clear versioning and change management would matter as Sandata evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Sandata product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.