Skip to main content
The Scribe API has two integration surfaces. They share the same core consultation flow — set a context, run the scribe, retrieve the record. They differ in who provisions the doctor accounts and in the key you authenticate with.

​
Doctor API

Use the Doctor API when you integrate for one doctor account that already exists. Telepatia, or your own institutional integration, created the account and gave you its secret key. The flow is a single consultation loop:
  1. Set the consultation context — patient data plus a Smart Template.
  2. Launch the scribe for the clinician (or stream a live session).
  3. Retrieve the results — the scribe session and the medical-record document.
The Doctor API does not create accounts, branches, or webhooks.

​
Institutional API

Use the Institutional API when your platform provisions and manages many doctors itself. It is a superset of the Doctor API: it adds a management layer, and each doctor still runs the Doctor flow above. The flow has a provisioning step first, then the same consultation loop per doctor:
  1. Provision the institution — create doctor accounts and branches. Each account returns its own doctor secret key.
  2. Configure institution controls — webhooks and audits, authenticated with the institutional key.
  3. Run each consultation — with that doctor’s key, follow the Doctor flow above.

​
Which one do I use?

Every Doctor API endpoint is also available with the institutional key. The Institutional API only adds account, branch, webhook, and audit management on top of the same consultation flow.
Next: Authentication explains the key types, and the Quickstart runs the consultation flow end to end.