Heidi API · unofficial, by Cotlet
Create your own Heidi API
Heidi's API and widget are for integration partners and closed to new integrations in Australia and New Zealand (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Heidi account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Heidi session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Heidi. Heidi is a trademark of its owner. If Heidi's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/sessions-without-document" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-20"}' const url = "https://cotlet.dev/api/v1/custom/sessions-without-document";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-20" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/sessions-without-document",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-20"},
)
data = res.json()["data"] {
"data": [
{
"session": "Knee pain, physio plan",
"time": "09:10",
"patient": "J. M.",
"template": "SOAP"
},
{
"session": "Lower back review",
"time": "13:15",
"patient": "A. P.",
"template": "SOAP"
}
]
} 01 Build
How do you build a Heidi endpoint with Cotlet?
-
Sign in to Heidi in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List today's sessions with no document yet, with time, patient initials and template."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a word in the note, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Heidi session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Heidi
Cotlet ships no fixed list of Heidi endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/sessions-without-document Sessions without a document
Time, patient initials and template of each one
-
POST
/api/v1/custom/find-sessions Find sessions
Sessions that mention a word you name, with their date
-
POST
/api/v1/custom/open-tasks Open tasks
Follow-up tasks not yet done, with their session
-
POST
/api/v1/custom/session-note The note of a session
The note of one session as text
-
POST
/api/v1/custom/writescreate-task Add a follow-up task
A task on the session you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/sessions-without-document" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-20"}' The answer is JSON, with your fields under data:
{
"data": [
{
"session": "Knee pain, physio plan",
"time": "09:10",
"patient": "J. M.",
"template": "SOAP"
},
{
"session": "Lower back review",
"time": "13:15",
"patient": "A. P.",
"template": "SOAP"
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Heidi endpoints for?
- Evening Cotlet endpoint Email
An evening follow-up list.
Sessions with no follow-up task, sent to your email.
- Weekly endpoint Google Sheets
Referrals in one place.
Sessions that mention a referral, listed in a sheet each week.
- Your script endpoint Practice system
Notes into your practice software.
A finished note copied to the practice system by your own script.
- Chat agent endpoint notes
Your own clinic assistant.
A chat agent that reads a session's note before it drafts a reply to the patient.
04 Access
What can an endpoint see and change?
An endpoint works in your own Heidi session, so it can read and change only what your Heidi login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as adding a follow-up task, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Heidi have an official API?
Heidi built its API and widget for partners bringing Heidi into EHRs and telehealth software; a current customer who wants to integrate contacts Customer Success (checked 20 Nov 2026). No self-serve API key for a clinician was found. The full picture with sources: Does Heidi have an API or MCP server?
Want ChatGPT or Claude to work in Heidi instead of code? See the Heidi MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Heidi API with Cotlet: questions
Is this an official Heidi API?
No. Cotlet is independent and not affiliated with Heidi. The endpoints you build run in your own signed-in Heidi account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Heidi changes its screens?
An endpoint works while Heidi works the way it did when you built it. If Heidi changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Heidi endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.