Phreesia
Phreesia is a patient intake, registration, scheduling, payments, and engagement platform for healthcare organizations, powering more than 150 million patient visits annually. It delivers digital check-in, mobile intake and consent forms in 20+ languages, logic-driven patient interviews, real-time insurance eligibility verification, and patient payments, and pushes the resulting data back into the provider's systems of record. Phreesia is not a self-serve public API product - it is an enterprise platform whose integrations are delivered by a dedicated interoperability team using open healthcare standards (HL7v2, FHIR, CCD, CSV) alongside proprietary APIs and data extracts, with bidirectional interfaces into EHR/EMR, PM, HIE, data warehouse, and data lake systems (Epic, athenahealth, eClinicalWorks, NextGen, Oracle Health/Cerner, Veradigm, Meditech, ModMed, and more). There is no publicly documented developer portal, API reference, or self-service key registration as of this writing; the API surface below is modeled from Phreesia's published product and integration capabilities, not from public reference documentation.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Phreesia the way a machine reads it — 7 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Phreesia scores 9.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Phreesia's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/phreesia/"
title="Phreesia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/phreesia.svg"
alt="Phreesia Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/phreesia/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/phreesia/"
title="Phreesia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/phreesia/card.svg"
alt="Phreesia Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Phreesia
Each block below is one kind of artifact we hold for Phreesia. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Phreesia Intake & Forms API
Digital intake, consent, and clinical questionnaire capture - logic-driven interviews customized per patient and delivered as mobile intake in 20+ languages. Completed intake, c...
Phreesia Registration & Demographics API
Bidirectional patient registration and demographic data exchange - verify and update patient identity, contact, and demographic fields and write them back to the EHR/PM system o...
Phreesia Scheduling & Appointments API
Appointment scheduling, reminders, and contactless mobile/kiosk check-in, driving arrival status back into the practice management system. Modeled on HL7v2 SIU and FHIR Appointm...
Phreesia Insurance Eligibility Verification API
Real-time insurance eligibility and benefits verification at or before check-in, returning coverage, copay, and patient-responsibility estimates. Modeled on X12 270/271 eligibil...
Phreesia Payments API
Patient payments, card-on-file, copay collection, and payment plans, with real-time payment posting back to the PM/billing system. Endpoints are modeled from published product c...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Phreesia — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/phreesia · machine-readable index on apis.io
This is an independent, third-party profile of Phreesia, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.