{"status":"success","data":""}
curl --location --request POST 'https://zylalabs.com/api/12985/ultimate+tts+text+processing+and+formatter+api/25971/purifier' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw 'This is a test message.'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Ultimate TTS Text Processing and Formatter API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
Advanced TTS Text Purifier & Formatter API
The TTS Text Purifier & Formatter API offers a robust solution to a common issue: messy raw text generated by Large Language Models (LLMs) or scraped from the web. This text often contains unnecessary markdown, emojis, irregular brackets, and chaotic line breaks. When this unrefined text is fed directly into Text-to-Speech (TTS) engines like Edge-TTS or ElevenLabs, it can lead to audio glitches, unnatural pauses, or even crashes.
Our specialized, high-performance API serves as a vital link between text generation and audio synthesis, acting as an ultra-reliable filter to ensure that only perfectly formatted and TTS-ready text enters your audio pipeline.
Core Capabilities:
Ideal For: This API is perfect for automated self-media production pipelines, AI video generators, audiobook narrations, and autonomous voice agents. Easily integrate our TTS Text Purifier & Formatter API into your workflow with a single POST request, and eliminate TTS formatting errors for good.
Quick Integration Guide:
To get started, simply send a POST request with your uncleaned text. You'll receive a standardized, line-by-line formatted string that is optimized for immediate TTS processing.
Request Method: POST Content-Type: application/json
Request Body Example:
{
"raw_text": "Hello world!!! 【cheering】 This is a messy text... \n\n\n It has too many spaces and (weird brackets)."
}
Response Example:
{
"status": "success",
"original_length": 105,
"cleaned_length": 76,
"data": "Hello world!!!\nThis is a messy text...\nIt has too many spaces and."
}
Note: The data field in the response contains the fully formatted text, perfectly divided by newline characters (\n) for sequential TTS engine processing.
The Purifier endpoint returns a JSON object containing the status of the request, the original text length, the cleaned text length, and the cleaned data itself. This ensures users receive clear feedback on the processing of their input text.
The key fields in the response data include "status" (indicating success or failure), "original_length" (the length of the input text), "cleaned_length" (the length of the processed text), and "data" (the cleaned, TTS-ready text).
The returned data is structured as a JSON object. It includes fields for status, original and cleaned text lengths, and the cleaned text itself, formatted with newline characters for easy processing by TTS engines.
The Purifier endpoint provides information about the status of the text purification process, the lengths of the original and cleaned texts, and the cleaned text itself, which is optimized for TTS applications.
The response data is organized in a JSON format with clearly defined fields. The "status" field indicates the outcome, while "original_length" and "cleaned_length" provide metrics on text size, and "data" contains the formatted text.
Typical use cases for the Ultimate TTS Text Processing and Formatter API include preparing text for automated media production, enhancing AI video generation, improving audiobook narration quality, and optimizing text for autonomous voice agents.
Users can utilize the returned data by directly feeding the "data" field into their TTS engines, ensuring that the text is properly formatted and free of errors, which enhances audio quality and reduces processing issues.
The API employs aggressive symbol stripping, spatial compression, smart sentence segmentation, and a zero-empty-line guarantee to ensure the purified text is clean, coherent, and ready for seamless TTS processing.
The Purifier endpoint accepts a single parameter, "raw_text," which should contain the uncleaned text you want to purify. This text can include various formatting issues, such as markdown, emojis, and irregular line breaks.
Users can customize their requests by modifying the "raw_text" parameter to include any text they wish to purify. This allows for flexibility in handling different types of messy text from various sources.
In the response, "status" indicates whether the purification was successful, "original_length" shows the length of the input text, "cleaned_length" reflects the length of the processed text, and "data" contains the cleaned, TTS-ready text.
Data accuracy is maintained through rigorous processing techniques, including aggressive symbol stripping and smart sentence segmentation, which ensure that the semantic meaning of the text is preserved while removing errors.
Users can expect the response to consistently include a "status" field indicating success, along with "original_length" and "cleaned_length" metrics. The "data" field will always contain the cleaned text formatted with newline characters for TTS processing.
If the API returns an empty "data" field, users should check the "status" field for error messages. This can indicate issues with the input text, prompting users to revise the "raw_text" parameter for better results.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund