Documentation Index

Fetch the complete documentation index at: https://help.commbox.io/llms.txt

Use this file to discover all available pages before exploring further.

Transcribe a Call Recording

Prev Next
Post
/objects/{OBJECT_ID}/transcribe

This API submits a call recording for transcription. The transcript is written back into the conversation as speaker-attributed messages.
The request is accepted immediately and processed asynchronously – use the returned request_id with the GET status API to follow its progress.

The recording can be supplied in one of three ways:

  • activity_id – reference an existing call-recording activity already on the conversation.
  • recording_path – a path on the channel's configured recording domain, which CommBox downloads.
  • file upload – send the audio file directly as multipart/form-data.
Note: Sending both an activity_id and a recording (path/file) returns ambiguous_input; sending none returns missing_input.


Required path param is the Object (conversation) Id.

(POST) /objects/OBJECT_ID/transcribe

Example:
https://api.commbox.io/objects/293854/transcribe
Security
HTTP
Type bearer

API key is needed to authorize requests. You can get your API key via the management console.
A Bearer Token is needed to be set in the Authorization header of every API call.
For additional support you can contact us.

Path parameters
OBJECT_ID
Required

Object Id is a CommBox generated number for the conversation.

Body parameters

Use application/json to reference an existing activity (activity_id) or a recording path (recording_path). Use multipart/form-data to upload the audio file itself.

Expand All
object
Example{ "activity_id": 982310, "client_reference_id": "twilio-seg-9f3a", "speakers": [ { "name": "Agent Dan", "managerId": 4012 }, { "name": "Customer" } ] }
activity_id
integer (int64)

A CommBox generated number for an existing call-recording activity on the conversation. Mutually exclusive with recording_path / file upload.

Example982310
recording_path
string

Path of the recording on the channel's configured recording domain (relative, must not be an absolute URL). Mutually exclusive with activity_id.

Example/2024/05/call-8842.wav
client_reference_id
string

Your own identifier for this request. When supplied, the request becomes idempotent – repeating it with identical content returns the original request_id.

Exampletwilio-seg-9f3a
speakers
Array of object

Ordered list of the speakers expected in the recording. An entry with managerId is attributed to that agent; an entry without one is attributed to the customer of the conversation.

object
name
string

Display name of the speaker.

ExampleAgent Dan
managerId
integer (int64)

A CommBox generated number for the agent (manager). Omit for the customer.

Example4012
object
file
string (binary)

The audio file to transcribe.

client_reference_id
string

Your own identifier for this request (idempotency key).

Exampletwilio-seg-9f3a
recording_path
string

Alternative to uploading a file – a path on the channel's configured recording domain.

Example/2024/05/call-8842.wav
speakers
string

The speakers array, JSON-encoded as a string.

Example[{"name":"Agent Dan","managerId":4012},{"name":"Customer"}]
Responses
201

Accepted - The transcription request was accepted and is being processed

Expand All
object
status
string
Example201
description
string
ExampleAccepted
response_time
string
Example2024-08-06T07:51:52.2581942Z
data
object
request_id
string

A CommBox generated identifier for the transcription request. Use it with the GET status API.

Examplereq_8f3a12c47b9e4d05
status
string

Status of the request at submission time.

Exampleaccepted
object_id
integer

A CommBox generated number for the conversation.

Example293854
activity_id
integer

The referenced call-recording activity. Returned only when activity_id was supplied – otherwise the activity is created during processing and appears in the GET status response.

Example982310
client_reference_id
string

Echo of the supplied client_reference_id. Returned only when one was supplied.

Exampletwilio-seg-9f3a
400

Bad Request - The request could not be understood by the server. Incoming parameters might not be valid (missing_input, ambiguous_input, invalid_speakers, activity_id_required, activity_not_found, activity_wrong_type, file_too_large, blocked_url)

Expand All
object
status
string
Example400
description
string
ExampleProvide either activity_id or a recording (recording_path / file), not both.
response_time
string
Example2024-08-06T07:51:52.2581942Z
data
object
error
object
code
string

Machine-readable error code.

Exampleambiguous_input
message
string
ExampleProvide either activity_id or a recording (recording_path / file), not both.
401

Unauthorized - The supplied credentials, if any, are not sufficient to access the resource

404

Not found - The requested resource is not found

409

Conflict – The provided client_reference_id has already been used for a different transcription request. Use a new client_reference_id or resend the original request content

422

Unprocessable Entity - Transcription is not installed or not enabled for this channel (transcription_not_configured)

429

Too Many Requests - Too many concurrent transcription requests for this brand (Throttling). A Retry-After header is returned

500

Server Error - The server could not return the representation due to an internal server error

501

Not Implemented - The requested operation is not supported