Create transcript upload request - Cognigy Documentation
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
POST
/ v1
/transcript-request
Try it
cURL
basic
curl --request POST \
--url https://api-trial.cognigy.ai/testing/v1/transcript-request \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'
201
400
429
{
"success": true,
"requestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"expiresAt": "2026-02-08T15:00:00.000Z",
"maxFiles": 5,
"maxFileSize": 10485760,
"maxTotalSize": 52428800,
"supportedFormats": [
"application/pdf",
"text/csv",
"application/vnd.openxmlformats-officedocument.wordprocessingml.document"
],
"status": "pending"
}
{
"error": "projectId is required (in body, query, or as projectReference)"
}
{
"error": "Maximum of 10 active transcript requests reached for this project."
}
Authorizations
bearerAuthapiKeyAuthbearerAuthapiKeyAuth
Authorization
string
header
required
JWT Bearer Token for authentication
Headers
project_id
string
Project identifier. Use this header to pass projectId; alternatively use body or query.
Query Parameters
projectId
string
Project identifier (alternative to project_id header or projectReference in body)
Body
application/json
projectId
string
Project identifier (alternative to project_id header)
projectReference
string
Alternative project reference
Response
201
application/json
Transcript request created successfully
success
boolean
required
requestId
string
required
Unique request identifier for subsequent calls
expiresAt
string
required
When this request will expire
maxFiles
integer
required
Maximum number of files that can be uploaded
maxFileSize
integer
required
Maximum file size in bytes
supportedFormats
string[]
required
Supported file formats
status
enum
required
Request status
Available options:
pending
maxTotalSize
integer
Maximum total upload size in bytes
Last modified on July 2, 2026
Upload and parse a transcript file Upload a single transcript file for parsing and content extraction. This is the second step in the three-step workflow. The file is streamed directly to Redis via the streamUpload middleware, then:
- Read back from Redis
- Parsed based on file type (PDF, CSV, DOCX)
- Analyzed for speaker labels (Agent/Customer)
- Stored as structured data in Redis (keyed by requestId)
Multiple files can be uploaded by calling this endpoint multiple times with the same requestId. The generate endpoint retrieves all files for the request by requestId.