Modification for chat closure #
Modification for chat closure 
- From this version onwards, each chat will not be closed based on the time elapsed since its creation, but rather from the last message sent. This means that if there is inactivity in the chat since the last message sent, it will be closed according to the time configured in the timeout.
- Remember that in the general configuration section of web chats, the timeout or inactivity closure time is set.
- The minimum time is 15 minutes and the maximum is 1380 (23 hours).
- Note: The inactivity time applies to both the agent and the customer.
New possible response when consuming an API #
- The following response has been incorporated when consuming an API if the server is performing backups.
- { “code”: “403”, “error”: “Forbidden”, “msg”: “The APIs cannot be consumed at this time, try again later.” }
- This response ensures control over API consumption when the server is busy creating backups.
New API to get information about audio storage #
- The new API “15. Total Audio Storage” allows you to obtain the total size in gigabytes or terabytes that the operation has in audio storage.
- Thanks to this new feature, you can know the total weight of the operation related to the audios and then take actions on the operation in relation to this matter.
- To go to the official API documentation, click here.
- It is also found in the public Postman collection. Click here to go. It is located within the Information APIs group.
