Initiate a Transcription

In order to initiate a transcription for an existing recording, you must do a POST request to the following endpoint.

Transcribe recording

post

Create transcription for a recording

Authorizations

useraccessKey

Path parameters

workspaceIdstringRequired

recordingIdstringRequired

Body

localestring · enumRequiredDefault: en-USExample: en-USPossible values:

messageIdstring · uuidOptional

conversationIdstring · uuidOptional

recordingIdstring · uuidOptional

Responses

202

Transcription was accepted for processing

application/json

400

The request did not pass validation

application/json

404

The request did not pass validation

application/json

422

The request did not pass validation

application/json

post

HTTPcURLJavaScriptPython

POST /workspaces/{workspaceId}/recordings/{recordingId}/transcriptions HTTP/1.1
Host: 
Authorization: Bearer jwt
Content-Type: application/json
Accept: */*
Content-Length: 178

{
  "locale": "en-US",
  "messageId": "123e4567-e89b-12d3-a456-426614174000",
  "conversationId": "123e4567-e89b-12d3-a456-426614174000",
  "recordingId": "123e4567-e89b-12d3-a456-426614174000"
}

{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "recordingId": "123e4567-e89b-12d3-a456-426614174000",
  "status": "accepted",
  "stereo": true,
  "locale": "en-US",
  "url": "text",
  "summary": "text",
  "createdAt": "2025-07-13T02:24:39.217Z",
  "updatedAt": "2025-07-13T02:24:39.217Z"
}

A transcription request is asynchronous. That means it will take some time before the result has been generated. This depends on the total duration of the recording.

Request

curl "/workspaces/{workspaceId}/recordings/{recordId}/transcriptions" \
     -H 'Authorization: Bearer {Token}'

Response

{
  "id": "85530fbe-6dc1-4884-a9e6-e62b0f4c6df1",
  "recordingId": "5b74ee9e-9d45-473a-82cd-f1f7feea6bbd",
  "status": "accepted",
  "stereo": false,
  "locale": "en-US",
  "createdAt": "2023-10-24T12:52:27.483Z",
  "updatedAt": "2023-10-24T12:52:27.483Z"
}