NexHealth
NexHealth is a universal, real-time API for healthcare that lets developers read from and write to dozens of electronic health record (EHR) and practice management systems through a single standardized interface. The NexHealth Synchronizer API covers patients, providers, locations, scheduling and available slots, appointments, working hours, clinical notes, treatment plans, documents, insurance (plans, coverages, claims, balances), and practice financials (charges, payments, adjustments, fee schedules), with signed webhooks for real-time events. It is used across dental and medical practices and by health-tech companies building scheduling, billing, and patient-engagement products.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles NexHealth the way a machine reads it — 39 machine-readable artifacts across 33 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 — NexHealth scores 62.4/100 (strong), with a separate agent-readiness read of 71/100 (agent native). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile NexHealth
Each block below is one kind of artifact we hold for NexHealth. 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 33
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.
NexHealth Adjustment Types API
Adjustment types used to create adjustment
NexHealth Adjustments API
Adjustments resources
NexHealth Appointment Types API
Defines booking parameters for services offerred by the practice
NexHealth Appointments API
A booking on the Practice's calendar
NexHealth Authenticates API
Authentication endpoints for NexHealth resources
NexHealth Available Slots API
Available start date/times for an appointment
NexHealth Balances API
Guarantor and Insurance Balances resources
NexHealth Charges API
Charges resources
NexHealth Claims API
Claims resources
NexHealth Clinical Notes API
Clinical notes are the official documentation of a patient's clinical encounter or care interaction
NexHealth Document Types API
A document types resource
NexHealth Fee Schedules API
A fee schedules resource
NexHealth Institutions API
An organization containing at least one location is refered to as Institution
NexHealth Insurance API
An insurance resource
NexHealth Locations API
A singular Practice/clinic/office
NexHealth Nex Staff API
NexHealth staff users
NexHealth Onboardings API
An Onboarding resource
NexHealth Operatories API
A chair or room that can be booked
NexHealth Patient Alerts API
Short communication contents to Patients requiring a response
NexHealth Patient Documents API
A patient documents resource
NexHealth Patient Recalls API
Notifications used for encouraging patients to book follow-up appointments with providers
NexHealth Patients API
A patients resource
NexHealth Payment Plans API
Payment plans resource
NexHealth Payment Types API
Payments types used to create payments
NexHealth Payments API
Payments resources to view and create payments
NexHealth Procedures API
A procedures resource
NexHealth Providers API
A providers resource
NexHealth Recall Types API
A recall notification type
NexHealth Sync Status API
Status of a NexHealth EHR synchronization service
NexHealth Treatment Plans API
A treatment plans resource
NexHealth Webhook Endpoints API
Save and configure API user endpoints for use with webhooks
NexHealth Webhook Subscriptions API
Configure webhook subscriptions to receive event based hooks
NexHealth Working Hours API
Configure working hours for providers
Scroll within the panel for all 33 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
nexhealth-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Nexhealth Webhooks
ASYNCAPISecurity Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for NexHealth — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
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/nexhealth · machine-readable index on apis.io