Patientco Waystar API
★ Only Publicly Available OpenAPI DocumentHealthcareEhr Emrbearer11 EndpointsREST
For Agents
Manage healthcare patient payments, billing statements, and payment plans. Retrieve patient records, process payments, and configure installment schedules for medical billing.
Use for: I need to create a new patient record for billing, I want to process a payment for a patient statement, Retrieve the payment history for a specific patient, Set up a payment plan with monthly installments
Not supported: Does not handle clinical records, appointment scheduling, or insurance claims — use for patient-facing payment collection and billing only.
Jentic publishes the only available OpenAPI specification for Waystar API, keeping it validated and agent-ready. The Waystar API (formerly Patientco) enables healthcare organizations to manage patient payments, statements, and payment plans programmatically. It provides 11 endpoints for creating and retrieving patient records, processing payments, generating billing statements, and configuring installment payment plans. The API uses Bearer token authentication and operates on the patientco.com domain.
Install Jentic One Beta
Connect the Waystar API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Waystar 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 Waystar API.
Create and retrieve patient records with demographic and contact information
Process individual payments and track payment status by ID
Generate billing statements tied to specific patient accounts
Configure installment payment plans with custom terms and schedules
Retrieve payment history and statement details for patient accounts
Update existing patient records and payment plan configurations
Look up individual statements and payments by unique identifier
Use Cases
Patterns agents use Waystar API for, with concrete tasks.
★ Patient Payment Processing
Process payments against outstanding patient balances using the Waystar API. The payments endpoint accepts payment amounts, methods, and patient references, returning confirmation with transaction identifiers. This enables automated payment collection from patient portals, kiosks, or agent-driven billing systems.
Create a payment of $150.00 for patient ID 'pat_12345' via POST /payments and verify the payment status is confirmed
Billing Statement Management
Generate and retrieve patient billing statements that itemize charges, adjustments, and balances owed. Statements are linked to patient records and can be queried individually or in bulk. This supports automated statement delivery, balance verification, and patient communication workflows.
Retrieve the latest statement for patient 'pat_12345' via GET /statements and extract the total balance due
Payment Plan Configuration
Set up installment payment plans that allow patients to pay outstanding balances over time. The payment-plans endpoint supports configuring plan terms including installment amounts, frequency, and duration. Plans are linked to patient records and can be retrieved or modified after creation.
Create a 6-month payment plan for patient 'pat_12345' with monthly installments of $50.00 via POST /payment-plans
AI Agent Healthcare Billing Automation
AI agents integrate with the Waystar API through Jentic to automate patient billing workflows without managing Bearer token lifecycle directly. Agents search for billing operations like 'create a patient payment' and Jentic returns the operation schema with required parameters, handling credential injection at execution time.
Search Jentic for 'process a patient payment', load the operation schema for POST /payments, and execute with patient ID and amount parameters
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for waystar api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/patients
Create a new patient record
GET
/patients/{patientId}
Retrieve a patient by ID
POST
/payments
Process a payment
GET
/payments/{paymentId}
Get payment details
POST
/statements
Generate a billing statement
GET
/statements/{statementId}
Retrieve a statement by ID
POST
/payment-plans
Create a payment plan
GET
/payment-plans/{planId}
Get payment plan details
POST
/patients
Create a new patient record
GET
/patients/{patientId}
Retrieve a patient by ID
POST
/payments
Process a payment
GET
/payments/{paymentId}
Get payment details
POST
/statements
Generate a billing statement
GET
/statements/{statementId}
Retrieve a statement by ID
POST
/payment-plans
Create a payment plan
GET
/payment-plans/{planId}
Get payment plan details
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Waystar Bearer tokens are stored encrypted in the Jentic vault. Agents receive automatic token injection for each request without exposure to raw API credentials.
Intent-based discovery
Agents search by intent (e.g., 'process a patient payment') and Jentic returns matching Waystar operations with parameter schemas, enabling direct execution without reading billing documentation.
Time to first call
Direct Waystar integration: 1-3 days for auth setup, error handling, and payment flow testing. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
General payment processing with card, wallet, and bank support
Use Stripe for general-purpose payment infrastructure. Use Waystar for healthcare-specific patient billing with statement and payment plan workflows.
FAQs
Specific to using Waystar API through Jentic.
Why is there no official OpenAPI spec for Waystar API?
Waystar does not publish an OpenAPI specification for their patient payments API. Jentic generates and maintains this spec so that AI agents and developers can call Waystar 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 Waystar API use?
The Waystar API uses Bearer token authentication. All requests require an Authorization header with a valid Bearer token. Through Jentic, tokens are stored encrypted in the credential vault and automatically injected into requests so agents never handle raw credentials.
Can I set up recurring payment plans through this API?
Yes. The POST /payment-plans endpoint creates installment payment arrangements linked to a patient record. You specify the plan terms including total amount, number of installments, and frequency. Existing plans can be retrieved via GET /payment-plans/{planId} to check status and remaining balance.
What patient data can I manage with the Waystar API?
The /patients endpoints allow creating and retrieving patient records that include demographic information, contact details, and billing references. Patients are identified by a unique patientId which links them to their payments, statements, and payment plans.
How do I process a patient payment through Jentic?
Search Jentic for 'process a patient payment', load the operation schema for POST /payments, and execute with the patient ID, amount, and payment method parameters. Jentic injects the Bearer token automatically. Install with pip install jentic.
Is the Waystar API the same as Patientco?
Yes. Waystar acquired Patientco and the API operates on the patientco.com domain. The API surface and functionality remain the same, providing patient payment management capabilities under the Waystar brand.
GET STARTED