[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 Tidio API

> Tidio: its OpenAPI is on the Plus and Premium plans. 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/tidio

Tidio has an official OpenAPI, but most endpoints are only on the Plus and Premium plans (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Tidio 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 Tidio session and returns only what your login can see.

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

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

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

curl Node.js Python

curl

```
curl -X POST "https://cotlet.dev/api/v1/custom/open-tickets" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"topic": "order"}'
```

Node.js

```
const url = "https://cotlet.dev/api/v1/custom/open-tickets";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ topic: "order" }),
});
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/open-tickets",
headers={"Authorization": f"Bearer {key}"},
json={"topic": "order"},
)
data = res.json()["data"]
```

Response 200 OK · JSON

```
{
"data": [
{
"received": "08:12",
"customer": "Dana R.",
"subject": "Where is my order?",
"status": "open"
},
{
"received": "09:47",
"customer": "Tom H.",
"subject": "Order not here yet",
"status": "open"
}
]
}
```

01 Build

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

1. 01  
www.tidio.com  
Signed in  
### Sign in to Tidio in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
List the open tickets about orders with customer, subject and when they came in.  
### Do the job once with your agent.  
For example: "List the open tickets about orders with customer, subject and when they came in."
3. 03  
Save endpoint  
Name  
open-tickets  
Input  
topic  
Returns  
received, customer, subject, status  
### Save it as an endpoint.  
Give it a name, choose its inputs, such as a topic or a date, and the fields it returns.
4. 04  
$ POST /api/v1/custom/open-tickets  
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 Tidio session.

02 Endpoints

## Example endpoints you could build for Tidio

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

- POST `/api/v1/custom/open-tickets`  
### Open tickets  
Customer, subject and time of each open ticket
- POST `/api/v1/custom/lyro-handovers`  
### Lyro handovers  
Chats Lyro handed to a person, with their status
- POST `/api/v1/custom/find-contact`  
### Find a contact  
Matching contacts with email, properties and tags
- POST `/api/v1/custom/weekly-numbers`  
### Weekly numbers  
Conversations and reply times for a week
- POST `/api/v1/custom/tag-contact` writes  
### Tag a contact  
A tag added to the contact you name
- 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/open-tickets" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"topic": "order"}'
```

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

Response · 200 OK

```
{
"data": [
{
"received": "08:12",
"customer": "Dana R.",
"subject": "Where is my order?",
"status": "open"
},
{
"received": "09:47",
"customer": "Tom H.",
"subject": "Order not here yet",
"status": "open"
}
]
}
```

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

- Schedule Cotlet endpoint Slack  
### An open-ticket alert in Slack.  
Tickets open for more than a day, posted for your team each evening.
- Schedule endpoint CRM  
### Contacts in your CRM.  
Contacts tagged wholesale added to the CRM you already use.
- Schedule endpoint Google Sheets  
### A support sheet.  
Weekly conversations and reply times pulled into Google Sheets.
- Chat agent endpoint ticket history  
### Your own support assistant.  
A chat agent that reads a customer's last tickets before it drafts a reply.

04 Access

## What can an endpoint see and change?

An endpoint works in your own Tidio session, so it can read and change only what your Tidio 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 tagging a contact, 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/tag-contact

would POST www.tidio.com/... tag Lisa M. as wholesale

`tag-contact`writes

Allow writes

Daily cap 20 writes

05 Official API

## Does Tidio have an official API?

Tidio has an official OpenAPI for contacts, tickets and conversations, and webhooks, both on the Plus and Premium plans; its Analytics API MCP server only reads (checked 20 Nov 2026). Contacts export to CSV on every plan. The full picture with sources: [Does Tidio have an API or MCP server?](https://cotlet.dev/api-status/tidio.md)

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

2/3

Official API

Plus and Premium

[Full API & MCP report](https://cotlet.dev/api-status/tidio.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.

## Tidio API with Cotlet: questions

### Is this an official Tidio API?

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

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

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.
