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/comunix:comunix-incidents-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

openapi: 3.2.0
info:
  title: Comunix Incidents API
  version: '2026-10-10'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-10: 16 operation(s) read from 7 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Comunix has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 9
    documentation: 7
    pages-with-code: 6
    pages-read: 7
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-10'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://developer.zendesk.com/documentation/developer-tools/working-with-the-zendesk-apis/exploring-zendesk-apis-with-postman
  - https://developer.zendesk.com/documentation/ticketing/events/getting-started-with-events
  - https://developer.zendesk.com/documentation/ticketing/profiles/getting-started-with-profiles
  - https://developer.zendesk.com/documentation/custom-data/custom-objects/getting-started-with-custom-objects
  - https://developer.zendesk.com/documentation/developer-tools/getting-started/getting-a-trial-or-sponsored-account-for-development
  - https://developer.zendesk.com/api-reference/ticketing/introduction
  - https://developer.zendesk.com/api-reference/status_api/status_api
servers:
- url: https://status.zendesk.com
tags:
- name: Incidents
paths:
  /api/incidents:
    get:
      operationId: get_api_incidents
      tags:
      - Incidents
      summary: GET /api/incidents
      x-source: https://developer.zendesk.com/api-reference/status_api/status_api
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetApiIncidentsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl https://status.zendesk.com/api/incidents/ { incident_id } } ?include [ ] = incident_services,incident_updates,incident_services.service \n Go \n import ( \"fmt\" \"io\" \"net/http\" ) \n func main ( ) { url := \"https://support.zendesk.com/api/incidents/247?include[]=incident_updates%2Cincident_services%2Cincident_services.service\" method := \"GET\" req , err := http . NewRequest ( method , url , nil ) \n"
  /api/incidents/:
    get:
      operationId: getApiIncidents
      tags:
      - Incidents
      summary: List Active Incidents
      x-source: https://developer.zendesk.com/api-reference/status_api/status_api
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetApiIncidentsResponse2'
      x-evidence:
        kind: documentation
      x-operation-id-source: normalized
      x-operation-id-original: get_api_incidents
components:
  schemas:
    GetApiIncidentsResponse2:
      type: object
      properties:
        data:
          type: array
          description: Primary incident data with attributes and relationships included
        included:
          type: array
          description: Related resources (incident_updates, incident_services, and services)
    GetApiIncidentsResponse:
      type: object
      properties:
        degradation:
          type: boolean
        impact:
          type: string
        outage:
          type: boolean
        postmortem:
          type: string
        resolved_at:
          type:
          - string
          - 'null'
        started_at:
          type: string
          format: date-time
        status:
          type: string
        title:
          type: string