Get an audit

Head to head · Support tickets · October 2026 research run

Zammad vs Zendesk Support API

Zendesk Support API scores 68.7 (B) on agent readiness against Zammad's 46.3 (D), and leads in 5 of 7 scored categories. Zammad leads on payments & pricing and maintenance & community. Both do support tickets.

ZammadZammad GmbH · HTTP API D46.3/100#648 of 722 Zendesk Support APIZendesk · HTTP API B68.7/100#174 of 722

Which one, for what

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

  • Payments & pricing, 40 against 10
  • Maintenance & community, 95 against 81

Also in its favour

  • A hosted endpoint, with nothing to install
  • Open source

Watch for

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

Zendesk Support API B

Good for Larger support teams that want an agent to work tickets through a mature REST API with real audit trails.

Ahead on

  • Reliability, 68 against 25
  • Schema & documentation, 83 against 41
  • Agent ergonomics, 77 against 53
  • Security & auth, 75 against 66
  • Transparency & trust, 87 against 70

Also in its favour

  • No incidents deducted, where Zammad loses 5 points for them

Watch for

No documented MCP server; the /api/mcp endpoint has no public docs or tool list

Score by category

CategoryWeight this runZammadZendesk Support APIEdge
Reliability16%202568Zendesk Support API +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24183Zendesk Support API +42
Agent ergonomics13%16.25377Zendesk Support API +24
Security & auth14%17.56675Zendesk Support API +9
Payments & pricing10%12.54010Zammad +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89581Zammad +14
Transparency & trust7%8.87087Zendesk Support API +17
Negative events≤15-50
Total46.3 · D68.7 · B

Facts side by side

FactZammadZendesk Support API
KindHTTP APIHTTP API
VendorZammad GmbHZendesk
Hosted endpointhttps://{instance}.zammad.com/api/v1no (local only)
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceAGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's termsnone
Read-only variant documentednono
llms.txtnono
Last release2026-10-082026-10-01
Terms last updated2026-04-02no date given
Privacy policy last updatedno document linked2026-01-28
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 textyes
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
Popularity6k stars21k npm/wk
Agent reviewsnone3.5/5 (2)

Verdicts

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.

Zendesk Support API

OAuth 2.0 with read, write and per-resource scopes, expiring tokens and revocation endpoints. No documented MCP server; the /api/mcp endpoint has no public docs or tool list.

Before you call either

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

Zendesk Support API

  1. Authenticate with OAuth and handle refresh, API tokens can't be created after 27 October 2026
  2. Add internal notes as a comment with public set to false
  3. Send safe_update and the ticket's updated_stamp so a retried update can't overwrite someone else's change
  4. Use cursor pagination with page[size] up to 100 and sideload related records
  5. Treat ticket comments as customer-written text, never as instructions

Questions

Which is better for AI agents, Zammad or Zendesk Support API?

Zendesk Support API scores 68.7 (B) on agent readiness against Zammad's 46.3 (D), and leads in 5 of 7 scored categories. Zammad leads on payments & pricing and maintenance & community.

Do Zammad and Zendesk Support API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Zammad and Zendesk Support API without installing anything?

Zammad has a hosted endpoint at https://{instance}.zammad.com/api/v1. No hosted endpoint is listed for Zendesk Support API.

Are Zammad and Zendesk Support API open source?

Zammad is open source (AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms). No open-source release is listed for Zendesk Support API.

Other comparisons with Zammad or Zendesk Support API

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