Fetch Transcription Results
Retrieves the results of multiple transcription runs using the provided run IDs in the request body.
Efficient Bulk Processing
Managing multiple transcription projects becomes seamless with bulk retrieval functionality. Our system delivers transcriptions for multiple runs that include:- Parallel Processing: Retrieve results from multiple transcription runs in a single request
- Temporal Precision: Exact start and end timestamps for each spoken segment across all runs
- Speaker Differentiation: Clear identification of different speakers throughout each piece of content
- Verbatim Text: Accurate textual representation of all spoken content for each run
Retrieving Multiple Transcription Results
To access your completed transcriptions in bulk, you’ll need the uniquerun_id values that were assigned when you initially submitted your transcription requests. These identifiers allow our system to locate your specific transcription results within our processing infrastructure and return them as a consolidated response.
Understanding the Request Structure
The bulk transcription endpoint requires a JSON payload containing an array of run IDs. This allows you to specify exactly which transcription results you want to retrieve:Response Structure
The API returns an array of transcription results, where each element corresponds to one of the requested run IDs. Each transcription result contains an array of dialogue items with detailed timing and speaker information:Bulk Processing Benefits
The bulk transcription endpoint provides several advantages for managing multiple transcription projects:Workflow Efficiency
- Single Request: Retrieve multiple transcription results without making separate API calls
- Reduced Latency: Minimize network overhead by consolidating requests
- Batch Processing: Perfect for processing entire content libraries or project collections
Content Management
- Comparative Analysis: Easily compare transcriptions across multiple runs
- Consolidated Reporting: Generate unified reports from multiple transcription sources
- Quality Assurance: Streamline review processes for large-scale transcription projects
Integration Capabilities
- Database Population: Efficiently populate content databases with transcription data
- Search Indexing: Build comprehensive search indexes across multiple content pieces
- Analytics Processing: Perform cross-content analysis and pattern recognition
Best Practices for Bulk Processing
To maximize the effectiveness of bulk transcription retrieval:Request Optimization
- Batch Size: Request reasonable batch sizes (typically 3-5 runs per request)
- Run Grouping: Group related runs together for more efficient processing
- Retry Logic: Implement retry mechanisms for handling temporary failures
Data Management
- Result Caching: Cache frequently accessed transcription results
- Incremental Processing: Process new runs while maintaining existing data
- Storage Strategy: Implement efficient storage solutions for large transcription datasets
Performance Considerations
- Parallel Processing: Use the bulk endpoint instead of multiple individual requests
- Memory Management: Process large result sets in chunks to manage memory usage
- Rate Limiting: Respect API rate limits when making frequent bulk requests
Authorizations
The x-api-key is a custom header required for authenticating requests to our API. Include this header in your request with the appropriate API key value to securely access our endpoints. You can find your API key(s) in the 'API' section of our studio website.
Body
An array of unique positive integers, each representing the ID of a specific run. You must provide between 2 and 5 IDs, and all IDs must correspond to the same run type (e.g., all text-to-speech or all dubbing runs).
2 - 5 elementsResponse
Successful Response
An object containing the results of one to five transcription runs. Each key in the object is a unique identifier for a run, and the corresponding value is the transcription output.