myEZcare API
★ Only Publicly Available OpenAPI DocumentHealthcareAppointment SchedulingapiKey4 EndpointsREST
For Agents
List and create patients and schedule appointments inside a myEZcare home healthcare account using a header API key.
Use for: I need to add a new patient to our myEZcare account, List all patients currently registered in myEZcare, Schedule a home visit appointment for a patient, Retrieve all upcoming appointments on the myEZcare calendar
Not supported: Does not handle clinical documentation, billing, or e-prescribing — use for home healthcare patient and appointment management only.
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.
Install Jentic One Beta
Connect the myEZcare API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the myEZcare API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with myEZcare API.
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
Patterns agents use myEZcare API for, with concrete tasks.
★ 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.
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.
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.
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.
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
4 endpoints — jentic publishes the only available openapi specification for myezcare api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
myEZcare API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access through Jentic — the raw header API key never enters agent context or logs.
Intent-based discovery
Agents search by intent (e.g., 'schedule a home healthcare visit') and Jentic returns matching myEZcare operations with their JSON Schemas, so the agent can call POST /appointments directly without reading docs.
Time to first call
Direct myEZcare integration: 1-2 days for header auth wiring, schema mapping, and error handling. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using myEZcare API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED