Skip to main content
POST
Inworld TTS 2

1. Overview

This document describes how to use speech synthesis and voice cloning through the Inworld TTS native protocol. Both endpoints are synchronous: a POST request returns the result directly, with no need to create a task and poll for the result.

1.1 Endpoints

The full address in the examples in this document is https://api.novita.ai plus the endpoint path in the table above, where https://api.novita.ai is the API domain you use.

1.2 Authentication

All requests must carry the platform API Key and specify the JSON content type:

1.3 Response Structure

Both endpoints return JSON on success:
  • In the JSON returned by a successful speech synthesis request, audioContent is Base64-encoded audio data that must be decoded to obtain the raw audio bytes.
  • In the JSON returned by a successful voice cloning request, voice.voiceId is the ID of the newly cloned voice, which can be used directly as the voiceId field of the speech synthesis endpoint.

2. Speech Synthesis

Official parameter reference: Synthesize Speech

2.1 Endpoint

Common request fields: voiceId and voiceDesign (instant voice design, out of scope of this document) are mutually exclusive; do not provide both.

2.2 Example

2.3 Response

On success, the endpoint returns (HTTP 200):
Verified in practice: this endpoint has been validated with real requests in all three platform environments and returns real audioContent.

2.4 Billing

The character count is calculated from the text field. Chinese characters count as 2 characters, and other characters (including English letters, digits, spaces, and punctuation) count as 1 character. The exact unit price depends on the pricing page of the service you use.

3. Voice Cloning

Official parameter reference: Clone a Voice

3.1 Endpoint

The request body is JSON. Common fields:
gender/ageGroup/categories cannot be set during cloning. Call UpdateVoice separately after cloning is complete to set them.

3.2 Example

3.3 Response

On success, the endpoint returns (HTTP 200):
Verified in practice: the full “clone → synthesize with the cloned voiceId” path has been validated with real requests in all three platform environments.

3.4 Billing

The voice cloning endpoint is always free of charge and generates no cost.

4. Common Errors and Notes

Endpoint errors use the following structure:
Other notes:
  • A voiceId created by voice cloning is shared among all callers under the current API Key, and the system does not record which caller cloned which voice. Manage voice ownership and visibility in your own business layer, and do not assume the platform isolates voices between callers.
  • Supported audio formats for the voice cloning endpoint are wav/mp3/webm, with a maximum of 12MB per file.
Última modificação em 20 de outubro de 2026