canonical: https://jentic.com/apis/myezcare.com/myezcare # myEZcare API Jentic publishes the only available OpenAPI specification for myEZcare API, keeping it validated and agent-ready. The myEZcare API exposes a small set of endpoints for home healthcare and patient management, focused on listing and creating patient records and scheduling appointments. It targets home health, hospice, and private duty agencies that need programmatic access to patient rosters and appointment calendars. Authentication uses an API key passed in the Authorization header against the api.myezcare.com base URL. ## For AI agents List and create patients and schedule appointments inside a myEZcare home healthcare account using a header API key. ## Scope Does not handle clinical documentation, billing, or e-prescribing - use for home healthcare patient and appointment management only. ## Capabilities - Retrieve the full patient roster for downstream reporting and roster reconciliation - Register a new patient record with demographics into the myEZcare account - Pull the appointments calendar to surface upcoming patient visits to caregivers - Schedule a new patient appointment against an existing patient and caregiver - Synchronise patient and appointment data into external EHR or CRM systems ## Use cases ### Patient Onboarding Automation Automate the creation of new patient records in myEZcare when a referral arrives from an intake form or partner system. Instead of manual entry, an integration calls POST /patients with demographics and returns the created record for follow-up. This compresses intake from minutes per patient to a single API call and keeps the agency roster in sync with intake sources. Example prompt: Call POST /patients with the new referral's demographics and return the created patient identifier for the caregiver coordinator. ### Caregiver Daily Schedule View Surface today's patient appointments to caregivers in a mobile or chat interface by reading from GET /appointments. The integration filters the calendar to a date or caregiver and renders the visit list. This avoids caregivers logging into the full myEZcare portal just to see their day's visits. Example prompt: Fetch GET /appointments, filter to today's date, and return the ordered list of patient visits for the requesting caregiver. ### Visit Booking from External Channel Book new patient appointments from an external scheduling channel such as a chatbot, IVR, or referral partner portal. The integration calls POST /appointments with the patient, caregiver, and time slot, then confirms the booking back to the requester. This extends myEZcare's calendar to channels the portal does not natively serve. Example prompt: Call POST /appointments with the patient ID, caregiver ID, and visit time and return the created appointment ID to the requesting channel. ### AI Agent Scheduling Assistant An AI agent handles the full scheduling loop for a home healthcare coordinator. It searches Jentic for myEZcare scheduling operations, loads the appointment schemas, and chains GET /patients, GET /appointments, and POST /appointments to confirm patient identity, find a free slot, and book the visit. Jentic isolates the myEZcare API key in the vault so the agent never sees the raw secret. Example prompt: Search Jentic for 'schedule a home healthcare visit', load the POST /appointments schema, and book a 9am visit for patient 1234 with the on-call caregiver. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/patients` | List patients in the account | | POST | `/patients` | Create a new patient record | | GET | `/appointments` | List scheduled appointments | | POST | `/appointments` | Schedule a new patient appointment | ## Key resources - **Patients** — List existing patients and create new patient records with demographics. - **Appointments** — Retrieve the appointment calendar and schedule new patient visits. ## Why Jentic - **Setup:** Wiring the myEZcare API by hand means learning its Authorization header API key auth and structuring the patient and appointment payloads yourself. Through Jentic you install once, import the myEZcare API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Patient and appointment targets travel in the request body, so limit the agent to the operations it needs, such as listing patients or booking an appointment. You choose which operations are in scope, so a write call like creating a patient is not included unless you add it. - **Credential handling:** Your myEZcare API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'schedule a home healthcare visit' or 'list patients', and Jentic returns the matching myEZcare operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **DrChrono API** — DrChrono is a full EHR with broader patient, clinical, and billing endpoints than myEZcare's home-health focus. - **athenahealth API** — athenahealth offers a comprehensive ambulatory EHR API spanning patients, appointments, billing, and clinical data. - **Calendly API** — Calendly handles external-facing appointment booking links that can feed into myEZcare's internal calendar. ## FAQ ### Why is there no official OpenAPI spec for myEZcare API? myEZcare does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call myEZcare API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the myEZcare API use? The myEZcare API uses an API key passed in the Authorization request header. Through Jentic, this key is stored in the encrypted credential vault and never exposed to agent context - agents call myEZcare operations through Jentic and the key is injected at execution time. ### Can I schedule patient visits with the myEZcare API? Yes. Call POST /appointments with the patient identifier, caregiver, and visit time to create a new visit on the calendar. You can read existing visits with GET /appointments before booking to avoid conflicts. ### What endpoints are exposed in the myEZcare API spec? The current spec covers four endpoints: GET /patients and POST /patients for patient roster management, plus GET /appointments and POST /appointments for the visit calendar. Additional endpoints can be added if myEZcare expands the public surface. ### How do I onboard a new patient through Jentic? Search Jentic for 'create a patient in myEZcare', load the POST /patients schema, and execute the call with the patient's demographics. Jentic returns the created patient record so the agent can chain it into a follow-up appointment booking. ### What are the rate limits for the myEZcare API? The published spec does not document rate limits. Treat the API as rate-limited in production and implement exponential backoff on 429 responses. Contact myEZcare directly for account-specific limits. ### Can I limit what my agent is allowed to do with the myEZcare API? Yes. Because you run Jentic One yourself, your own rules decide which myEZcare operations the agent may call, so you can grant read-only access to GET /patients and GET /appointments while withholding writes. A booking-focused agent might be scoped to POST /appointments only, and a create call like POST /patients stays out of scope until you add it. The stored API key is injected at execution time under those same rules, so the agent can reach only the operations you have allowed.