Bulk Processing Benefits
This endpoint provides several operational advantages:- Reduced API Calls: Fetch multiple story results with one request
- Consistent Data Structure: Uniform response format across all stories
- Efficient Resource Usage: Optimized for high-volume story retrieval
- Batch Processing Support: Perfect for automated content pipelines
Request Structure
The endpoint accepts a JSON payload containing an array of run IDs from your story conversion tasks. Each run ID corresponds to a previously submitted story processing job.Response Format
The API returns an array of story result objects, each containing the same structure as the individual story result endpoint:- Full Audio Narration: Complete audiobook-style recording (
audio_url
) - Dialogue-Only Track: Isolated character conversations (
dialogue_url
) - Time-Coded Transcript: Narrative transcript with speaker attribution (
transcript
)
Example Python Implementation
Here’s how to fetch multiple story results efficiently using Python:Use Cases
This bulk endpoint is particularly valuable for:- Content Management Systems: Retrieving story assets for publication workflows
- Analytics Dashboards: Aggregating conversion results for reporting
- Automated Publishing: Batch processing completed stories for distribution
- Quality Assurance: Bulk validation of story conversion outputs
- Archive Management: Collecting completed story assets for long-term storage
Error Handling
The endpoint validates all provided run IDs before processing. If any run ID is invalid or corresponds to an incomplete conversion task, the entire request will return a validation error. Ensure all run IDs represent successfully completed story processing jobs before making 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
elements[12345, 6789]
Response
Successful Response
An object containing the results of one to five story runs. Each key in the object is a unique identifier for a run, and the corresponding value is stories run output.