Skip to main content
GET
Get Tts Result
This route is the legacy status check that pairs with deprecated POST /tts. For greenfield work, prefer streaming: call POST /tts-stream and let audio flow continuously instead of polling here.
This endpoint allows you to check on the progress of your Text-to-Speech tasks. When you submit a text-to-speech request, our system begins processing your audio in the background. This endpoint lets you monitor that process from start to finish, keeping you informed about when your audio will be ready.

How to Use This Endpoint

To check the status of your Text-to-Speech task, simply send a GET request to this endpoint with the task_id you received when you submitted your original request. The system will respond with detailed information about where your task stands in the processing pipeline.

Understanding the Response

When you call this endpoint, you’ll receive a status response that includes several key pieces of information:
  • Status Code: Indicates whether the task is still processing, has completed successfully, or encountered an error.
  • Result Information: For completed tasks, includes the run_id needed to download your finished audio file.

Status Types Explained

Your text-to-speech task will pass through different states as our system processes it. Understanding these status codes will help you properly handle each situation in your application:

Example Code

This polling mechanism gives you flexibility to build applications that can provide real-time feedback to users about their text-to-speech conversions. You can adjust the polling interval based on your specific needs, checking more frequently for time-sensitive applications or less frequently for background tasks.

Next Steps

Once your task shows a status of SUCCESS, you’ll receive a run_id in the response. This run_id is your key to accessing the generated audio. Take this identifier and use it with the /tts-result/{run_id} endpoint to download your finished audio file and put it to work in your application.

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

task_id
string
required

A unique identifier for the task. This is used to query the status of the text to speech task that is running. It is returned when a create request is made for a text to speech.

Response

Successful Response

status
enum<string>
Available options:
SUCCESS,
PENDING,
TIMEOUT,
ERROR,
PAYMENT_REQUIRED
run_id
integer | null
Last modified on May 12, 2026