[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Bluedot API

> No public Bluedot API was found. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/bluedot

No public Bluedot API was found; the data routes Bluedot documents include webhooks, Zapier triggers and an MCP server (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Bluedot 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 Bluedot session and returns only what your login can see.

[Try it free now](https://cotlet.dev/app/signup?app=bluedot)

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

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

curl Node.js Python

curl

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

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/meetings-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-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-this-week",
headers={"Authorization": f"Bearer {key}"},
json={"week": "2026-11-16"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"date": "2026-11-16",
"title": "Demo call",
"participants": "Dana R.",
"collection": "Sales",
"actions": 2
},
{
"date": "2026-11-17",
"title": "Interview",
"participants": "Tom H.",
"collection": "Hiring",
"actions": 1
}
]
}
```

01 Build

## How do you build a Bluedot endpoint with Cotlet?

1. 01  
app.bluedothq.com  
Signed in  
### Sign in to Bluedot in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List my meetings this week with title, participants, collection and the number of action items in the summary.  
### Do the job once with your agent.  
For example: "List my meetings this week with title, participants, collection and the number of action items in the summary."
3. 03  
Save endpoint  
Name  
meetings-this-week  
Input  
week  
Returns  
date, title, participants, collection, actions  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a week or a collection, and the fields it returns.
4. 04  
$ POST /api/v1/custom/meetings-this-week  
200 OK  
### 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 Bluedot session.

02 Endpoints

## Example endpoints you could build for Bluedot

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

- POST `/api/v1/custom/meetings-this-week`  
### Meetings in a week  
Title, participants, collection and action items for each
- POST `/api/v1/custom/search-transcripts`  
### Search transcripts  
Meetings that mention a word, with the line it is in
- POST `/api/v1/custom/meeting-summary`  
### A meeting's summary  
The AI summary and action items of the meeting you name
- POST `/api/v1/custom/unsorted-meetings`  
### Unsorted meetings  
Meetings that are in no collection yet
- POST `/api/v1/custom/move-to-collection` writes  
### Move a meeting  
The meeting you name moved to a collection
- POST `/api/v1/custom/<name>`

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

Request

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

The answer is JSON, with your fields under `data`:

Response · 200 OK

```
{
"data": [
{
"date": "2026-11-16",
"title": "Demo call",
"participants": "Dana R.",
"collection": "Sales",
"actions": 2
},
{
"date": "2026-11-17",
"title": "Interview",
"participants": "Tom H.",
"collection": "Hiring",
"actions": 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 Bluedot endpoints for?

- Schedule Cotlet endpoint Slack or email  
### A weekly action list in n8n or Make.  
Action items from the week's meetings, sent to Slack or email on Friday.
- Meeting ends endpoint CRM  
### A CRM note after each sales call.  
The summary of a sales call added to the deal in your CRM.
- Week end endpoint Google Sheets  
### A hiring sheet.  
Interviews and their summaries each week, pulled into Google Sheets.
- Chat agent endpoint transcripts  
### Your own AI assistant.  
A chat agent that searches your transcripts before it answers a question.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Bluedot session, so it can read and change only what your Bluedot 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 moving a meeting to a collection, 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.

DRY RUN · nothing sent

$ POST /api/v1/custom/move-to-collection

would POST app.bluedothq.com/... move the Monday demo call to Sales

`move-to-collection`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Bluedot have an official API?

No public Bluedot API was found on its integrations page or in its help center (checked 20 Nov 2026). Bluedot sends summaries and transcripts out through webhooks and Zapier triggers, and its MCP server lets an AI assistant read your meetings. The full picture with sources: [Does Bluedot have an API or MCP server?](https://cotlet.dev/api-status/bluedot.md)

Want ChatGPT or Claude to work in Bluedot instead of code? See the [Bluedot MCP server](https://cotlet.dev/integrations/bluedot-api-mcp-server.md).

0/3

Official API

None found

[Full API & MCP report](https://cotlet.dev/api-status/bluedot.md)

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.

## Bluedot API with Cotlet: questions

### Is this an official Bluedot API?

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

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

POST /api/v1/custom/<name>

## Build your first Bluedot endpoint

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

[Try it free now](https://cotlet.dev/app/signup?app=bluedot)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
