Foothold Technology API
Foothold Technology makes AWARDS, a long-standing EHR and care-management platform for human services agencies, behavioral health, intellectual/developmental disabilities (I/DD), homeless services, supportive housing, and home and community-based services. This page is an independent design exercise that asks what a well-designed Foothold Technology 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 Foothold Technology 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 Foothold Technology 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 Foothold Technology?
Foothold Technology makes AWARDS, a long-standing EHR and care-management platform for human services agencies, behavioral health, intellectual/developmental disabilities (I/DD), homeless services, supportive housing, and home and community-based services. The platform spans service and treatment plans, e-prescribing and E-MAR, billing, scheduling, reporting and analytics, outcomes tracking, and HMIS workflows. Foothold is part of the Radicle Health family and serves more than 1,000 human services agencies across the U.S., with a concentration in New York and New Jersey.
For nonprofit and public agencies, AWARDS is the system of record for case management, clinical documentation, program enrollment and census, and Medicaid billing, the operational core of their county and state contracts.
An API for a platform like this would naturally organize around its core data entities:
- Client demographics and case management records
- Service and treatment plans
- Program enrollment and census data
- Clinical documentation and medication records (E-MAR)
- Medicaid billing and claims data
The Foothold Technology Integration Challenge
- The only public API surface is the ONC (g)(10)-mandated FHIR API, a compliance endpoint focused on read-oriented USCDI clinical data, not a general operational API.
- FHIR app access requires OAuth2 application registration through Foothold itself, there is no self-serve developer signup.
- Operational data, billing, scheduling, case management, program enrollment, census, has no public API at all.
- No SDKs, no documented webhooks, and no integration marketplace, interoperability is limited to vendor-managed connections to labs, pharmacies, and collaboratives.
- Agencies answering county and state reporting requirements are left with manual exports from a decades-old system of record.
What a Foothold Technology API Could Look Like
If Foothold Technology 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 Foothold Technology: 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 establish an authenticated session with AWARDS, including MFA handling and automatic session refresh.
Client Operations
/clientsWould retrieve client demographics and case management records across programs.
Care Management
/service_plansWould fetch service and treatment plans with goals, objectives, and review dates.
Program Operations
/program_enrollmentsWould list program enrollments, admissions, and discharges for census and utilization tracking.
Program Operations
/censusWould retrieve current census and occupancy data across residential and day programs.
Billing
/submit_claimWould submit Medicaid claims into AWARDS billing workflows and track submission status.
Use Cases
County and state reporting automation
- Pull enrollment, census, and service data for contract reporting - Replace manual AWARDS exports with scheduled programmatic syncs - Keep funders' reporting portals in sync with the system of record
Medicaid billing oversight
- Extract claims and billing data into finance and BI tools - Monitor denials and reimbursement timelines by program - Reconcile AWARDS billing against state remittances
Case management coordination
- Sync client records and service plans with care coordination platforms - Trigger workflows when enrollments, discharges, or plan reviews occur - Give supervisors a live view of caseloads across programs
Beyond-FHIR data access
- Access operational data the compliance FHIR endpoint doesn't expose - Combine clinical, enrollment, and billing data in one API - Feed data warehouses without vendor-managed interface projects
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require managed credential-based login with MFA support;
Connectivity
Would build on REST API over HTTPS
Response format
Normalized JSON schemas across case management, clinical, and billing entities
Rate limits
Tuned per tenant to stay within safe platform thresholds
Session management
Would need automatic session refresh and re-authentication on expiry
Data freshness
On-demand fetches with optional scheduled syncs; near real-time
Security
Encryption in transit and at rest; HIPAA-eligible data handling
Webhooks
Latency
Design target: typical reads return in seconds
Throughput
Design target: scales with concurrent managed sessions per agency
Reliability
24/7 monitoring with automated failure detection and recovery
Versioning
Clear versioning and change management would matter as Foothold Technology 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 Foothold Technology 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.