The conversation API.
For builders in the EU.
The same conversations, folders, and bots you have in Klang, now reachable from your code. Sign in, grab a key, send a notetaker into a meeting. From first call to production in an afternoon.
Request
import Klang from "@klang-ai/sdk-ts"; const klang = new Klang({ apiKey: process.env.KLANG_API_KEY, }); const conv = await klang.conversations.retrieve("kw3pq2nyax7lr9d"); console.log(conv.summary);
curl https://app.klang.ai/api/v1/conversations/kw3pq2nyax7lr9d \
-H "Authorization: Bearer $KLANG_API_KEY" Response 200 application/json
{ "id": "kw3pq2nyax7lr9d", "title": "Q2 roadmap planning", "created_at": "2026-04-23T13:00:00Z", "updated_at": "2026-04-23T14:32:09Z", "status": "ready", "folder_id": "12", "digest": "Q2 roadmap shipping May 28; Ada owns checklist", "summary": "Team aligned on shipping the desktop client on May 28...", "sources": [ { "id": "bf6dxh4mvw9p8sk", "type": "transcript", "duration_seconds": 3287, "language": "eng" } ] }
What's new
October 7, 2026
MCP write access
Assistants can now manage todos, tags and folders, rename or move conversations, and start transcriptions from a URL, a file or a meeting bot. Existing connections stay read-only until you reconnect. See the write tools →
June 3, 2026
MCP server
Connect your favorite AI agent straight to your workspace over MCP — they read your meetings and conversations in plain language. Set up a client →
May 20, 2026
Klang API 1.0
Conversations, folders, identity, the meeting-recorder bot, and webhooks for state changes. TypeScript SDK.