SETWorks API
SETWorks is a cloud platform built for disability service agencies, IDD providers running day programs, employment services, community services, personal care, and residential programs. This page is an independent design exercise that asks what a well-designed SETWorks 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 SETWorks 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 SETWorks 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 SETWorks?
SETWorks is a cloud platform built for disability service agencies, IDD providers running day programs, employment services, community services, personal care, and residential programs. Founded in Kansas City and backed by a Polaris Growth Fund investment in May 2025, it serves organizations in 38 states.
The platform spans the client record, case management, service delivery documentation, scheduling, billing for state-specific Medicaid waiver programs, electronic visit verification (EVV), time and attendance feeding payroll, and an AI layer for note summarization and QA. For the agencies that run on it, SETWorks is the operational system of record.
An API for a platform like this would naturally organize around its core data entities:
- Clients and case records
- Service and attendance documentation
- EVV visit data
- Medicaid waiver claims and billing
- Schedules, staff time, and payroll data
The SETWorks Integration Challenge
- No public API, developer portal, SDKs, or webhooks, SETWorks publishes no self-serve integration surface.
- Existing integrations, QuickBooks, Paycom, ADP, Paylocity, and state EVV aggregators like Sandata, are vendor-built and enabled by the SETWorks team, not connectors you can configure yourself.
- Claims often move via file exports formatted for state Medicaid waiver systems rather than API calls.
- Anything beyond the pre-built list requires contacting the SETWorks team, custom integration requests route through the vendor.
- State-by-state waiver billing and EVV rules mean data structures vary by program, which makes one-off export-based workarounds brittle.
What a SETWorks API Could Look Like
If SETWorks 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 SETWorks: 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
/authenticateClient Operations
/clientsWould retrieve client records with demographics, program enrollment, and plan context.
Service Documentation
/service_recordsWould pull service delivery and attendance documentation, filterable by client, program, staff, and date range.
EVV
/evv_visitsWould retrieve EVV visit records including check-in/out times, locations, and verification status.
Scheduling
/schedulesWould retrieve staff and client schedules across programs and locations.
Billing
/claimsWould retrieve Medicaid waiver claims and billing statuses across state programs.
Use Cases
Medicaid waiver billing automation
- Pull claims and billing statuses from SETWorks on a schedule - Reconcile against state remittances in your finance system - Flag rejected or stalled claims for rework without manual exports
EVV compliance monitoring
- Sync EVV visit records into a compliance dashboard - Detect missing or unverified visits before aggregator submission deadlines - Cross-check EVV data against scheduled services
Payroll and attendance sync
- Extract staff time and attendance data automatically - Feed payroll systems beyond the vendor-built connector list - Eliminate re-keying between service documentation and payroll
Agency-wide reporting
- Aggregate client, service, and billing data into a warehouse - Build cross-program utilization and outcomes dashboards - Report across states without wrestling per-program export formats
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Connectivity
Would build on cloud-to-cloud; no on-premise agents or VPNs required.
Response format
Normalized JSON over REST.
Rate limits
Session management
Would need automatic session refresh and re-authentication; no manual logins.
Data freshness
On-demand reads plus configurable sync intervals for bulk pulls.
Security
HIPAA-aligned handling of PHI; encryption in transit and at rest; credentials stored in a secrets vault.
Webhooks
Latency
Design target: typical reads return in seconds; large exports run asynchronously.
Throughput
Design target: paginated, batchable access designed for multi-program agency volumes.
Reliability
Monitored 24/7 with automatic retries and failure alerting.
Versioning
Clear versioning and change management would matter as SETWorks 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 SETWorks 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.