We have prepared a dictionary for developers in English, Spanish and Portuguese with most common Kommo terms that is highly recommedned to use when creating an integration!
The maximum number of sources per integration changed from 50 to 100.
We've added a bunch of new parameters and descriptions to our developer guides and references.
- Added information about parameter List Message in webhooks in the Chats API.
"message":
{
"id": "0371a0ff-b78a-4c7b-8538-a7d547e10692",
"type": "text",
"text": "Lead #15926745 Message text",
"markup": {
"list_message": {
"header": "What type of service do you want to receive?",
"body": "Please select one of the answer options from the menu by clicking the button below.",
"footer": "Sincerely, Test Company",
"button": "Services",
"sections": [
{
"title": "Available services",
"rows": [
{
"callback_data": "vG9ujre8N7",
"title": "Service 1",
"description": "Service 1 description"
}
]
}
]
}
}
}
- Added
tags_to_add
andtags_to_delete
keys to lead/contact/company creation and editing via API. You can pass tags to add and delete using the keys. These keys can be useful for avoiding collisions when multiple integrations can simultaneously change an entity. - Updated Permissions article: X-Context-User-ID header is introduced. Full access term is specified.
- Updated Sources API article: added the
waba
parameter. Updated the Webhooks API article: added a new type add_chat_template_review hook. - Added
with
parameterdescriptions
in API methods of stages. Added the ability to add stage descriptions in API methods for adding stages. Added the ability to add/edit/delete stage descriptions in API methods for editing stages.
"descriptions": [
{
"level": "newbie",
"description": "Stage description"
}
]
- Added
with
parametersuser_rank
,amojo_id
,uuid
in API methods of users . - Added description of parameters that need to be passed when using
reply_to
in sending/importing messages in Chats API section. Added description of parameters that come in webhooks when replying to a message (reply_to
). - Described
call_responsible
parameter in adding calls via API. Addedcall_responsible
parameter for adding an incoming lead of sip type (call) via API. - Added description of using files from the File API in custom fields.
- Added
is_need_to_trigger_digital_pipeline
parameter when [adding notes](Added is_need_to_trigger_digital_pipeline parameter when adding notes to the Notes API.) via API. - Added a list of available tag colors for leads. Tag color is now returned in leads.
- Added
_embedded[source][external_id]
and_embedded[source][type]
parameters to the methods for adding leads.
Private integration can be created with just one click!
But be aware that all the scopes will be checked, your integration name will be Integration name, and your integration description will be Description.
- We've added three articles about Digital Pipeline.
- A new rule has been added regarding widget naming:
When naming a widget, avoid using words that exceed 19 characters. Also, if you include symbols between words without spaces, they will be treated as a single word. To avoid this issue, make sure to add spaces before or after any symbols if you need to use them in the widget name.
We've added user roles endpoints , an article about limitations , and an article about Website Chat Button .
You can learn how to enhance the appearance of your widget in the dark theme and gain a better understanding of webhooks.
The whole Go to Marketplace section was added.