tl;dv API · unofficial, by Cotlet
Create your own tl;dv API
tl;dv has an API, in alpha, but only on the Pro or Business plan (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your tl;dv 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 tl;dv 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 tl;dv. tl;dv is a trademark of its owner. If tl;dv's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/next-steps-this-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"week": "2026-W47"}' const url = "https://cotlet.dev/api/v1/custom/next-steps-this-week";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ week: "2026-W47" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/next-steps-this-week",
headers={"Authorization": f"Bearer {key}"},
json={"week": "2026-W47"},
)
data = res.json()["data"] {
"data": [
{
"meeting": "Acme Labs · kickoff",
"next_step": "Send the project plan",
"owner": "Maya",
"due": "2026-11-21"
},
{
"meeting": "Bluebird Co. · demo",
"next_step": "Book a security review",
"owner": "Leo",
"due": "2026-11-25"
}
]
} 01 Build
How do you build a tl;dv endpoint with Cotlet?
-
Sign in to tl;dv 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 the next steps agreed in this week's calls, with the meeting, the owner and the due date."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a week or a meeting title, 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 tl;dv session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for tl;dv
Cotlet ships no fixed list of tl;dv endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/next-steps-this-week Next steps for a week
Meeting, next step, owner and due date from each call
-
POST
/api/v1/custom/meetings-for-period Meetings for a period
Title, date, length and attendees of each meeting
-
POST
/api/v1/custom/quote-from-calls What was said about a topic
Quotes on a topic, with the meeting and the time in the call
-
POST
/api/v1/custom/unshared-client-calls Client calls not shared yet
Calls with outside guests that nobody has shared
-
POST
/api/v1/custom/writesshare-meeting Share a meeting
The meeting shared with the email you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/next-steps-this-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"week": "2026-W47"}' The answer is JSON, with your fields under data:
{
"data": [
{
"meeting": "Acme Labs · kickoff",
"next_step": "Send the project plan",
"owner": "Maya",
"due": "2026-11-21"
},
{
"meeting": "Bluebird Co. · demo",
"next_step": "Book a security review",
"owner": "Leo",
"due": "2026-11-25"
}
]
} 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 tl;dv endpoints for?
- After each call Cotlet endpoint Your CRM
Next steps in your CRM.
Each call's next steps added to the deal in your CRM.
- Friday endpoint Slack
A weekly call digest.
The week's calls and next steps, sent to Slack every Friday.
- On demand endpoint Google Sheets
A research sheet.
What customers said about a topic, pulled into Google Sheets.
- Chat agent endpoint meetings
Your own AI assistant.
A chat agent that reads the last call before it answers a customer.
04 Access
What can an endpoint see and change?
An endpoint works in your own tl;dv session, so it can read and change only what your tl;dv 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 sharing a meeting, 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 tl;dv have an official API?
tl;dv has an API, v1alpha1, that imports meetings and reads meetings, transcripts and notes, on the Pro or Business plan only, and an official MCP server that is read only (checked 20 Nov 2026). The full picture with sources: Does tl;dv have an API or MCP server?
Want ChatGPT or Claude to work in tl;dv instead of code? See the tl;dv 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.
tl;dv API with Cotlet: questions
Is this an official tl;dv API?
No. Cotlet is independent and not affiliated with tl;dv. The endpoints you build run in your own signed-in tl;dv 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 tl;dv changes its screens?
An endpoint works while tl;dv works the way it did when you built it. If tl;dv 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 tl;dv 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.