- HTTP request
- Path parameters
- Request body
- Response body
- Authorization scopes
- IAM Permissions
- Try it!
Create a long-running conversation upload operation. This method differs from conversations.create
by allowing audio transcription and optional DLP redaction.
HTTP request
POST https://{endpoint}/v1/{parent=projects/*/locations/*}/conversations:upload
Where {endpoint}
is one of the supported service endpoints.
The URLs use gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
parent |
Required. The parent resource of the conversation. |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "conversation": { object ( |
Fields | |
---|---|
conversation |
Required. The conversation resource to create. |
conversation |
Optional. A unique ID for the new conversation. This ID will become the final component of the conversation's resource name. If no ID is specified, a server-generated ID will be used. This value should be 4-64 characters and must match the regular expression |
redaction |
Optional. DLP settings for transcript redaction. Will default to the config specified in Settings. |
speech |
Optional. Speech-to-Text configuration. Will default to the config specified in Settings. |
Response body
If successful, the response body contains an instance of Operation
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.
IAM Permissions
Requires the following IAM permissions on the parent
resource:
contactcenterinsights.authorizedConversations.upload
contactcenterinsights.conversations.upload
For more information, see the IAM documentation.