The Dialogflow team announced that they would be deprecating their V1 version of the Dialogflow api in Oct 2019
The Bot Forge have been following the progress of the latest V2 api since its official launch in April this year, it’s no surprise that the Dialogflow team have made this announcement as they concentrate their efforts on the new API. However it does have some serious implications for existing chatbots utilising the v1 API.
You can see some more details about upgrading from V1 to V2 in the official guide here. We also aim to provide some more detailed information about carrying out an upgrade on this blog so watch out for that.
Anyone who already has built out their website chatbots using v1 API, then they should start planning for the migration sooner rather than later. Any new features should be added after the upgrade. The migration is potentially a non-trivial task, considering some chatbots have some fairly complex code driving their fulfilment. If you have a live bot in production our advice is to set up an upgrade chatbot as a copy of your existing bot project and then work through the upgrade there. You can guarantee that changing to V2 will mean that fulfilment and API calls may stop working. Once the upgrade is complete re-testing all bot functionality is strongly advised before setting live.
Chatbot Web Interfaces
We would recommend everyone who is creating custom website chatbots to do so using the v2 API. All our new chatbots are built using the v2API.
The big change for v2 is that it uses Google’s OAuth2 for its authentication, with v1 you could simply use the client access token when calling the v1 API. Implementing the features required to authenticate against the new v2 API means some significant extra development effort.
If you need assistance or advice with your own chatbot v2 upgrade please get in touch, we are Dialogflow experts and would be happy to help!
At the Bot Forge, we specialise in building chatbots so you feel free to contact us if you want to discuss further.