Krisp API · unofficial, by Cotlet

Create your own Krisp API

Krisp: asked "Does Krisp have an API?", Krisp answers "Not right now" (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Krisp 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 Krisp session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Krisp. Krisp is a trademark of its owner. If Krisp's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/meetings-since" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "2026-11-16"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/meetings-since";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ from: "2026-11-16" }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/meetings-since",
    headers={"Authorization": f"Bearer {key}"},
    json={"from": "2026-11-16"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "meeting": "Acme kickoff",
      "date": "2026-11-17",
      "attendees": "Dana R., Tom H.",
      "open_action_items": 3
    },
    {
      "meeting": "Weekly sync",
      "date": "2026-11-18",
      "attendees": "Team",
      "open_action_items": 1
    }
  ]
}

01 Build

How do you build a Krisp endpoint with Cotlet?

  1. Sign in to Krisp in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List my meetings since a date with the title, people and open action items."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or a folder, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in Krisp session.

02 Endpoints

Example endpoints you could build for Krisp

Cotlet ships no fixed list of Krisp endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/meetings-since

    Meetings since a date

    Title, date, people and open action items for each meeting

  • POST /api/v1/custom/open-action-items

    Open action items

    Every open action item with its meeting and owner

  • POST /api/v1/custom/meeting-summary

    Summary of a meeting

    Key points and action items of the meeting you name

  • POST /api/v1/custom/meetings-by-tag

    Meetings by tag

    Meetings with the tag you name, newest first

  • POST /api/v1/custom/file-meeting writes

    File a meeting in a folder

    A meeting moved to the folder you name

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/meetings-since" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from": "2026-11-16"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "meeting": "Acme kickoff",
      "date": "2026-11-17",
      "attendees": "Dana R., Tom H.",
      "open_action_items": 3
    },
    {
      "meeting": "Weekly sync",
      "date": "2026-11-18",
      "attendees": "Team",
      "open_action_items": 1
    }
  ]
}

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 Krisp endpoints for?

  • Schedule Cotlet endpoint Slack

    Action items in Slack.

    Open action items from the week, posted every Friday.

  • Schedule endpoint CRM

    Meeting summaries in your CRM.

    The summary of each client call, copied to the deal or contact.

  • Schedule endpoint Google Sheets

    A weekly digest in a sheet.

    The week's meetings and open items, pulled into Google Sheets.

  • AI agent endpoint email draft

    Your own follow-up agent.

    An AI agent that reads a meeting summary and drafts the follow-up email for you to check.

04 Access

What can an endpoint see and change?

An endpoint works in your own Krisp session, so it can read and change only what your Krisp login can. You choose what each endpoint does when you build it.

An endpoint that changes something, such as filing a meeting in a folder, 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 Krisp have an official API?

Krisp says it has no public API for meetings and notes and points to its integrations and Zapier instead (checked 20 Nov 2026). Krisp does run an official MCP server for AI tools and offers webhooks on Core and Advanced. The full picture with sources: Does Krisp have an API or 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.

Krisp API with Cotlet: questions

Is this an official Krisp API?

No. Cotlet is independent and not affiliated with Krisp. The endpoints you build run in your own signed-in Krisp 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 Krisp changes its screens?

An endpoint works while Krisp works the way it did when you built it. If Krisp 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 Krisp endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.