ClearCare API
ClearCare is the web-based operations platform that private-duty home care agencies run on, covering scheduling and shift management, caregiver recruiting and management, electronic visit verification (EVV) and telephony clock-ins, billing, payroll inputs, and family communication. This page is an independent design exercise that asks what a well-designed ClearCare 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 ClearCare 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 ClearCare 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 ClearCare?
ClearCare is the web-based operations platform that private-duty home care agencies run on, covering scheduling and shift management, caregiver recruiting and management, electronic visit verification (EVV) and telephony clock-ins, billing, payroll inputs, and family communication. Originally built by San Francisco-based ClearCare, the platform was acquired by WellSky in November 2019 and renamed WellSky Personal Care in September 2021, but much of the industry still knows it as ClearCare, and agencies still log in at clearcareonline.com. Today it powers 4,500+ agencies and 600,000 caregivers delivering roughly $6 billion in annual care, from single-site agencies to the largest franchise enterprises in home care.
Core product areas include:
- Scheduling and shift management (caregiver-to-client scheduling, open-shift management, mobile schedule access)
- Caregiver management (applicant tracking, screening and training tools, engagement and retention programs)
- EVV and visit documentation (clock-ins/outs and task documentation from the field)
- Billing and payroll inputs (invoicing, payment collection, payroll-ready hours)
- Family Room portal (client care calendar, shift notes, and family bill pay and splitting)
- Mobile app and AI workflows (WellSky Personal Care mobile app; SkySense AI summarization and ambient documentation)
An API for a platform like this would naturally organize around its core data entities:
- Clients, Care plans, Assessments
- Caregivers, Applicants, Credentials
- Shifts, Schedules, Visit records (carelogs)
- EVV clock-ins, Telephony records, Tasks
- Invoices, Payments, Payroll hours
The ClearCare Integration Challenge
Agencies run their entire operation on ClearCare, and there is a documented REST API, but access is contractual, not self-serve:
- Public docs, gated access: The WellSky Personal Care Connect API is documented at apidocs.clearcareonline.com, but you can't just sign up, access requires a signed ClearCare Connect API Agreement plus a fee-bearing Order Form
- Vendor-issued tokens: API tokens are issued by WellSky only after the contract is executed, so timelines depend on vendor legal and enablement queues
- Vendor-side enablement for partners: Even established integrations, like Checkr background checks, require WellSky-side enablement before they work for an agency
- No SDKs or marketplace: There are no client libraries or app marketplace, every integration is a bespoke, contract-first project
- Webhooks behind the same gate: Event subscriptions exist via the API's /v1/subscriptions/ resource, but only for contracted API customers
- Rebrand confusion: Logins and API docs still live on clearcareonline.com while contracts and support run through WellSky, complicating procurement and support paths
What a ClearCare API Could Look Like
If ClearCare 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 ClearCare: 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
/authenticateWould authenticate to a ClearCare (WellSky Personal Care) agency account and obtain a session token for downstream calls.
Client Operations
/clientsWould list client profiles, care plans, and status with agency and location filters.
Caregiver Operations
/caregiversWould retrieve caregiver profiles, credentials, and availability across the agency.
Scheduling
/schedulesWould pull schedules and open shifts with date-range, caregiver, and client filters.
Visits
/carelogsWould retrieve visit records with EVV clock-ins/outs, completed tasks, and shift notes.
Billing
/invoicesWould pull invoices, payments, and payroll-ready hours for billing and payroll reconciliation.
Use Cases
Sync agency operations into your systems
- Pull clients, caregivers, and schedules into a central warehouse - Stream shift and schedule changes to analytics and staffing tools - Build a single operational view across franchise locations
Automate billing and payroll
- Pull invoices and payments into accounting systems - Feed payroll-ready hours to payroll providers automatically - Flag unbilled or mismatched visits before invoicing runs
Monitor EVV and visit compliance
- Compare EVV clock-ins against scheduled shifts in real time - Flag missed, late, or short visits to care coordinators - Feed visit verification data to state EVV reporting workflows
Streamline caregiver recruiting and retention
- Sync applicant and credential data with HR and screening tools - Alert on expiring credentials before they lapse - Track caregiver utilization and retention metrics across offices
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require agency credentials and MFA handled in a managed, encrypted session
Connectivity
Would build on authenticated ClearCare web workflows surfaced as a normalized API, no Connect API Agreement or Order Form required
Response format
Normalized JSON across client, caregiver, shift, EVV, and invoice objects
Rate limits
Adaptive throttling tuned to your agency to avoid platform-side limits
Session management
Would need automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for shifts, EVV events, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned controls, and audit logging
Webhooks
Event-style callbacks for shift changes, clock-ins/outs, new clients, and invoice updates
Latency
Design target: sub-second reads on cached entities; multi-second reads on deep schedule pulls
Throughput
Design target: horizontally scaled workers sized to single-office and franchise-enterprise volume
Reliability
Retry, backoff, and idempotency keys across scheduling and billing operations
Versioning
Clear versioning and change management would matter as ClearCare evolves
Frequently asked questions
Yes. ClearCare was acquired by WellSky in November 2019 and renamed WellSky Personal Care in September 2021. It's the same platform, agencies still log in at clearcareonline.com, and this page uses the ClearCare name most of the industry still searches for.
Yes. Data flows through an encrypted credential vault with scoped tokens, HIPAA-aligned access controls, and full audit logging so client, caregiver, and visit data stays protected.
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 ClearCare 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.