Zammad

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.

GitHub OpenAPI

Operations 3

GET / GET / #
POST /api/v1/cti/{instance} POST /api/v1/cti/{instance} #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/zammad/openapi/_ae-authored/zammad-openapi-generated.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/zammad/json-schema/zammad-get-api-v1-tickets-search-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/zammad/json-schema/zammad-post-api-v1-cti-instance-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/zammad/json-schema/zammad-post-api-v1-cti-instance-request-schema.json

Other Resources

🔗
APIsJSON
https://artifacts.apis.io/zammad/apis.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/zammad:zammad-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

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.

OpenAPI Specification

zammad-openapi-generated.yml Raw ↑ 
openapi: 3.1.0
info:
  title: Zammad API
  version: '2026-10-28'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-28: 3 operation(s) read from 4 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Zammad has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 2
    documentation: 1
    pages-with-code: 4
    pages-read: 4
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-28'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://docs.zammad.org/en/latest/api/intro.html
  - https://docs.zammad.org/en/latest/api/generic-cti/answer-event.html
  - https://docs.zammad.org/en/latest/api/generic-cti/newcall-event.html
  - https://docs.zammad.org/en/latest/api/generic-cti/hangup-event.html
paths:
  /:
    get:
      operationId: get
      tags:
      - Api
      summary: GET /
      x-source: https://docs.zammad.org/en/latest/api/intro.html
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -H \"Authorization: Token token={your_token}\" https://{fqdn} / {endpoint} \n OAuth2 (token access) \n The token must be\
          \ provided as HTTP header in your calls. \n This allows 3rd party applications to authenticate against Zammad. "
  /api/v1/cti/{instance}:
    post:
      operationId: post_api_v1_cti_instance
      tags:
      - Api
      summary: POST /api/v1/cti/{instance}
      x-source: https://docs.zammad.org/en/latest/api/generic-cti/answer-event.html
      parameters:
      - name: instance
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiV1CtiInstanceRequest'
      responses:
        '201':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostApiV1CtiInstanceResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --request POST 'https://{FQDN-Zammad}/api/v1/cti/{instance specific token}'  --header 'Content-Type: application/json'\
          \  --data-raw '{ \n \"event\": \"answer\", \n \"from\": \"493023125741\", \n \"to\": \"492214710334\", \n \"direction\": \"out\", \n\
          \ \"callId\": \"9f1840cb-8be9-4d3a-8200-3da2937085f0\", \n \"caller\": \"Christopher Miller\" \n }' \n Inbound Payload: \n { \n \"event\"\
          \ : \"answer\" , \n \"from\" : \"493023125741\" , \n \"t"
  /api/v1/tickets/search:
    get:
      operationId: get_api_v1_tickets_search
      tags:
      - Api
      summary: Introduction — Zammad System Documentation
      x-source: https://docs.zammad.org/en/latest/api/intro.html
      parameters:
      - name: query
        in: query
        required: true
        schema:
          type: string
        description: Search term
      - name: expand
        in: query
        required: false
        schema:
          type: boolean
        description: If true, expands related objects
      - name: full
        in: query
        required: false
        schema:
          type: boolean
        description: If true, returns full assets payload
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetApiV1TicketsSearchResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    PostApiV1CtiInstanceRequest:
      type: object
      properties:
        event:
          type: string
        from:
          type: string
        to:
          type: string
        direction:
          type: string
        callId:
          type: string
        caller:
          type: string
    PostApiV1CtiInstanceResponse:
      type: object
      properties:
        event:
          type: string
        from:
          type: string
        to:
          type: string
        direction:
          type: string
        callId:
          type: string
        answeringNumber:
          type: string
        caller:
          type: array
          items:
            type: string
    GetApiV1TicketsSearchResponse:
      type: object
      properties:
        id:
          type: integer
        group_id:
          type: integer
        priority_id:
          type: integer
        state_id:
          type: integer
        organization_id:
          type: integer
        number:
          type: string
        title:
          type: string
        owner_id:
          type: integer
        customer_id:
          type: integer
        note:
          type: string
        article_count:
          type: integer
        preferences:
          type: object
        created_at:
          type: string
          description: ISO8601 timestamp
        updated_at:
          type: string
          description: ISO8601 timestamp
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: Authorization
security:
- apiKey: []
tags:
- name: Api