TRUE CARE SYSTEM • API DOCUMENTATION
API Documentation
Technical reference for the True Care System application programming interfaces, security model, Provider isolation, validation, audit behavior, and integration standards.
This public documentation describes approved architectural patterns and general API behavior. Exact production routes, credentials, security controls, internal validation logic, and customer-specific integrations remain restricted to authorized implementation personnel.
API payloads may contain PHI, workforce information, Provider identifiers, billing data, authentication evidence, or other sensitive operational records. Examples use demonstration values only. Never place real credentials, access tokens, SSNs, full Medicaid identifiers, or production PHI in public documentation or source-control examples.
Purpose
Technical reference for the True Care System application programming interfaces, security model, Provider isolation, validation, audit behavior, and integration standards.
The API layer connects True Care System Web, Mobile EVV, background processes, Provider administration, reporting, billing, payroll, Sandata workflows, and future AI agents while preserving Provider isolation and auditable access.
Available API Guides
| Guide | Purpose | Documentation |
|---|---|---|
| API Overview | Understand the API architecture, request lifecycle, authentication model, Provider scope, response conventions, and production integration responsibilities. | Open guide |
| Authentication API | Authenticate approved users, establish secure sessions, validate access tokens, enforce account status, and record authentication activity. | Open guide |
| Provider API | Maintain Provider-scoped identity, operational configuration, branches, locations, branding, and administrative defaults. | Open guide |
| Employee API | Create, retrieve, update, search, and manage Provider employee records, workforce status, roles, and Sandata-related identifiers. | Open guide |
| Individual API | Manage Individual records, contact information, program data, service addresses, payer information, and readiness-critical fields. | Open guide |
| Service API | Maintain Provider service definitions, billing codes, rate relationships, unit formats, status, and operational service configuration. | Open guide |
| Authorization API | Manage service authorizations, payer and program data, approved units, date ranges, usage, remaining balance, and readiness validation. | Open guide |
| Scheduling API | Create and maintain shifts, assignments, backup-plan shifts, recurrence, conflict validation, coverage, and schedule status. | Open guide |
| Medication API | Manage medication orders, administration records, PRN documentation, medication profiles, and clinical access controls. | Open guide |
| BSS API | Support BSS cases, assessments, daily service logs, supervisor review, approval, billing readiness, and behavior-support documentation. | Open guide |
| Reports API | Retrieve Provider-scoped report data, apply filters, generate document outputs, and support controlled operational exports. | Open guide |
Core API Principles
Provider Isolation
Every protected operation must derive and enforce the authorized Provider scope on the server.
Role-Based Access
Authentication identifies the user; authorization determines whether the requested action is permitted.
Minimum Necessary
Responses should return only the data reasonably required for the approved operational purpose.
Auditability
Security-sensitive and PHI-related activity should produce sufficient evidence for authorized review.
Recommended Review Sequence
- Review API Overview and the shared request lifecycle.
- Review Authentication API before any protected module.
- Review Provider, Employee, Individual, Service, and Authorization data foundations.
- Review Scheduling, Medication, BSS, and Reports according to implementation scope.
- Complete security, HIPAA, QA, and Test Catalog review before production release.