If you want to implement other channels with which Aivo has no integration and you only need the bot's conversational engine, you can use the messaging API. For example, if you want to place the bot in an App, but you do not want the window to open, but the bot to be embedded as if it were part of the application, you can use the API.
To do this you will need to consider the following:
Plugins: The plugins must be developed entirely, Aivo will only provide the information in JSON.
Important: With the Assisted Navigation add-on it will not be possible to keep the chat history when redirecting to another page unless you work on such implementation.
Integrations: If you already have integrations and decide to continue via API, no adjustments are necessary. In case the integration contains add-ons (carousel, buttons, etc.) it is necessary to validate its operation and adapt it to the provider used, that is, it will depend on the channel where it is used and the scope of the add-ons in it.
Forms: you will have to develop their structure, even if the channel adapts them to call back, they will work correctly.
Analytics: if you have the API when analyzing the channels implemented with it, you must apply in the Channels filter "Public Api".
Important: If you connect more than one channel through the API, all of them will be analyzed under the indicated filter ("Public API"), it is not possible to apply a distinction.
SDK: Through the API you will be able to send the data you want within the "user" parameter, to be able to use it in integrations or see it within the Chat Reports, for example.
Important: If the API is used, Aivo will not be able to provide support for the tool with which the integration is made, since they are platforms of which it has no knowledge.
Keep in mind that this type of practice requires a team of developers due to the level of complexity.