Migrate to Dialogflow API V2 before October 23, 2019October 23, 2018
Back in April, we announced that Dialogflow API V2, along with Dialogflow Enterprise Edition (built on API V2), became generally available to all users. API V2 now serves as the default API for all new Dialogflow agents, and we’ve been releasing new features on API V2 since then. Some of the new features include: Versions and environments for building, testing, and deploying multiple environments, and Knowledge Connectors and Phone Gateways for easily implementing content-heavy FAQs and phone numbers into your agent.
API V1 will be deprecated on October 23, 2019
As we’re building out more and more functionality for API V2, we will also be shutting down API V1 in one year – on October 23th, 2019. If your production agent is currently using API V1, it must be migrated to API V2 before this date.
See the API V1 → V2 migration guide for instructions on how to migrate, or read on for an overview of what’s required.
How to migrate from API V1 to API V2
Migrating from API V1 to API V2 affects the behavior of the Dialogflow console, APIs, and your fulfillment. You can check what parts of Dialogflow you are using here. When migrating from API V1 to API V2, please note the following:
- If utilizing fulfillment for your agent, you must update your fulfillment code to support the API V2 request and response formats before switching to API V2.
- All Dialogflow APIs have been redesigned and use OAuth for authentication. If you use this API directly, you need to update your client code before switching to API V2. See this guide for API V2 equivalents of API V1 methods and fields.
- If you’re building an Action with the Google Assistant integration, see this Medium post for information on how to migrate from API V1 to API V2.
Posted by Matt Carroll, Developer Programs Engineer