Kommo Events API
The Events API from Kommo — 4 operation(s) for events.
The Events API from Kommo — 4 operation(s) for events.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/kommo:kommo-events-api"
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.
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: 3.2.0
info:
title: Kommo Events API
version: '1.0'
description: 'Operations tagged Events across 2 of this provider''s published API definitions: kommo-api-openapi.yml, kommo-api-references-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://{subdominio}.kommo.com
variables:
subdominio:
default: subdominio
- url: https://{subdomain}.kommo.com
variables:
subdomain:
default: subdomain
security:
- sec0: []
tags:
- name: Events
paths:
/api/v4/events:
get:
summary: Lista de eventos
description: Este método permite obtener la lista de eventos.
operationId: lista-de-eventos
parameters:
- name: with
in: query
description: Este parámetro acepta una cadena que puede consistir en varios valores separados por comas. Puedes encontrarlos en la tabla WITH
schema:
type: string
- name: page
in: query
description: Una página de los datos de la respuesta
schema:
type: integer
format: int32
- name: limit
in: query
description: 'El número de entidades retornadas en la respuesta de una solicitud (límite: 250)'
schema:
type: integer
format: int32
- name: filter[id]
in: query
description: Filtrar por el ID del evento. Puedes pasar un solo ID o varios IDs separados por comas
schema:
type: string
- name: filter[created_at][from]
in: query
description: Filtrar por la fecha de creación del evento. Se puede pasar una marca de tiempo; en ese caso, se retornarán los eventos creados después del valor de la marca de tiempo
schema:
type: integer
format: int32
- name: filter[created_at][to]
in: query
description: Filtrar por la fecha de creación del evento. Se puede pasar una marca de tiempo, en ese caso, se retornarán los eventos creados antes del valor de la marca de tiempo
schema:
type: integer
format: int32
- name: filter[created_by]
in: query
description: Filtrar por usuarios. Se puede pasar una cadena de hasta 10 IDs de usuarios, separados por coma
schema:
type: string
- name: filter[entity]
in: query
description: 'Filtrar por el tipo de entidad, pasado como una cadena de entidades separadas por coma. Parámetros disponibles: lead, contact, company, task, catalog_{LIST_ID}'
schema:
type: string
- name: filter[entity_id]
in: query
description: Filtrar por el ID de la entidad. Se puede pasar una cadena con hasta 10 IDs separados por comas. Pasa solo una entidad para filtrar[entity] para utilizar este filtro
schema:
type: string
- name: filter[type]
in: query
description: 'Filtrar por el tipo de evento. Los tipos se pasan como una cadena de tipos separados por comas. Puedes encontrar los tipos de evento aquí: https://es-developers.kommo.com/reference/tipos-de-eventos'
schema:
type: string
responses:
'200':
description: '200'
content:
application/json:
examples:
Solicitud exitosa:
value: "{\n \"_page\": 1,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/events?page=1&limit=250\"\n },\n \"next\": {\n \"href\": \"https://example.kommo.com/api/v4/events?page=2&limit=250\"\n }\n },\n \"_embedded\": {\n \"events\": [\n {\n \"id\": \"aaabbbbcccc1234567\",\n \"type\": \"lead_status_changed\",\n \"entity_id\": XXXXXX,\n \"entity_type\": \"lead\",\n \"created_by\": YYYYYYY,\n \"created_at\": 1665064411,\n \"value_after\": [\n {\n \"lead_status\": {\n \"id\": ZZZZZZZ,\n \"pipeline_id\": 123XYZ\n }\n }\n ],\n \"value_before\": [\n {\n \"lead_status\": {\n \"id\": 321XYZ,\n \"pipeline_id\": XXXXXX\n }\n }\n ],\n \"account_id\": 111222333,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/events/aaabbbbcccc1234567\"\n }\n },\n \"_embedded\": {\n \"entity\": {\n \"id\": 1234567,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/leads/XXXXXX\"\n }\n }\n }\n }\n }\n ]\n }\n}"
'401':
description: '401'
content:
application/json:
examples:
El usuario no está autorizado:
value: "{\n \"title\": \"Unauthorized\",\n \"type\": \"https://httpstatus.es/401\",\n \"status\": 401,\n \"detail\": \"Nombre de usuario o contraseña incorrectos\"\n}"
schema:
type: object
properties:
title:
type: string
example: Unauthorized
type:
type: string
example: https://httpstatus.es/401
status:
type: integer
example: 401
default: 0
detail:
type: string
example: Nombre de usuario o contraseña incorrectos
'402':
description: '402'
content:
application/json:
examples:
Cuenta no pagada:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Events
servers:
- url: https://{subdominio}.kommo.com
variables:
subdominio:
default: subdominio
/api/v4/events/types:
get:
summary: Obtener tipos de eventos
description: Este método permite obtener todos los tipos de eventos disponibles.
operationId: obtener-tipos-de-eventos
parameters:
- name: language_code
in: query
description: 'Código de idioma que define el idioma de los tipos retornados. Si no se pasa ninguno, los tipos se retornarán en el idioma del usuario que realiza la solicitud. Parámetros disponibles: en, es, pt'
schema:
type: string
responses:
'200':
description: '200'
content:
application/json:
examples:
Solicitud exitosa:
value: "{\n \"_total_items\": 35,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/events/types?limit=6\"\n }\n },\n \"_embedded\": {\n \"events_types\": [\n {\n \"key\": \"lead_added\",\n \"type\": 1,\n \"lang\": \"New lead\"\n },\n {\n \"key\": \"lead_deleted\",\n \"type\": 7,\n \"lang\": \"Lead deleted\"\n },\n ...\n ]\n }\n}"
'400':
description: '400'
content:
application/json:
examples:
Datos transmitidos inválidos:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Events
servers:
- url: https://{subdominio}.kommo.com
variables:
subdominio:
default: subdominio
/api/v4/events/{id}:
get:
summary: Obtener un evento por su ID
description: Este método permite obtener los datos de un evento en particular por su ID.
operationId: obtener-evento-por-su-id
parameters:
- name: id
in: path
description: ID del evento
schema:
type: string
required: true
- name: with
in: query
description: Este parámetro toma una cadena que puede consistir en varios valores separados por comas. Puedes encontrarlos en la tabla "WITH"
schema:
type: string
responses:
'200':
description: '200'
content:
application/json:
examples:
Solicitud exitosa:
value: "{\n \"id\": \"01pz58t6p04ymgsgfbmfyfy1mf\",\n \"type\": \"lead_added\",\n \"entity_id\": 0000000,\n \"entity_type\": \"lead\",\n \"created_by\": XXXXXXX,\n \"created_at\": 1888888888,\n \"value_after\": [\n {\n \"note\": {\n \"id\": 123XXXX\n }\n }\n ],\n \"value_before\": [],\n \"account_id\": 321XXXX,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/events/01pz58t6p04ymgsgfbmfyfy1mf\"\n }\n },\n \"_embedded\": {\n \"entity\": {\n \"id\": 555XXX,\n \"_links\": {\n \"self\": {\n \"href\": \"https://example.kommo.com/api/v4/leads/0000000\"\n }\n }\n }\n }\n}"
'401':
description: '401'
content:
application/json:
examples:
El usuario no está autorizado:
value: "{\n \"title\": \"Unauthorized\",\n \"type\": \"https://httpstatus.es/401\",\n \"status\": 401,\n \"detail\": \"Nombre de usuario o contraseña incorrectos\"\n}"
schema:
type: object
properties:
title:
type: string
example: Unauthorized
type:
type: string
example: https://httpstatus.es/401
status:
type: integer
example: 401
default: 0
detail:
type: string
example: Nombre de usuario o contraseña incorrectos
'402':
description: '402'
content:
application/json:
examples:
Cuenta no pagada:
value: '{}'
schema:
type: object
properties: {}
deprecated: false
tags:
- Events
servers:
- url: https://{subdominio}.kommo.com
variables:
subdominio:
default: subdominio
/api/v2/events:
post:
description: ''
operationId: post_apiv2events
responses:
'202':
description: Accepted
content:
application/json:
examples:
Accepted:
value:
_links:
self:
href: /api/v2/events
_embedded:
items:
- element_type: 2
element_id: 21430700
uid: b9ccb0ff-c94b-4e86-87fb-adceb56af024
phone_number: '1234567890'
summary: Accepted
parameters: []
requestBody:
content:
application/json:
schema:
properties:
add:
type: array
items:
properties:
type:
type: string
description: Notification type – `phone_call`
enum:
- phone_call
phone_number:
type: string
description: The phone number to which the call is being made. Can be transmitted in any format
users:
type: array
description: ID of users for whom the notification will be sent. If this parameter is not passed, the notification will be sent to all users.
items:
type: integer
type: object
type: object
tags:
- Events
summary: Post apiv2events
x-summary-source: derived
servers:
- url: https://{subdomain}.kommo.com
variables:
subdomain:
default: subdomain
components:
securitySchemes:
sec0:
type: oauth2
flows: {}
x-refined-from:
- kommo-api-openapi.yml
- kommo-api-references-api-openapi.yml
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/ai-add-source-file.md
- https://developers.kommo.com/reference/ai-add-source-text.md
- https://developers.kommo.com/reference/ai-add-source-url.md
- https://developers.kommo.com/reference/launch-import-of-products-from-crm-to-ai.md
- https://pt-developers.kommo.com/reference/ai-add-source-file.md
- https://pt-developers.kommo.com/reference/ai-add-source-text.md
- https://pt-developers.kommo.com/reference/ai-add-source-url.md
- https://pt-developers.kommo.com/reference/launch-import-of-products-from-crm-to-ai.md
merge:
pages: 8
deduped: 7
conflicts_kept_first: 4