POST /intents/search endpoint
by intent title, ID, relevance, the creation date or the date it was last updated.
PUT /forms/{formId}
endpoint’s endFormMessage parameter to customize end form messages shown in Chatbot conversations.
POST intents/search
endpoint that allows to search intents programmatically.
GET /contents/{contentId}
, POST /contents
and PATCH /contents/{contentId}
endpoints, and added the POST /intents
, GET /intents/{intentId}
and PATCH /intents/{intentId}
endpoints instead.
POST /intents
and PATCH /intents/{intentId}
endpoints.
PATCH contents/{id}
with an empty payload.
We created the following new endpoints to manage intent attributes:
createAttribute
getAttributes
getAttribute
getAttributesGroup
editAttribute
createAttributesGroup
editAttributesGroup
addAttributeToAttributesGroup
When a direct call name is set for an intent, a validation now takes place to check whether the direct call is already being used by another intent. If the direct call is already being used, an error is now returned that shows the IDs of the conflicting intents.
We now allow to set webhook private urls. To activate the ability to enable and disable private URLs, the user must have the CHATBOT_WEBHOOKS_ENABLE_PRIVATE_URLS right found within the CONTENTS section activated.
New Feature: The Chatbot Editor API now includes endpoints for managing variables. See Chatbot Editor API Routes for further info.
We updated the Chatbot Editor API documentation to use terms like “intents”, “folders”, “data fields”, etc. that correspond to the new intent editor wherever possible.
POST /publication
that allows to publish programmatically an instance to Test and/or Production.
/actions
endpoints. These endpoints allow to manage actions programmatically.