Skip to main content

Overview

Zentake is a patient intake platform. Practices use it to collect demographics, insurance information, consent, and medical history from patients before a visit, on the patient's own phone, instead of a clipboard in the waiting room. The Zentake API and webhooks let your team pull that data (or push it) into the systems you already run, most commonly an EHR.

Who this is for

This section is written for anyone evaluating Zentake as an integration, product managers, practice administrators, and engineers who haven't worked with the API yet. No prior Zentake experience assumed. If you're ready to write code, jump straight to the API Reference.

What Zentake does​

  1. A patient receives a link by SMS or email for a Form or a Packet (a bundle of forms), for example, a new-patient intake packet before a first visit.
  2. The patient fills it out on their phone: demographics, insurance, consent and e-signatures, medical history. Required fields, required signatures, and office-use-only questions are enforced before the submission is accepted.
  3. The submission becomes structured data. Each completed form is a Response; a completed packet is a Packet Response that groups the individual form responses inside it.
  4. Your system picks it up. Zentake fires a webhook the moment a response is created or completed, and your integration can then fetch the structured JSON or download a filled PDF and write it into the patient's chart.

Who the API is for​

  • EHR and practice-management integrators who need patient intake data to land in a chart automatically instead of being retyped from a PDF.
  • Practice operations teams evaluating whether Zentake's data model (patients, forms, packets, responses) matches how their intake process works today.
  • Developers building or maintaining a sync between Zentake and an EHR, data warehouse, or internal tool.

Where to go next​

  • What Zentake integrates with. EHR export, webhooks, and batch patient upload, at a glance.
  • Common EHR integration patterns. The send → complete → webhook → fetch → export flow, with a sequence diagram.
  • Data model. How Patient, Form, Packet, Response, and the rest of the resources relate to each other.
  • Core Concepts. One page per resource, with the real fields and a link to the matching API Reference operations.
  • API Reference. The generated reference for every endpoint, request, and response shape.