What Zentake can integrate with

Zentake is not an EHR itself. It's the intake layer in front of one. For several EHRs it can push completed intake into the chart automatically; for everything else, three complementary mechanisms let your team pull or push the data into whatever you already run.

Native EHR integrations

For a set of supported EHRs, Zentake can auto-sync completed intake straight into the patient's chart, no code on your side.

EHR	Native sync
Elation	Most complete. Demographics plus clinical data (visit notes, allergies, medications, vitals).
Athena	Demographics and documents, via the API. A Chrome-plugin mode also syncs demographics.
ChiroTouch	Demographics and document uploads.
Open Dental	Demographics and document uploads.
Office Ally	Demographics, via the Chrome plugin.

Elation, Athena, and ChiroTouch have step-by-step setup guides in the Zentake Help Center; Open Dental and Office Ally are also supported.

The Chrome plugin noted above is an early-access feature, currently in alpha/beta.

When a native integration is configured, the patient's chart ID flows back onto the Patient record as external_id / external_integration, and appears in CSV exports (for example customer_elation_id). A CSV batch upload can also carry the matching elation_id, open_dental_id, athena_id, and chirotouch_id columns so Zentake links each patient to their existing chart.

Want full control over how data lands? The three mechanisms below let you build the sync yourself against the API and webhooks.

Don't see your EHR?

If your EHR isn't listed, you have questions, or you feel something's missing, we're always open to a conversation and happy to walk you through the system. Book a demo, or reach us through our contact page. New to Zentake? You can also try it free or see pricing.

1. Real-time sync via webhooks

Webhook Configs let you register a URL that Zentake calls with an HTTP POST whenever something happens to a resource your team cares about, a patient record, form, packet, response, packet response, or PDF document being created, updated, or deleted. This is the recommended way to know the moment a patient finishes an intake packet, without polling.

• Configure a target URL, one or more event types (created / updated / deleted), and a source resource.
• Every webhook config gets a signing secret so you can verify deliveries.
• You can send a test event to a configured webhook before relying on it.

See Common EHR integration patterns for how this fits into a full send → complete → sync flow.

2. Pulling data with the REST API

Once you know a response exists (via webhook, or just by polling), the API Reference covers everything else:

• Structured data. Fetch a Response or Packet Response as JSON, with every answer, signature, and file upload attached to the question it belongs to.
• A generated PDF. Download the filled-out form or packet as a PDF, ready to attach to a chart, via the response/packet-response "download" endpoints.
• Patients. Full CRUD, so you can create, look up, or update patient records that intake responses will be linked to.
• Sending intake. Create a Message to text or email a patient a form or packet, immediately or on a schedule.

3. Batch patient upload

For migrating an existing patient list, or keeping Zentake in sync with a scheduling system that doesn't support webhooks, the Patients API accepts a CSV batch upload: submit a file, then poll (or check) the upload's status until it finishes processing.

Sandbox environment

Every team gets an isolated sandbox for testing an integration without touching production data or sending real messages to real patients:

Environment	Purpose	Limits
Production	Live data, real SMS/email delivery	Based on your plan
Sandbox	Testing only, fully isolated data	60 req/min, 500 req/day, 5 SMS/day, 10 emails/day, max 100 patients / 20 forms

Sandbox and production use different X-API-KEY / X-API-SECRET credentials, and every API response includes an X-Zentake-Environment: sandbox | production header so you can confirm which one you're talking to. See the API Reference introduction for full authentication details.