Trengo

Trengo is an omnichannel customer-engagement and shared-inbox platform that unifies email, WhatsApp, live chat, voice, SMS, and social channels into one team inbox with AI agents. The Trengo REST API (app.trengo.com/api/v2) lets you create and manage tickets, contacts, messages, channels, teams, users, labels, custom fields, webhooks, and WhatsApp templates programmatically with Bearer-token authentication.

Trengo publishes 8 API contracts indexed on the APIs.io network, including Channels API, Contacts API, Labels and Custom Fields API, and 5 more. Tagged areas include Customer Engagement, Omnichannel, Shared Inbox, Messaging, and WhatsApp.

The Trengo catalog on APIs.io includes 1 Spectral governance ruleset.

Trengo’s developer surface includes pricing, authentication, documentation, engineering blog, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

37.5/100 thin ▬ flat Agent 25/100 agent aware Front door AI 6/6 dominant Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

1 published contract

Customer Engagement Omnichannel Shared Inbox Messaging WhatsApp Customer Service

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Service Management

BC-430

MessagesTickets

GET /tickets PATCH /tickets/{ticket_id}/assign PATCH /tickets/{ticket_id}/close POST /tickets/{ticket_id}/messages

Customer Relationship Management

BC-420

Contacts

GET /contacts POST /contacts PUT /contacts/{contact_id}

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 37.5/100 · thin

Contract Quality 9.4 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 6.1 / 15

Operational Transparency 1.4 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/trengo/"><img src="https://apis.io/badge/trengo/card.svg" alt="Trengo on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 32.1 — up to +13.6 composite points Ask about this →
Contract Quality scores 49.9 — up to +12.5 composite points Ask about this →
Access Clarity scores 40.4 — up to +11.9 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/trengo/apis.yml: open an issue on github.com/api-evangelist/trengo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

Trengo Channels API

List connected channels.

Trengo Contacts API

Manage contacts and contact profiles.

Trengo Labels and Custom Fields API

Manage labels and custom fields.

Trengo Messages API

List and send text and media messages on a ticket.

Trengo Teams and Users API

Manage teams and list agents.

Trengo Tickets API

Create, list, assign, label, and close conversations.

Trengo Webhooks API

Trengo Whats App API

Send approved WhatsApp Business templates.

Scroll for all 8

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Trengo Channels API

OPEN COLLECTION

Trengo Channels Contacts API

OPEN COLLECTION

Trengo Channels Labels and Custom Fields API

OPEN COLLECTION

Trengo Channels Messages API

OPEN COLLECTION

Trengo Channels Teams and Users API

OPEN COLLECTION

Trengo Channels Tickets API

OPEN COLLECTION

Trengo Channels Webhooks API

OPEN COLLECTION

Trengo Channels WhatsApp API

OPEN COLLECTION

Trengo API

OPEN COLLECTION

Scroll for all 9

Trengo API pricing

Prices published by Trengo, read 2026-09-20 from trengo.com/prices. A free plan or tier is listed.

Plan	Price
Boost (annual)	€ 299/month Includes: 10 users included, 6,000 conversations/year
Pro (annual)	€ 499/month Includes: 20 users included, 18,000 conversations/year
Boost (monthly)	€ 349/month Includes: 10 users included, 500 conversations/month
Pro (monthly)	€ 599/month Includes: 20 users included, 1,500 conversations/month
Enterprise	Custom Includes: Custom users included, Custom conversations
Conversations with an AI surcharge (monthly)	€ 0.30 per conversation
Conversations with an AI surcharge (yearly)	€ 0.25 per conversation
All WhatsApp service conversations	Free

Plan details, limits and sources →

Rate limits

Requests Per Minute (per token): 120 requests

Compiled by API Evangelist, not yet checked against Trengo's documentation. Rate-limit details →

Pricing Plans 2

Published pricing tiers and plan structures.

Trengo Plans Pricing

8 plans

PLANS

Trengo Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Trengo Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Trengo Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Trengo API Rules

61 rules · 57 error-severity 2 warn-severity 2 info-severity

SPECTRAL

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Trengo Authentication

http · 1 scheme

SECURITY

Trengo Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Trengo Vulnerability Disclosure

no policy recorded

SECURITY

Trengo Trust Center

PCI DSS, GDPR

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Trengo Agentic Access

21 operations · 15 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: trengo
url: https://raw.githubusercontent.com/api-evangelist/trengo/refs/heads/main/apis.yml
name: Trengo
kind: company
description: Trengo is an omnichannel customer-engagement and shared-inbox platform that unifies email, WhatsApp, live chat,
  voice, SMS, and social channels into one team inbox with AI agents. The Trengo REST API (app.trengo.com/api/v2) lets you
  create and manage tickets, contacts, messages, channels, teams, users, labels, custom fields, webhooks, and WhatsApp templates
  programmatically with Bearer-token authentication.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/trengo.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Customer Engagement
- Omnichannel
- Shared Inbox
- Messaging
- WhatsApp
- Customer Service
tags_raw:
- Customer Engagement
- Omnichannel
- Shared Inbox
- Messaging
- WhatsApp
- Customer Support
- Customer-Support
created: '2026-06-20'
modified: '2026-06-20'
specificationVersion: '0.23'
apis:
- aid: trengo:trengo-channels-api
  name: Trengo Channels API
  description: List connected channels.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Channels
  properties:
  - type: OpenAPI
    url: openapi/trengo-channels-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-contacts-api
  name: Trengo Contacts API
  description: Manage contacts and contact profiles.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Contacts
  properties:
  - type: OpenAPI
    url: openapi/trengo-contacts-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-labels-and-custom-fields-api
  name: Trengo Labels and Custom Fields API
  description: Manage labels and custom fields.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Labels and Custom Fields
  properties:
  - type: OpenAPI
    url: openapi/trengo-labels-and-custom-fields-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-messages-api
  name: Trengo Messages API
  description: List and send text and media messages on a ticket.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Message
  tags_raw:
  - Messages
  properties:
  - type: OpenAPI
    url: openapi/trengo-messages-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-teams-and-users-api
  name: Trengo Teams and Users API
  description: Manage teams and list agents.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Teams and Users
  properties:
  - type: OpenAPI
    url: openapi/trengo-teams-and-users-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-tickets-api
  name: Trengo Tickets API
  description: Create, list, assign, label, and close conversations.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Ticketing
  tags_raw:
  - Tickets
  properties:
  - type: OpenAPI
    url: openapi/trengo-tickets-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-webhooks-api
  name: Trengo Webhooks API
  description: Register and manage webhook subscriptions.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/trengo-webhooks-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
- aid: trengo:trengo-whats-app-api
  name: Trengo Whats App API
  description: Send approved WhatsApp Business templates.
  humanURL: https://developers.trengo.com/reference/list-all-tickets
  baseURL: https://app.trengo.com/api/v2
  tags:
  - WhatsApp
  tags_raw:
  - Whats App
  properties:
  - type: OpenAPI
    url: openapi/trengo-whats-app-api-openapi.yml
  - type: Documentation
    url: https://developers.trengo.com/docs/welcome
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-tickets
  - type: PostmanCollection
    url: collections/trengo.postman_collection.json
  - type: OpenCollection
    url: collections/trengo.opencollection.json
  - type: APIReference
    url: https://developers.trengo.com/reference
  - type: APIReference
    url: https://developers.trengo.com/reference/list-all-messages
  - type: Documentation
    url: https://developers.trengo.com/docs/configuration
common:
- type: Pricing
  url: https://trengo.com/prices
- type: CapabilityMap
  url: capabilities/trengo-capability-edges.yml
  name: Trengo Business Capability Map
- type: AgenticAccess
  url: agentic-access/trengo-agentic-access.yml
- type: TrustCenter
  url: security/trengo-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/trengo-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/trengo-domain-security.yml
- type: Authentication
  url: authentication/trengo-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/trengo
- type: Website
  url: https://trengo.com/
- type: Documentation
  url: https://developers.trengo.com/docs/welcome
- type: Plans
  url: plans/trengo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/trengo-rate-limits.yml
- type: FinOps
  url: finops/trengo-finops.yml
- url: https://trengo.com/blog
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Trengo API — frequently asked questions

Does Trengo have an API?

Yes. APIs.io lists 8 APIs from Trengo, including Trengo Channels API, Trengo Contacts API and Trengo Labels and Custom Fields API, and 5 more.

Is there an OpenAPI specification for the Trengo API?

Yes. APIs.io indexes 8 OpenAPI specifications for Trengo, each linked for download from this page.

How do I authenticate with the Trengo API?

Trengo uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Trengo Authentication.

How much does the Trengo API cost?

Trengo publishes its prices; its Boost (annual) plan is € 299/month as of 2026-09-20. APIs.io lists 8 pricing plans for Trengo, with each plan's price, limits and inclusions under Pricing on this page.

Is the Trengo API ready for AI agents?

Trengo has a Kin Score of 37.5 out of 100 (thin) and an Agent Readiness score of 24.8 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/trengo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/trengo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/trengo/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.