Adequacy of URLs September 19, 2024 14:06 Updated Index: Correcting URLs in chatbots builder Correction of URLs in APIs URL correction when using the Teams channel URL correction when using the BlipChat channel on your own websites Access to sites with contract ID Correcting URLs in chatbots To facilitate the correction process, we will be forwarding a spreadsheet with simple information to help identify and correct. File example: Considering the example above, it is possible to extract the following information: “examplebot” is the chatbot id “https://.msging.net/commands” is the incorrect URL that has been identified and needs to be adjusted “Endpoint” is the title of the action that made the request “UserAgent” is the agent that made the request, it can be the name of the API, or tool used “Quantity” number of times the request was made in the last 24 hours With the information on where you need correction in hand, simply open the chatbot that holds the informed ID and click on Builder. Now, look for the block by searching in the magnifying glass for the url you already have and navigate to the “Actions” tab and locate the HTTP Request type action. Open the request and adjust the URL. The correct URL must use the CONTRACT ID at the beginning as the subdomain. Example: https://ID_DO_CONTRATO.http.msging.net/” and keeps the rest of the URL used, which can be the word “commands” or “messages”. Before As an example, I will be using the contract id “takenet”. The correct URL in this example looks like this: “https://takenet.http.msging.net/commands” After Correction of URLs in APIs The process of correcting URLs in APIs works exactly the same as the process for bots. Just adjust the URL to use the CONTRACT ID and point to the correct subdomain. Example: Consider that my contract is called “takenet”, and my API uses the address “https://msging.net/commands”. So, the correct URL to use should be “https://takenet.http.msging.net/commands”. URL correction when using the Teams channel For customers using the Teams channel, it is necessary to check the application configuration to check and, if necessary, correct the use of the URL. To validate the URL, first open Teams and look for the Developer Portal app in the left side corner. After opening the Developer Portal, access the “Tools” tab, then access “Bot Management” and select the bot you use in your Teams application. Now select the bot that is associated with the application used in Teams and then open the “Configure” section. Look for the field called “Endpoint Address” which is where the Contract Id should be included. As an example, I will use the contract id “takenet”. All you need to do is insert this word as a subdomain right after the “https://” field and before the “.abs”. In my example the address was like “https://takenet.abs.gw.msging.net/…” Before After Correction of URLS when using BlipChat In cases where the BlipChat channel is used on its own websites, it is important to check whether the script used is using the contract ID. To do this, open the chatbot being used, access the Channels tab, and open the BlipChat channel. Then, open the “Installation” tab and check if the script used is the same as the one available in your bot.In the example below, the use of the contract ID is evident. Access to sites with contract ID Whenever you access your chatbots on the portal, use the address with your contract ID.Ex: https://takenet.blip.ai Whenever you use DESK for service, open the address with your contract ID.Ex: https://takenet.desk.blip.ai For more information, access the discussion on the subject at our community or the videos on our canal. 😃 Related articles Creating interactive messages in WhatsApp Audience file configuration - Bulk notification sending Sending WhatsApp Active Messages on Blip Desk Using Dynamic Content Managing Access Permissions