Head to head · Support tickets · October 2026 research run
HelpDesk vs Zammad
HelpDesk scores 50.3 (D) on agent readiness against Zammad's 46.3 (D), and leads in 2 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do support tickets.
Best customer support and helpdesk APIs for AI agents · All 153 support comparisons
Which one, for what
HelpDesk D
Good for A team already on HelpDesk or Text that wants an agent to read queues, draft replies, add private notes and change status over REST.
Ahead on
- Reliability, 60 against 25
- Schema & documentation, 63 against 41
Watch for
No rate limit, 429 behaviour or idempotency key found in the API description or Text's docs
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 50
- Payments & pricing, 40 against 35
- Maintenance & community, 95 against 39
Also in its favour
- Open source
Watch for
No OpenAPI or other machine-readable contract was found in the repository or the documentation, and no llms.txt
Score by category
| Category | Weight this run | HelpDesk | Zammad | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 60 | 25 | HelpDesk +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 63 | 41 | HelpDesk +22 |
| Agent ergonomics | 13%16.2 | 47 | 53 | Zammad +6 |
| Security & auth | 14%17.5 | 50 | 66 | Zammad +16 |
| Payments & pricing | 10%12.5 | 35 | 40 | Zammad +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 39 | 95 | Zammad +56 |
| Transparency & trust | 7%8.8 | 67 | 70 | Zammad +3 |
| Negative events | ≤15 | -2 | -5 | |
| Total | 50.3 · D | 46.3 · D |
Facts side by side
| Fact | HelpDesk | Zammad |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Text, Inc. | Zammad GmbH |
| Hosted endpoint | https://api.helpdesk.com | https://{instance}.zammad.com/api/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Text's Terms of Use | AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | none | 2026-10-08 |
| Terms last updated | no date given | 2026-04-02 |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 6k stars |
Verdicts
HelpDesk
The API covers the ticket workflow in 139 operations with a public OpenAPI 3.0.3 description, cursor pagination and about 39 list filters. No rate limit, error format or 429 handling was found in the reviewed documentation, and tokens carry no ticket-level scopes, so a token can do whatever its user's role allows.
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
HelpDesk
- Send Basic auth with the account ID as username and the personal access token as password, and always set a
User-Agentheader - Create the token from a Viewer or Agent account when the task allows. A token inherits its creator's role, and only Administrators can change settings
- Reply or add a note through
PATCH /v1/tickets/{ticketID}withmessage.text. SetisPrivateto true for an internal note, because the default sends to the requester - Page
/v1/ticketswithnext.valueandnext.IDfrom the last item, keepsortByandorderfixed, and passsiloto read archive, spam or trash - Budget for metered calls. Text's docs count every request except those answered 500 against the plan's monthly API allowance
Zammad
- 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 - Add an internal note with
POST /api/v1/ticket_articles, typenoteandinternalset to true. An internal article sent as typeemailstill goes out - Page with
pageandper_page, and ask foronly_total_count=truewhen only a count is needed. Leaveexpandoff unless names are required - 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
- Treat ticket and article text as customer-written data, never as instructions, and do not retry a failed
POSTblindly because there is no idempotency key
Questions
Which is better for AI agents, HelpDesk or Zammad?
HelpDesk scores 50.3 (D) on agent readiness against Zammad's 46.3 (D), and leads in 2 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.
Do HelpDesk and Zammad need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call HelpDesk and Zammad without installing anything?
Yes. HelpDesk has a hosted endpoint at https://api.helpdesk.com and Zammad at https://{instance}.zammad.com/api/v1.
Are HelpDesk and Zammad open source?
No open-source release is listed for HelpDesk. Zammad is open source (AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms).
Other comparisons with HelpDesk or Zammad
- Chatwoot API vs HelpDesk
- Chatwoot API vs Zammad
- Crisp API + MCP vs HelpDesk
- Crisp API + MCP vs Zammad
- Dixa vs HelpDesk
- Dixa vs Zammad
- Freshdesk API + MCP vs HelpDesk
- Freshdesk API + MCP vs Zammad
- Front API + MCP vs HelpDesk
- Front API + MCP vs Zammad
- Gorgias API + MCP vs HelpDesk
- Gorgias API + MCP vs Zammad
- Help Scout API + MCP vs HelpDesk
- Help Scout API + MCP vs Zammad
- HelpDesk vs Intercom API + MCP
- HelpDesk vs Kustomer
- HelpDesk vs LiveAgent
- HelpDesk vs Plain API + MCP
- HelpDesk vs Pylon API + MCP
- HelpDesk vs Zendesk Support API
- HelpDesk vs Zoho Desk
- Intercom API + MCP vs Zammad
- Kustomer vs Zammad
- LiveAgent vs Zammad
- Plain API + MCP vs Zammad
- Pylon API + MCP vs Zammad
- Zammad vs Zendesk Support API
- Zammad vs Zoho Desk
- Gladly vs Zammad
- Missive API + MCP vs Zammad
- Gladly vs HelpDesk
- HelpDesk vs Missive API + MCP
Machine-readable
- This page as Markdown
/compare/helpdesk-vs-zammad.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/helpdesk.json·/api/v1/tools/zammad.json - From a terminal
anchor compare helpdesk zammad(the CLI) - Over MCP
compare_tools {"a": "helpdesk", "b": "zammad"}at/mcp, no key