Kommo Typing API

The Typing API from Kommo — 1 operation(s) for typing.

GitHub OpenAPI

Operations 1

POST /{scope_id}/typing Transfer typing information #

Specifications

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/kommo:kommo-typing-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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

kommo-typing-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: chats-api Typing API
  version: '1.0'
servers:
- url: https://amojo.kommo.com/v2/origin/custom/
security:
- {}
tags:
- name: Typing
paths:
  /{scope_id}/typing:
    post:
      summary: Transfer typing information
      description: The method provides transferring information that the client is currently typing something in the messenger. The information will be displayed in Kommo interface.
      operationId: typing-info
      parameters:
      - name: scope_id
        in: path
        description: Get the scope ID in the step 2
        schema:
          type: string
        required: true
      - name: Content-Type
        in: header
        description: Request data type. Currently, only application/json is supported.
        schema:
          type: string
          enum:
          - application/json
      - name: Date
        in: header
        description: Date and time when the request was generated. The signature will be valid for 15 minutes from this Date. The date should be in the format “Thu, 01 Jan 2023 12:00:00 +0000” (RFC2822)
        schema:
          type: string
      - name: Content-MD5
        in: header
        description: For the request body, it is necessary to calculate the MD5 hash and indicate it in the header in lowercase. At the same time, it is important to keep in mind that the request body is calculated as a stream of bytes without considering the end of JSON markup, and if there are “\n” or spaces at the end, they will also be taken into account. For GET requests, MD5 must also be calculated. Even if nothing is passed in the request body, MD5 will be obtained from an empty string.
        schema:
          type: string
      - name: X-Signature
        in: header
        description: Signature of the request as a string. It is formed from the name of the method (GET/POST) in uppercase, with the values of the headers concatenated by “\n”. Header values ​​come in a specific order. If there is no header, an empty string is specified instead. Next, add the requested path from the URL without the protocol and domain (without GET parameters) to the line. The resulting string is calculated using HMAC-SHA1, and as a secret, we use the channel secret obtained during registration. The resulting hash in lowercase is indicated in the X-Signature header.
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                conversation_id:
                  type: string
                  description: Chat ID on the integration side
                sender:
                  type: object
                  description: User ID on the integration side
                  properties:
                    id:
                      type: string
                      description: User ID on the integration side
                duration_ms:
                  type: integer
                  description: Optional. Print time duration in milliseconds. Default is 5000 ms.
                  default: '5000'
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                conversation_id:
                  type: string
                  description: Chat ID on the integration side
                sender:
                  type: object
                  description: User ID on the integration side
                  properties:
                    id:
                      type: string
                      description: User ID on the integration side
          multipart/form-data:
            schema:
              type: object
              properties:
                conversation_id:
                  type: string
                  description: Chat ID on the integration side
                sender:
                  type: object
                  description: User ID on the integration side
                  properties:
                    id:
                      type: string
                      description: User ID on the integration side
          application/hal+json:
            schema:
              type: object
              properties:
                conversation_id:
                  type: string
                  description: Chat ID on the integration side
                sender:
                  type: object
                  description: User ID on the integration side
                  properties:
                    id:
                      type: string
                      description: User ID on the integration side
            examples:
              Request Example:
                value:
                  conversation_id: XXXXXX-80c5-403d-93d9-bada6302810f
                  sender:
                    id: XXXXXXXX-4f66-46ff-b06f-d245fca1af0a
      responses:
        '204':
          description: '204'
          content:
            application/json:
              examples:
                Event accepted, the typing status appears:
                  value: '{}'
              schema:
                type: object
                properties: {}
        '403':
          description: '403'
          content:
            application/json:
              examples:
                Request signature is incorrect:
                  value: '{}'
              schema:
                type: object
                properties: {}
        '404':
          description: '404'
          content:
            text/plain:
              examples:
                Incorrect data was passed. Details are available in the response.:
                  value: ''
      deprecated: false
      tags:
      - Typing
x-readme-fauxas: true
x-provenance:
  method: searched
  source: https://developers.kommo.com/reference
  harvested: '2026-11-15'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:
  - https://developers.kommo.com/reference/chat-history.md
  - https://developers.kommo.com/reference/connect-channel.md
  - https://developers.kommo.com/reference/create-chat.md
  - https://developers.kommo.com/reference/disconnect-channel.md
  - https://developers.kommo.com/reference/send-import-messages.md
  - https://developers.kommo.com/reference/send-reactions.md
  - https://developers.kommo.com/reference/typing-info.md
  - https://developers.kommo.com/reference/update-delivery-status.md
  - https://es-developers.kommo.com/reference/actualizar-el-estado-de-entrega-del-mensaje.md
  - https://es-developers.kommo.com/reference/desconectar-el-canal-de-chat.md
  - https://es-developers.kommo.com/reference/enviar-o-retirar-reacciones.md
  - https://es-developers.kommo.com/reference/obtener-el-historial-del-chat.md
  - https://es-developers.kommo.com/reference/paso-2-conectar-canal-de-chat.md
  - https://es-developers.kommo.com/reference/paso-3-crear-nuevo-chat.md
  - https://es-developers.kommo.com/reference/paso-5-enviar-recibir-o-importar-mensajes.md
  - https://pt-developers.kommo.com/reference/atualizar-status-de-entrega-da-mensagem.md
  - https://pt-developers.kommo.com/reference/conectar-canal-do-chat.md
  - https://pt-developers.kommo.com/reference/criar-novo-chat.md
  - https://pt-developers.kommo.com/reference/desconectar-canal-de-chat.md
  - https://pt-developers.kommo.com/reference/enviar-receber-ou-importar-mensagens.md
  - https://pt-developers.kommo.com/reference/obter-chats-de-contato.md
  merge:
    pages: 21
    deduped: 0
    conflicts_kept_first: 5