To use Insights with VPC Service Controls (VPC Service Controls), add
Insights to your security perimeter. See theVPCSC documentationfor more information.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eSeveral APIs, including Insights, Cloud Storage, Speech-to-Text, Cloud Data Loss Prevention, and Dialogflow, must be enabled for conversation data processing in Conversational Insights.\u003c/p\u003e\n"],["\u003cp\u003eEnabling APIs is done through the Google Cloud console, navigating to the APIs & Services page, and selecting each API to enable.\u003c/p\u003e\n"],["\u003cp\u003eSetting up Insights API access involves selecting or creating a Google Cloud project and enabling the Conversational Insights API within that project.\u003c/p\u003e\n"],["\u003cp\u003eAfter setup, you can verify your configuration by using a CURL command to list Insights conversations, which initially returns an empty dictionary.\u003c/p\u003e\n"],["\u003cp\u003eFor enhanced security, Insights can be integrated with VPC Service Controls by adding it to your security perimeter, as detailed in the VPCSC documentation.\u003c/p\u003e\n"]]],[],null,["You must enable the following APIs for conversation data processing in Conversational Insights:\n\n- Insights API to use Insights.\n- Cloud Storage API to ingest conversations into Insights.\n- Speech-to-Text API to upload audio files.\n- Cloud Data Loss Prevention API to perform redaction on audio or transcript files.\n- Dialogflow API, which is required for Dialogflow runtime integration and Topic modeling V1.\n\nThis quickstart walks you through the following actions:\n\n1. Enable the Cloud Storage API, Cloud Data Loss Prevention API, Speech-to-Text, and Dialogflow APIs.\n2. Enable the Insights API.\n3. Successfully send a request to the Insights API and receive a response.\n\nEnable the Cloud Storage API, Cloud Data Loss Prevention API, Speech-to-Text, and Dialogflow APIs.\n\nYou must enable the Cloud Storage API before you can use Cloud Storage. To enable APIs:\n\n1. Navigate to the [Google Cloud console](http://console.cloud.google.com).\n2. Click **Go to APIs overview** :\n\n3. On the **APIs \\& Services** page that appears, click **Cloud Storage**.\n\n4. If you haven't already enabled this API, click **Enable**.\n\n5. Repeat the preceding steps for the **Speech-to-Text API** , **Cloud Data Loss Prevention API** , and the **Dialogflow API**.\n\nSet up Insights API access\n\n1. Navigate to the [Google Cloud console](http://console.cloud.google.com).\n2. Click the project selector menu:\n3. Select a pre-existing project or create a new project.\n4. Enter **Conversational Insights API** into the Google Cloud console search bar.\n5. Click the option that pops up and select **Enable**.\n6. [Install and set up](/sdk/install) the Google Cloud SDK.\n\n\n7.\n\n Create local authentication credentials for your user account:\n\n ```bash\n gcloud auth application-default login\n ```\n\n\n If an authentication error is returned, and you are using an external identity provider\n (IdP), confirm that you have\n [signed in to the gcloud CLI with your federated identity](/iam/docs/workforce-log-in-gcloud).\n8. Verify your setup by entering the following CURL command, which lists all of your\n Insights conversations. It should return an empty dictionary:\n\n curl -H \"Authorization: Bearer $(gcloud auth application-default print-access-token)\" \"https://contactcenterinsights.googleapis.com/v1/projects/\u003cvar\u003eproject-id\u003c/var\u003e/locations/us-central1/conversations\"\n\nOptional: Use Insights with VPCSC\n\nTo use Insights with VPC Service Controls (VPC Service Controls), add\nInsights to your security perimeter. See the\n[VPCSC documentation](/vpc-service-controls/docs) for more information."]]
