---
title: NexHealth API Integration on Truto
slug: nexhealth
category: CRM
canonical: "https://truto.one/integrations/detail/nexhealth/"
---

# NexHealth API Integration on Truto



**Category:** CRM  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 85 tools for NexHealth that AI agents can call directly.

- **create_a_nex_health_access_token** — Retrieve bearer token. This endpoint exchanges an API key for a JWT bearer token to authenticate subsequent requests. The connector calls this on connect and every 30 minutes with the stored API key; tokens last 1 hour.
- **get_single_nex_health_adjustment_type_by_id** — View adjustment type. This endpoint returns a single adjustment type. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_adjustment_types** — View adjustment types. This endpoint returns the adjustment types configured in the integrated system for the specified location. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_adjustment** — Create adjustment. This endpoint enqueues an asynchronous write-back that records a new adjustment in the connected EHR and returns 202 Accepted. Required: adjustment. `subdomain` and `location_id` default to the connected institution and location.
- **get_single_nex_health_adjustment_by_id** — View adjustment. This endpoint returns a single ledger adjustment. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_adjustments** — View adjustments. This endpoint returns the ledger adjustments for the specified location. At least one of the patient_id, provider_id, guarantor_id, claim_id, charge_id, or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **list_all_nex_health_appointment_appointment_descriptors** — View appointment descriptors. This endpoint returns the EHR appointment descriptors for a specific appointment ID under the institution specified by the subdomain parameter. descriptor_type is an optional filter. Required: appointment_id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_appointment_type_appointment_descriptors** — View appointment type appointment descriptors. This endpoint returns the EHR appointment descriptors linked to the appointment type for a specific ID, under the institution specified by the subdomain parameter or a specific location within it when appointment types are location specific; location_id is req. Required: appointment_type_id. `subdomain` defaults to the connected institution.
- **create_a_nex_health_appointment_type** — Create appointment type. This endpoint creates an appointment type under the institution specified by the subdomain parameter, or a specific location within it when appointment types are location specific; location_id is required in that case. Required: appointment_type. `subdomain` defaults to the connected institution.
- **delete_a_nex_health_appointment_type_by_id** — Delete appointment type. This endpoint permanently deletes the appointment type for a specific ID under the institution specified by the subdomain parameter, or under a specific location within it when appointment types are location specific; location_id is required in that case. Required: id. `subdomain` defaults to the connected institution.
- **get_single_nex_health_appointment_type_by_id** — View appointment type. This endpoint returns the appointment type for a specific ID under the institution specified by the subdomain parameter, or under a specific location within it when appointment types are location specific; location_id is required in that case, and is also requ. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_appointment_types** — View appointment types. This endpoint returns appointment types for the institution specified by the subdomain parameter, or for a specific location within it when appointment types are location specific. `subdomain` defaults to the connected institution.
- **update_a_nex_health_appointment_type_by_id** — Edit appointment type. This endpoint updates the appointment type identified by ID, within the institution specified by the subdomain parameter or a specific location within it; location_id is required in that case. Only the fields included in the request body are changed. Required: id, appointment_type. `subdomain` defaults to the connected institution.
- **create_a_nex_health_appointment** — Create appointment. This endpoint books an appointment for the given patient with the given provider at the specified location. When is_guardian is true, the booking is made by a guardian and a patient object with the dependent's details must be provided. Required: appt. `subdomain` and `location_id` default to the connected institution and location.
- **get_single_nex_health_appointment_by_id** — View appointment. This endpoint returns the appointment for a specific ID under the institution specified by the subdomain parameter. Related resources can be included via include[]; patient is included by default. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_appointments** — View appointments. This endpoint returns the appointments starting within the requested time window, narrowed down by the optional filters configured. At least one of location_id or foreign_id must be provided. Required: start, end. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **update_a_nex_health_appointment_by_id** — Edit appointment. This endpoint updates an existing appointment. Required: id, appt. `subdomain` defaults to the connected institution.
- **list_all_nex_health_available_slots** — View available slots. This endpoint returns the bookable slots for the requested locations over the given date range, computed from provider availabilities and existing appointments. At least one of pids or appointment_type_id must be provided. Required: start_date, days, lids. `subdomain` defaults to the connected institution.
- **get_single_nex_health_charge_by_id** — View charge. This endpoint returns a single ledger charge. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_charges** — View charges. This endpoint returns the ledger charges for the specified location. At least one of the patient_id, provider_id, procedure_id, guarantor_id, or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_claim_by_id** — View claim. This endpoint returns a single insurance claim by its NexHealth ID. Use the include parameter to embed related resources: patient, provider, guarantor, charges and/or charge_payouts. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_claims** — View claims. This endpoint returns a list of insurance claims for a location. You can filter by patient_id, guarantor_id, provider_id, updated_since or date_of_service, and must provide at least one of these filters. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **list_all_nex_health_clinical_notes** — View clinical notes. This endpoint returns the clinical notes for the specified location. At least one of the patient_id, procedure_id, entered_before, entered_after, or updated_since filters must be provided. Results are cursor-paginated. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_document_type_by_id** — View document type. This endpoint returns a single document type by its NexHealth ID for the specified location. Required: id. `subdomain` and `location_id` default to the connected institution and location.
- **list_all_nex_health_document_types** — View document types. This endpoint returns document types for the specified location, optionally filtered by active status (defaults to active only). `subdomain` and `location_id` default to the connected institution and location.
- **list_all_nex_health_fee_schedule_procedures** — View fee schedule procedures. This endpoint returns the procedure fees for the specified location. At least one of the fee_schedule_id or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_fee_schedule_by_id** — View fee schedule. This endpoint returns a single fee schedule by its NexHealth ID, with optional sideloading of procedure_fees. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_fee_schedules** — View fee schedules. This endpoint returns the fee schedules for the specified location. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_guarantor_balance_by_id** — View guarantor balance. This endpoint returns a single guarantor balance. Required: id.
- **list_all_nex_health_guarantor_balances** — View guarantor balances. This endpoint returns the guarantor balances for the specified location. At least one of the guarantor_id or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_institution_by_id** — View institution. This endpoint returns a single institution by its NexHealth ID. Required: id.
- **list_all_nex_health_institutions** — View institutions. This endpoint returns all institutions accessible to the authenticated API user.
- **get_single_nex_health_insurance_balance_by_id** — View insurance balance. This endpoint returns a single insurance balance by its NexHealth ID. Responds with a 404 when no insurance balance with this ID exists or when it belongs to a location your token cannot access. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_insurance_balances** — View insurance balances. This endpoint returns a list of insurance balances for a location: the amounts insurance is expected to pay, broken into aging buckets. You can filter by patient_id, guarantor_id or updated_since, and must provide at least one of these filters. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_insurance_coverage_by_id** — View insurance coverage. This endpoint returns a single insurance coverage by its NexHealth ID, including details of the subscriber who holds the coverage. Responds with a 404 when no coverage with this ID exists for the institution. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_insurance_coverages** — View insurance coverages. This endpoint returns a list of insurance coverages. All filters are optional: without any filters, every active insurance coverage for the institution is returned. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_insurance_plan_by_id** — View insurance plan. This endpoint returns a single insurance plan by its NexHealth ID. Use the include parameter to embed related resources: patient_coverages, subscribers and/or fee_schedule. Responds with a 404 when no plan with the given ID exists for the institution. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_insurance_plans** — View insurance plans. This endpoint returns a list of insurance plans. All filters are optional: without any filters, every insurance plan for the institution is returned. You can narrow the results by payer_id, group_num or updated_since. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **list_all_nex_health_location_appointment_descriptors** — View location appointment descriptors. This endpoint returns EHR appointment descriptors associated with the given location, optionally filtered by descriptor_type. Required: location_id.
- **get_single_nex_health_location_by_id** — View location. This endpoint returns a single location by its NexHealth ID. Required: id.
- **list_all_nex_health_locations** — View locations. This endpoint returns the institutions accessible to the caller, each with its nested list of locations. Pass subdomain to scope the response to a single institution.
- **list_all_nex_health_nex_staff** — View Nex staff. This endpoint returns NexHealth staff members for the institution, optionally filtered by inactive status or location_ids. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_operatory_by_id** — View operatory. This endpoint returns a single operatory by its NexHealth ID, optionally including appointment_types or appt_categories. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_operatories** — View operatories. This endpoint returns the operatories of the specified location. Every filter is optional. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_patient_alert** — Create patient alert. This endpoint creates a new patient alert for the given patient with a required note. Required: patient_id, patient_alert. `subdomain` defaults to the connected institution.
- **get_single_nex_health_patient_alert_by_id** — View patient alert. This endpoint returns a single patient alert by its NexHealth ID. Required: id, patient_id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_patient_alerts** — View patient alerts. This endpoint returns patient alerts for the given patient, optionally including disabled alerts by passing include_disabled: true. Required: patient_id. `subdomain` defaults to the connected institution.
- **update_a_nex_health_patient_alert_by_id** — Edit patient alert. This endpoint updates a patient alert; setting disabled: true disables the alert, but re-enabling a disabled alert is not supported and returns a 400 error. Required: id, patient_id, patient_alert. `subdomain` defaults to the connected institution.
- **create_a_nex_health_patient_document** — Create patient document. This endpoint uploads a document for the given patient; the file's name is used when inserting the document into the EHR's filesystem, while the optional name param is for NexHealth display purposes only. Required: patient_id, file. `subdomain` and `location_id` default to the connected institution and location.
- **list_all_nex_health_patient_documents** — View patient documents. This endpoint returns all documents associated with the given patient, ordered by creation date. Required: patient_id. `subdomain` defaults to the connected institution.
- **get_single_nex_health_patient_recall_by_id** — View patient recall. This endpoint returns a single active patient recall by its NexHealth ID. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_patient_recalls** — View patient recalls. This endpoint returns the patient recalls for the specified location, with the recall type and interval for each patient. Every filter is optional. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_patient** — Create patient. This endpoint creates a new patient or returns an existing patient if return_existing_if_match is true. Required: provider, patient. `subdomain` and `location_id` default to the connected institution and location.
- **get_single_nex_health_patient_by_id** — View patient. This endpoint returns a single patient by its NexHealth ID. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_patients** — View patients. This endpoint returns the patients for the specified location. Every filter is optional. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_payment_plan_by_id** — View payment plan. This endpoint returns a single payment plan by its NexHealth ID, with optional sideloading of the associated patient and guarantor. Required: id.
- **list_all_nex_health_payment_plans** — View payment plans. This endpoint returns payment plans for the specified location; at least one of guarantor_id, patient_id, or updated_since must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_payment_type_by_id** — View payment type. This endpoint returns a single payment type. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_payment_types** — View payment types. This endpoint returns the payment types configured in the integrated system for the specified location. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_payment** — Create payment. This endpoint enqueues a write-back that records the payment in the EHR and returns 202 Accepted with no body. Required: payment. `subdomain` and `location_id` default to the connected institution and location.
- **get_single_nex_health_payment_by_id** — View payment. This endpoint returns a single ledger payment. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_payments** — View payments. This endpoint returns the ledger payments for the specified location. At least one of the patient_id, provider_id, guarantor_id, claim_id, transaction_id or updated_since filters must be provided. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_procedure_by_id** — View procedure. This endpoint returns a single procedure by its NexHealth ID. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_procedures** — View procedures. This endpoint returns a list of procedures. You can filter by provider_id, patient_id, appointment_id, started_after, started_before, ended_after, ended_before or updated_since. You must provide at least one filter. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_provider_by_id** — View provider. This endpoint returns a single provider. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_providers** — View providers. This endpoint returns the providers of the institution. Every filter is optional. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **get_single_nex_health_recall_type_by_id** — View recall type. This endpoint returns a single active recall type by its NexHealth ID. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_recall_types** — View recall types. This endpoint returns recall types for the specified location, optionally filtered by foreign_id or updated_since. `subdomain` and `location_id` default to the connected institution and location.
- **list_all_nex_health_sync_statuses** — View sync status. This endpoint returns the live status of every sync the caller can access, one entry per sync, with separate read and write statuses (green or red), the last time data was read from the EHR and the last time the sync picked up write commands.
- **get_single_nex_health_treatment_plan_by_id** — View treatment plan. Returns a single treatment plan with its procedures embedded. Requesting a soft-deleted or unknown treatment plan returns 404. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_treatment_plans** — View treatment plans. Returns a cursor-paginated list of treatment plans for the institution, with each plan's procedures embedded. Soft-deleted treatment plans are excluded. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_webhook_endpoint** — Create webhook endpoint. This endpoint creates a new webhook endpoint for the authenticated API user; target_url must use HTTPS in production. Required: target_url.
- **delete_a_nex_health_webhook_endpoint_by_id** — Delete webhook endpoint. This endpoint permanently deletes a webhook endpoint belonging to the authenticated API user and returns 204 No Content. Required: id.
- **list_all_nex_health_webhook_endpoints** — View webhook endpoints. This endpoint returns all webhook endpoints for the authenticated API user, optionally filtered by active status.
- **update_a_nex_health_webhook_endpoint_by_id** — Edit webhook endpoint. This endpoint updates a webhook endpoint belonging to the authenticated API user; target_url must use HTTPS in production. Required: id.
- **create_a_nex_health_webhook_subscription** — Create webhook subscription. Creates a webhook subscription on the given webhook endpoint. The subscription is pinned to the API version used to create it (v3.0.0): webhook payloads delivered for this subscription use the v3.0.0 entity contract. Required: webhook_endpoint_id, resource_type, event. `subdomain` defaults to the connected institution.
- **delete_a_nex_health_webhook_subscription_by_id** — Delete webhook subscription. Permanently deletes the webhook subscription; deliveries for it stop immediately. Returns 204 No Content on success. Required: id, webhook_endpoint_id.
- **list_all_nex_health_webhook_subscriptions** — View webhook subscriptions. Lists all webhook subscriptions on the given webhook endpoint. When a subdomain is provided, results are scoped to that institution and exclude subscriptions without an institution (e.g. Required: webhook_endpoint_id.
- **update_a_nex_health_webhook_subscription_by_id** — Edit webhook subscription. Updates a webhook subscription. The subdomain parameter is required for request validation even when the subscription is not scoped to an institution (e.g. Onboarding); pass the subdomain of any institution your API user has access to. Required: id, webhook_endpoint_id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_working_hour_labels** — View working hour labels. This endpoint returns working hour labels. Every filter is optional. `subdomain` defaults to the connected institution. The connector pages through all results (100 per page, or your limit up to 1,000).
- **create_a_nex_health_working_hour** — Create working hour. This endpoint creates an availability for a provider at the specified location. Exactly one of days, specific_date, or custom_recurrence must be configured. Required: working_hour. `subdomain` and `location_id` default to the connected institution and location.
- **delete_a_nex_health_working_hour_by_id** — Delete working hour. This endpoint deletes a working hour. Required: id. `subdomain` defaults to the connected institution.
- **get_single_nex_health_working_hour_by_id** — View working hour. This endpoint returns a single working hour. Required: id. `subdomain` defaults to the connected institution.
- **list_all_nex_health_working_hours** — View working hours. This endpoint returns the working hours of the specified location. Every filter is optional. `subdomain` and `location_id` default to the connected institution and location. The connector pages through all results (100 per page, or your limit up to 1,000).
- **update_a_nex_health_working_hour_by_id** — Edit working hour. This endpoint updates an existing working hour. At most one of days, specific_date, or custom_recurrence can be provided. Required: id, working_hour. `subdomain` defaults to the connected institution.

## How it works

1. **Link your customer's NexHealth account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach NexHealth.** The Proxy API is a 1-to-1 mapping of the NexHealth API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Reach dozens of legacy EHRs through one integration** — NexHealth's Synchronizer gives you bidirectional access to on-premise dental and medical EHRs like Dentrix, Eaglesoft, and Open Dental. By shipping NexHealth via Truto, your SaaS instantly becomes compatible with thousands of practices running fragmented legacy systems.
- **Power AI scheduling and virtual receptionist workflows** — If you're building AI voice agents or SMS bots for clinics, you need real-time slot availability and reliable appointment write-back. Truto exposes NexHealth's slots, working hours, and appointment creation endpoints so your bot can book directly into the practice's EHR.
- **Automate revenue cycle and patient billing** — RCM and patient financing platforms can read charges, claims, insurance balances, and guarantor balances to calculate patient responsibility, then write payments and adjustments back to clear the EHR ledger — all through a single Truto connection.
- **Drive patient retention campaigns for DSOs** — Marketing CRMs serving dental groups can pull overdue recall lists across every connected location and attribute conversions back to campaigns using NexHealth webhooks, turning NexHealth into a growth channel for your customers.
- **Streamline digital intake and clinical documentation** — Intake, telehealth, and AI scribe products can fetch upcoming appointments and clinical notes, then push completed forms, PDFs, and visit summaries back into the EHR's file system without manual staff work.

## What you can build

- **Real-time appointment booking widget** — Combine appointment types, working hours, and available slots to render live availability, then create appointments (including guardian/dependent bookings) directly in the connected EHR.
- **Event-driven sync via webhooks** — Subscribe to NexHealth webhook events for patients, appointments, and documents so your product reacts instantly to changes instead of polling legacy on-premise servers.
- **Patient ledger and payment write-back** — Read charges, guarantor balances, and insurance balances, then post payments and adjustments back to the EHR to fully automate reconciliation after collecting via your own payment gateway.
- **Automated digital intake pipeline** — Trigger on new-appointment webhooks, send patients a dynamic form, then upload the signed PDF through patient documents and raise patient alerts for critical flags like allergies.
- **Recall-driven marketing automation** — Query patient recalls across every connected location to build overdue-care audiences, launch SMS or email campaigns, and attribute new bookings back through webhook events.
- **Clinic connection health dashboard** — Surface NexHealth sync statuses in your app so your customers (and your support team) can see whether a practice's local EHR connection is healthy before attempting writes.

## FAQs

### How does authentication to NexHealth work through Truto?

NexHealth uses API key–based authentication with short-lived access tokens generated from a long-lived key. Truto handles token creation and rotation for each of your end users' connections so you never store or refresh credentials yourself.

### Is data from NexHealth real-time or synced on a schedule?

NexHealth's Synchronizer bidirectionally syncs with on-premise EHRs continuously, but freshness depends on the practice's local server. For near real-time updates, use NexHealth webhook subscriptions (which Truto can provision via create_a_nex_health_webhook_subscription) instead of polling.

### Which write operations are supported?

Through Truto you can create appointments, patients, payments, adjustments, patient alerts, patient documents, appointment types, working hours, and webhook endpoints/subscriptions. Writes to the underlying EHR are asynchronous and typically return 202 Accepted.

### How do I know a practice's EHR is actually online before writing?

Use list_all_nex_health_sync_statuses to confirm the specific location's Synchronizer connection is healthy. This is especially important for billing and appointment writes, since the target EHR may be a local on-premise server.

### Does NexHealth support multi-location practices and DSOs?

Yes. You can list institutions, locations, operatories, and providers, and most resources are scoped by location — making it straightforward to build features for Dental Service Organizations managing many clinics under one NexHealth account.

### Can I handle pediatric or dependent bookings?

Yes. The create_a_nex_health_appointment endpoint supports guardian flows (e.g., is_guardian: true), so you can book minors or dependents under a responsible party through Truto.
