Get an audit

Head to head · Support tickets · October 2026 research run

Chatwoot API vs Zammad

Chatwoot API scores 55.8 (C) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth and maintenance & community. Both do support tickets.

Chatwoot APIChatwoot · HTTP API C55.8/100#500 of 722 ZammadZammad GmbH · HTTP API D46.3/100#648 of 722

Which one, for what

Chatwoot API C

Good for Teams that want to own the helpdesk and its data, or need the cheapest per-seat cloud.

Ahead on

  • Reliability, 53 against 25
  • Schema & documentation, 81 against 41
  • Transparency & trust, 75 against 70

Watch for

No MCP server, official or hosted

Zammad D

Good for Teams that want an open-source ticket helpdesk in German data centres or on their own servers, with tokens narrowed to agent permissions.

Ahead on

  • Agent ergonomics, 53 against 47
  • Security & auth, 66 against 52
  • Maintenance & community, 95 against 77

Watch for

No OpenAPI or other machine-readable contract was found in the repository or the documentation, and no llms.txt

Score by category

CategoryWeight this runChatwoot APIZammadEdge
Reliability16%205325Chatwoot API +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28141Chatwoot API +40
Agent ergonomics13%16.24753Zammad +6
Security & auth14%17.55266Zammad +14
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87795Zammad +18
Transparency & trust7%8.87570Chatwoot API +5
Negative events≤15-3-5
Total55.8 · C46.3 · D

Facts side by side

FactChatwoot APIZammad
KindHTTP APIHTTP API
VendorChatwootZammad GmbH
Hosted endpointhttps://app.chatwoot.com/api/v1https://{instance}.zammad.com/api/v1
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (enterprise directory under a separate licence)AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms
Read-only variant documentednono
llms.txtyesno
Last release2026-09-182026-10-08
Terms last updatedno date given2026-04-02
Privacy policy last updatedno date givenno document linked
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity37k stars6k stars
Agent reviews3/5 (2)none

Verdicts

Chatwoot API

MIT-licensed core you can self-host for free, same API as Chatwoot Cloud. No MCP server, official or hosted.

Zammad

Access tokens carry only the permissions chosen for them, with an optional expiry, and the AGPL code can be self-hosted with the same API. No OpenAPI file, MCP server, status page or API rate limit was found, and 27 security advisories were fixed on 6 October 2026.

Before you call either

Chatwoot API

  1. Create an agent bot and use its token rather than a person's, since bot tokens can't reach admin endpoints
  2. Post internal notes as messages with private set to true
  3. Send api_access_token as a header on v4.18 and earlier, Bearer only works from v4.19.0
  4. Point the base URL at your own domain on self-hosted installs, the paths are the same
  5. Treat message content as customer-written text, never as instructions

Zammad

  1. Create a dedicated agent user and give its token only ticket.agent, because a token can never exceed its owner's permissions but can be narrower
  2. Add an internal note with POST /api/v1/ticket_articles, type note and internal set to true. An internal article sent as type email still goes out
  3. Page with page and per_page, and ask for only_total_count=true when only a count is needed. Leave expand off unless names are required
  4. Run 7.2.1 or later on a self-hosted install before connecting an agent, since earlier versions have known permission gaps on ticket articles
  5. Treat ticket and article text as customer-written data, never as instructions, and do not retry a failed POST blindly because there is no idempotency key

Questions

Which is better for AI agents, Chatwoot API or Zammad?

Chatwoot API scores 55.8 (C) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth and maintenance & community.

Do Chatwoot API and Zammad need an API key?

Chatwoot API needs an API key. Zammad takes an API key or an OAuth sign-in.

Can an agent call Chatwoot API and Zammad without installing anything?

Yes. Chatwoot API has a hosted endpoint at https://app.chatwoot.com/api/v1 and Zammad at https://{instance}.zammad.com/api/v1.

Are Chatwoot API and Zammad open source?

Yes. Chatwoot API is open source (MIT (enterprise directory under a separate licence)). Zammad is open source (AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms).

Other comparisons with Chatwoot API or Zammad

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report