Phreesia is the patient intake and engagement platform behind more than 180 million patient visits a year — digitizing registration, insurance capture, consents, and copay collection for thousands of US healthcare organizations. But Phreesia has no public developer portal: every integration is built by Phreesia's own interface team over HL7v2, FHIR, and data extracts. Supergood creates a managed Phreesia API so your team can programmatically access intake, insurance, and payment data without waiting on an interface project.

Phreesia (NYSE: PHR) is a patient intake and engagement platform that digitizes registration, scheduling, digital consent forms, insurance capture, eligibility and benefits verification, and copay and balance collection for US medical groups, specialty practices, and health systems. Its product suite spans mobile and in-office registration, online scheduling, automated eligibility and benefits (E&B) verification, e-cashiering and flexible payment options, procedural consents, patient-reported data collection, and analytics.
Phreesia sits between patients and the practice's EHR or practice management system, syncing demographics, insurance, and payments bidirectionally. It supports roughly 4,650 healthcare services clients and more than 180 million patient visits per year — about one in six US patient visits — making it one of the largest repositories of intake, insurance, and patient-payment data in American healthcare.
Common data entities:
Supergood builds and operates a managed, unofficial API on top of the Phreesia platform your organization already uses. Instead of waiting on an HL7 interface project or negotiating a custom data extract, your systems get clean REST endpoints backed by Supergood's automation layer, which securely drives Phreesia the same way an authorized staff member would.
Use Phreesia with AI agents: Phreesia MCP Server →
Authentication
/authenticateAuthenticate with your Phreesia credentials and establish a managed session (MFA handled automatically).
Patient Operations
/patientsRetrieve patient demographics and registration records captured during intake.
Patient Operations
/appointmentsList appointments with check-in and arrival status across locations.
Intake
/intake_formsFetch completed intake packets, screeners, and signed consent forms for a patient or visit.
Billing
/eligibilityRetrieve insurance capture and eligibility & benefits verification results.
Billing
/paymentsPull copay and balance payment transactions, including amounts collected and posting status.
- Pull completed registration packets, demographics, and consents as structured JSON - Push updates into your EHR, CRM, or data warehouse without an HL7 interface project - Keep patient records consistent across systems automatically
- Retrieve copay and balance transactions collected through Phreesia - Match payments against PM system postings to catch posting failures - Feed clean payment data into revenue-cycle reporting
- Pull E&B verification results ahead of scheduled visits - Flag failed or missing verifications for front-desk follow-up - Reduce eligibility-related denials before claims go out
- Track appointment arrivals and check-in status in near real time - Build no-show and utilization analytics across locations - Trigger workflows when patients complete or abandon intake
Authentication
Managed credential-based login with MFA support and automatic re-authentication
Connectivity
Cloud-hosted REST API — no VPN, interface engine, or HL7 feed required
Response format
Normalized JSON across all endpoints
Rate limits
Managed throttling that mirrors normal user activity on the platform
Session management
Automatic session refresh, keep-alive, and recovery on expiry
Data freshness
On-demand pulls or scheduled syncs down to minute-level intervals
Security
Encrypted in transit and at rest; HIPAA-ready deployment with BAA available
Webhooks
Change-detection webhooks for new intake submissions, payments, and appointment events
Latency
Typically seconds for single-record reads
Throughput
Batch retrieval support for high-volume record sets
Reliability
24/7 monitoring with automatic retries and failure alerting
Adaptation
API automatically updated when Phreesia's UI or workflows change
No. Phreesia has no public developer portal, self-serve signup, API keys, sandbox, or SDKs. Its integrations are built and managed by an internal team using HL7v2, FHIR, proprietary APIs, and data extracts, and access runs through sales. Supergood creates an unofficial, managed API on top of the Phreesia account you already have.
Patient demographics and registration records, appointment and check-in status, completed intake and consent forms, insurance capture and eligibility & benefits results, and copay/balance payment transactions — returned as normalized JSON.
Supergood operates with your organization's authorized credentials, encrypts data in transit and at rest, and signs BAAs. You control which data the API can access, and every request is scoped to your own Phreesia account.
Phreesia-built interfaces are implementation projects with their own timelines and costs, limited to the systems Phreesia chooses to support. A Supergood API is delivered in days, returns modern JSON instead of HL7 feeds, and can cover data that interfaces don't expose.
Supergood continuously monitors Phreesia for UI and workflow changes and adapts the API automatically, so your integration keeps working without engineering effort on your side.