Zammad

Zammad provides an AI‑powered service platform for customer support, helpdesk and IT operations. It centralises communication across channels, adds AI‑driven efficiency, and offers a free trial for teams of any size. The platform combines human expertise with automation to deliver seamless support experiences.

Zammad is listed with 1 API on the APIs.io network. Tagged areas include Company, Support, Helpdesk, AI, and Customer-Service.

The Zammad catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Zammad’s developer surface includes support, changelog, documentation, engineering blog, pricing, getting-started guide, and 18 more developer resources.

🌐 Visit website📡 Profile data on GitHub
40.6/100 developing Agent 24/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →
1 API
CompanySupportHelpdeskAICustomer-ServicePlatform

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0
Composite quality — 40.6/100 · developing
Contract Quality 4.7 / 21
Developer Ergonomics 6.5 / 17
Access Clarity 10.7 / 17
Operational Transparency 4.4 / 11
Contract Governance 2.2 / 10
Discoverability 5.0 / 9
Regulatory Posture 3.4 / 15
Agent readiness — 24/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 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 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 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
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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Zammad It updates itself when the score changes. Paste this where you link to your API docs: 
<a href="https://apis.io/providers/zammad/"><img src="https://apis.io/badge/zammad/card.svg" alt="Zammad 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
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • 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)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
9 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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/zammad/apis.yml: open an issue on github.com/api-evangelist/zammad 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 →

APIs 1

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

Zammad API

Zammad API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider's own document.

Pricing Plans 1

Published pricing tiers and plan structures.

Zammad Plans Pricing

9 plans

PLANS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Zammad Context

3 classes · 21 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Zammad API Rules

10 rules · 8 errors 1 warnings 1 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

GetApiV1TicketsSearchResponse

14 properties

JSON SCHEMA

PostApiV1CtiInstanceRequest

6 properties

JSON SCHEMA

PostApiV1CtiInstanceResponse

7 properties

JSON SCHEMA

Security Posture 2

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

Zammad Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Zammad Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral
Spectral
 JSONLD
JSONLD
 Vocabulary
Vocabulary
 DataModel
DataModel
 Conformance
Conformance
 Webhooks
Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Security
Security
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Plans
Plans
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Pricing
Pricing

Company 3

The organization behind the API

Newsroom
Newsroom
 Website
Website
 Blog
Blog

Other 2

Properties that don't map to a standard resource type

Vendors
Vendors
 Hosts
Hosts

Source (apis.yml)

apis.yml Raw ↑ 
aid: zammad
name: Zammad
image: https://zammad.com/media/assets/assets/images/1601169394-1792392622/sharing-preview-1200x630-crop-q85.jpg
description: Zammad provides an AI‑powered service platform for customer support, helpdesk and IT operations. It centralises
  communication across channels, adds AI‑driven efficiency, and offers a free trial for teams of any size. The platform combines
  human expertise with automation to deliver seamless support experiences.
url: https://raw.githubusercontent.com/api-evangelist/zammad/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Company
- Support
- Helpdesk
- AI
- Customer-Service
- Platform
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Vendors
  url: vendors/zammad-vendors.yml
- type: Plans
  url: plans/zammad-plans-pricing.yml
- type: Spectral
  url: rules/zammad-rules.yml
- type: JSONLD
  url: json-ld/zammad-context.jsonld
- type: Vocabulary
  url: vocabulary/zammad-vocabulary.yml
- type: DataModel
  url: data-model/zammad-data-model.yml
- type: Conformance
  url: conformance/zammad-conformance.yml
- type: Hosts
  url: hosts/zammad-hosts.yml
- type: Webhooks
  url: https://zammad.com/en/product/features/webhooks
- type: TermsOfService
  url: https://zammad.com/en/company/terms
- type: Support
  url: https://support.zammad.com/help/en-us/3
- type: Security
  url: https://zammad.com/en/product/features/security
- type: PrivacyPolicy
  url: https://zammad.com/en/company/privacy
- type: Newsroom
  url: https://zammad.com/en/company/press
- type: GitHubOrganization
  url: https://github.com/zammad
- type: ChangeLog
  url: https://zammad.com/en/product/releases
- type: Documentation
  url: https://docs.zammad.com/
- type: DeveloperPortal
  url: https://docs.zammad.org/en/latest/
- type: VulnerabilityDisclosure
  url: security/zammad-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/zammad-domain-security.yml
- type: Website
  url: https://zammad.com/
- type: Blog
  url: https://zammad.com/en/blog
- type: Pricing
  url: https://zammad.com/en/pricing
- type: GettingStarted
  url: https://zammad.com/en/getting-started
apis:
- aid: zammad:zammad-api
  name: Zammad API
  description: 'Zammad API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist
    (2026-10-28); not the provider''s own document.'
  humanURL: https://docs.zammad.org/en/latest/api/intro.html
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/zammad-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/zammad-get-api-v1-tickets-search-response-schema.json
  - type: JSONSchema
    url: json-schema/zammad-post-api-v1-cti-instance-response-schema.json
  - type: JSONSchema
    url: json-schema/zammad-post-api-v1-cti-instance-request-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: No OpenAPI, AsyncAPI, GraphQL, gRPC or WSDL contracts were found; the API documentation pages return 404 for spec
    URLs.
  evidence:
  - url: https://api.zammad.com/openapi.json
    status: 404
  - url: https://docs.zammad.org/en/latest/api/
    status: 404
  checked: '2026-10-28'
x-submission-probe: 302 https://zammad.com/en, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 19
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Zammad API — frequently asked questions

Does Zammad have an API?

Yes. APIs.io lists 1 API from Zammad, including Zammad API.

Is there an OpenAPI specification for the Zammad API?

Yes. APIs.io indexes 1 OpenAPI specification for Zammad, each linked for download from this page.

How do I authenticate with the Zammad API?

Zammad uses bearer-token authentication.

How much does the Zammad API cost?

APIs.io lists 9 pricing plans for Zammad, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the Zammad API ready for AI agents?

Zammad has a Kin Score of 40.6 out of 100 (developing) and an Agent Readiness score of 23.5 (agent-aware), scored by API Evangelist on 2026-10-31.

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/zammad"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/zammad/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/zammad/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.