Skip to main content
GET
Get Tts Run Info
You’d reach this step after the old async POST /tts job completes. That whole pattern is deprecated—new builds should stream speech with POST /tts-stream rather than waiting on a finished run and fetching bytes afterward.
This endpoint is the final step in your text-to-speech journey, where you retrieve your completed audio file. Once your task has reached a SUCCESS status and you’ve received a run_id, you can use this endpoint to access your generated audio and incorporate it into your application.

How to Use this Endpoint

Retrieving your generated audio is straightforward - simply make a GET request to this endpoint with the run_id you received when your task completed. The system will respond by providing your audio in your preferred format.

Understanding Response Options

This endpoint offers flexibility in how you receive your audio content. You can specify your preference using the output_type parameter:

Working with Raw Bytes

When using the default raw_bytes output type, the endpoint streams the audio data directly to your application. This approach is ideal when you want to:
  1. Save the audio file to your local system
  2. Process the audio data immediately in your application
  3. Play the audio without storing it permanently
The streaming approach is particularly efficient for handling larger audio files as it processes the data in manageable chunks rather than loading everything into memory at once.

Working with File URLs

If you prefer to receive a URL pointing to your audio file instead of the raw data, specify output_type=file_url. The response will be a JSON object containing a URL where the audio file can be accessed. This approach is beneficial when:
  1. You need to share the audio file with others
  2. Embed the audio in web content
  3. Handle the download process separately from retrieval
Note that file URLs have an expiration time, so download or use them promptly rather than storing them long-term.

Examples

Saving Audio to a File

Here’s how to retrieve and save your generated audio using Python:

Getting a File URL

If you prefer to receive a URL to the audio file instead:

Next Steps

Now that you’ve successfully retrieved your generated audio, you can:
  1. Incorporate it into your applications or websites.
  2. Process it further with audio editing tools.
  3. Combine multiple audio segments into a cohesive narrative.
  4. Share it with your users through your platform.
With these capabilities, you have everything you need to build rich, accessible voice experiences into your applications.

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.

Path Parameters

run_id
integer
required

The unique identifier for the run, which was generated during the Text-to-Speech creation process and returned upon task completion.

Query Parameters

output_type
enum<string>
default:raw_bytes

The type of the Text-to-Speech output to return. Either streamable audio bytes or a URL to the generated file.

Available options:
raw_bytes,
file_url

Response

Successful Response

The generated audio file bytes in FLAC format, representing the speech created from the Text-to-Speech task.

Last modified on May 12, 2026