The API Report CardAPI Index
HHAeXchange

HHAeXchange API

Home Care / EVV · hhaexchange.com

A JSON API with OAuth 2.0 exists and is documented in the knowledge base, but it is partner-gated, not self-serve. Providers and EVV vendors email the integration support desk per state, and a vendor relationship team issues credentials. EVV specs differ state by state.

Last verified: July 2026Healthcare
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA documented OAuth 2.0 JSON API exists in the public knowledge base; the constraint is partner gated onboarding, not existence.
AccessFAILNot self-serve: providers email the third-party integration desk per state and credentials come from the vendor team.
CoveragePOORSeparate EVV aggregator specs per state fragment the surface; every state is its own integration.
AuthGOODAuthentication is OAuth 2.0; production credentials are issued by the vendor relationship team in 1 to 2 business days.
Docs & DXFAILNo official SDKs or sandbox; developer material is knowledge-base articles with per-state specs.
StabilityMIXED
Supergood: HHAeXchange has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

HHAeXchange scores F on the API Report Card. A JSON API with OAuth 2.0 exists and is documented in the knowledge base, but it is partner-gated, not self-serve. Providers and EVV vendors email the integration support desk per state, and a vendor relationship team issues credentials. EVV specs differ state by state.

Tried to integrate with HHAeXchange?
SOURCES
API access requires manual vendor-relationship onboarding, not self-serve knowledge.hhaexchange.com
Separate EVV aggregator spec per state increases integration burden knowledge.hhaexchange.com
Onboarding for integration requires emailing a support desk per state knowledge.hhaexchange.com
Fragmented state-by-state EVV API specifications knowledge.hhaexchange.com
Complex multi-payer billing/compliance workflows hhaexchange.com