No developer-facing API. Phreesia consumes EHR and PM systems' APIs through roughly 15 bidirectional integrations built by its own HL7v2 and FHIR team, all behind contact sales. It exposes no portal, keys, sandbox, SDKs, or webhooks of its own.
Phreesia scores F on the API Report Card. No developer-facing API. Phreesia consumes EHR and PM systems' APIs through roughly 15 bidirectional integrations built by its own HL7v2 and FHIR team, all behind contact sales. It exposes no portal, keys, sandbox, SDKs, or webhooks of its own.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Phreesia is a publicly traded (NYSE: PHR) patient intake platform digitizing registration, consent forms, insurance capture, copay/balance collection, and appointment workflows.
Healthcare / Patient Intake, US medical groups, specialty practices, health systems, hospitals (plus a life-sciences arm).
~4,658 average healthcare services clients (Q4 FY2026); $480.6M FY2026 revenue (+14% YoY), first annual profitability; 180M+ patient visits/yr, roughly 1 in 6 US visits.
Intake/registration forms, demographics, insurance eligibility and card capture, consents, copays and balance payments (real-time posting), appointment/check-in data, PROs/screeners.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.