Trengo API · unofficial, by Cotlet

Create your own Trengo API

Trengo's pricing page lists custom integrations via APIs on the Pro plan only (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Trengo 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 Trengo 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 Trengo. Trengo is a trademark of its owner. If Trengo's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/open-conversations" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"label": "Billing"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/open-conversations";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ label: "Billing" }),
});
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-conversations",
    headers={"Authorization": f"Bearer {key}"},
    json={"label": "Billing"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "conversation": "Refund for order 4417",
      "channel": "WhatsApp",
      "contact": "Dana R.",
      "last_message": "09:40",
      "assignee": "Ana"
    },
    {
      "conversation": "Invoice address change",
      "channel": "Email",
      "contact": "Tom H.",
      "last_message": "10:15",
      "assignee": "none"
    }
  ]
}

01 Build

How do you build a Trengo endpoint with Cotlet?

  1. Sign in to Trengo 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 the open conversations with the Billing label, with the channel, contact and last message time."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a label or a channel, 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 Trengo session.

02 Endpoints

Example endpoints you could build for Trengo

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

  • POST /api/v1/custom/open-conversations

    Open conversations

    Channel, contact, label and assignee for each open conversation

  • POST /api/v1/custom/unanswered

    Unanswered conversations

    Conversations waiting longer than the hours you name

  • POST /api/v1/custom/contact-history

    Contact history

    Past conversations of one contact across channels

  • POST /api/v1/custom/team-stats

    Team stats

    Conversations, first reply time and closes per person

  • POST /api/v1/custom/assign-conversation writes

    Assign a conversation

    A conversation assigned to the person or team you name

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

Request

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

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "conversation": "Refund for order 4417",
      "channel": "WhatsApp",
      "contact": "Dana R.",
      "last_message": "09:40",
      "assignee": "Ana"
    },
    {
      "conversation": "Invoice address change",
      "channel": "Email",
      "contact": "Tom H.",
      "last_message": "10:15",
      "assignee": "none"
    }
  ]
}

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

  • Schedule Cotlet endpoint Slack

    A morning backlog in Slack.

    Conversations waiting more than 12 hours, posted for the team.

  • Schedule endpoint Google Sheets

    A support sheet.

    Reply times and closes per person pulled into Google Sheets weekly.

  • Order page endpoint conversations

    Your shop or CRM.

    A customer's past Trengo conversations shown next to their order.

  • New conversation endpoint assigned

    Routing in n8n.

    New conversations assigned to a person by language or label.

04 Access

What can an endpoint see and change?

An endpoint works in your own Trengo session, so it can read and change only what your Trengo 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 assigning a conversation, 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 Trengo have an official API?

Trengo has a public API, webhooks and an official MCP server; its pricing page lists custom integrations "Via APIs" on the Pro plan only (checked 20 Nov 2026). The full picture with sources: Does Trengo 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.

Trengo API with Cotlet: questions

Is this an official Trengo API?

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

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