Audio - Append to existing Conversation

PUT {{base_url}}/v1/process/audio/{{conversation_id}}

Append Audio File

The Async Audio API allows you to process an additional audio file to the previous conversation, append the transcription and get conversational insights for updated conversation.

It can be useful in any use case where you have access to multiple audio files of any type of conversation, and you want to extract the insightful items supported by the Conversation API.

The conversationId of the conversation processed from any channels (Realtime, Audio/Video Files or Text Content) are allowed.

Learn More about Async Audio API.

Request Body

The binary payload of a file audio file.

Notice that the content type is binary, which allows you to select a file you want to upload.

Path Params

Query Params

Response

In response, conversationId and jobId are returned.

jobId can be used to get updates on the job status.

conversationId can be used with the Conversation API to get all the insights, topics and processed messages etc.

Webhook Payload

webhookUrl will be used to send the status of job created for uploaded audio. Every time the status of the job changes it will be notified on the webhookUrl.

## channelMetadata Object

 {
   "channelMetadata": [
     {
       "channel": 1,
       "speaker": {
         "name": "Robert Bartheon",
         "email": "robertbartheon@gmail.com"
       }
     },
     {
       "channel": 2,
       "speaker": {
         "name": "Arya Stark",
         "email": "aryastark@gmail.com"
       }
     }
   ]
 }

channelMetadata object has the following members:

speaker has the following members:

Billing for a speaker separated channel audio file happens according to the number of channels present in the audio files. The duration for billing will be calculated according to the below formula:

totalDuration = duration_of_the_audio_file * total_number_of_channels

So if you send a 120-second file with 3 speaker separated channels, the total duration for billing would be 360 seconds or 6 minutes.

Request Params

HEADERS