Skip to main content
POST
Get Stories Runs Results in Bulk
Streamline your workflow by retrieving results from multiple story conversion tasks in a single API call. This bulk endpoint eliminates the need for individual requests when managing large batches of story processing jobs, making it ideal for content management systems, automated publishing workflows, or analytics dashboards that need to aggregate story conversion results.

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.
All run IDs in the request must be valid and belong to completed story conversion tasks

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)
All retrieved audio links become inaccessible after 24 hours

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

Authorizations

x-api-key
string
header
required

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

application/json
run_ids
integer[]
required

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).

Required array length: 2 - 5 elements
Example:

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.

{key}
object
Last modified on May 16, 2026