Frequently asked questions
What is a TTS API?
A TTS API is a cloud service that converts text into audio files via a simple HTTP request. For LMS platforms, you send text to the endpoint and receive an audio file, replacing manual voice-over workflows with programmable speech generation.
How is it different from GTTS python?
GTTS relies on Google’s service, while our API uses dedicated engines with eight distinct voice presets like Aria and Atlas. It supports 23 languages, offers multiple audio formats (MP3, WAV, FLAC, OPUS, PCM), and provides consistent pricing.
Can it generate audio in real-time?
No. The API returns the complete audio file after synthesis. Requests are processed sequentially, so under load a request may wait in a queue. It does not support streaming or WebSocket connections for partial audio delivery.
Does it support SSML?
No. The API accepts plain text input up to 4096 characters. It does not support SSML tags, phoneme dictionaries, or custom pronunciation lexicons for fine-grained control over pacing or emphasis within the generated audio.
What languages are supported?
It supports 23 languages including English, Spanish, German, French, Japanese, and Hindi. Any voice can speak any supported language. Vietnamese, Indonesian, Thai, and Ukrainian are not supported. Set the language parameter to ensure correct pronunciation for non-English Latin text.
How many voices are available?
There are eight voice presets: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion. These range from warm narrators to deep documentary styles. All voices are based on licensed recordings and can be selected via the voice parameter.
Is the audio synthetic?
Yes. Every generated file carries an inaudible watermark marking it as synthetic speech. The voices are based on licensed recordings from LibriTTS-R and LibriVox, but the output is algorithmically generated text-to-speech, not a direct recording of a human speaker.
Can I clone voices?
No. The service offers eight fixed presets and does not support custom voice cloning, uploading your own voice, or voice design. You cannot create unique voice profiles for your brand; you must choose from the available eight options.
What is the character limit?
Each API request accepts up to 4096 characters of text. For longer course scripts, split the text into parts, generate audio for each, and join the files. Spaces and punctuation count toward the character limit.
How do I pay?
Payments are made via USDT on the TRON network (TRC-20). The minimum top-up is $5, credited automatically within minutes. There are no monthly plans, no credit cards, and no invoices. Balance does not expire.
Is there a free trial?
Yes, if you sign in with Google. You receive $0.50 credit (about 50,000 characters) valid for 7 days. Accounts created with email and password start without trial credit. Failed requests are free.
What formats are supported?
Supported formats are MP3, WAV, OPUS, FLAC, and PCM. You specify the format in the request body. This allows you to choose between compressed audio for web delivery or lossless formats for high-quality LMS integration.
How long does generation take?
Generation is roughly real-time, averaging 25 characters per second. Short phrases take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue before synthesis begins.
Is there an SLA?
No. There is no uptime guarantee, SLA, or enterprise contract. Support is by email only. There is no phone number or live chat. The service is provided as-is without guaranteed response times or certifications.
Definition of a TTS API
A TTS API is a cloud service that converts text into spoken audio files via a simple programmatic interface. Instead of manually recording voiceovers for every lesson, developers send text data to a server and receive an audio file in return. This shifts audio production from a manual creative process to a reliable technical workflow.
Cloud-based audio generation
Audio synthesis happens on remote servers, not on your local machine or student's device. This offloads the computational heavy lifting, ensuring consistent quality without requiring your LMS to handle large audio files during upload. The service processes requests sequentially, generating realistic speech that maintains uniform tone across entire course catalogs.
Programmatic access
Integration relies on standard HTTP requests. By sending a POST request with your text payload, you trigger the synthesis engine. The system returns the audio file directly in the response, allowing your Python scripts or LMS plugins to store the file or stream it to the user immediately. Authentication is handled via a single API key.
Scalable architecture
The API handles infrastructure scaling, meaning you do not need to provision servers for peak enrollment periods. Whether you are generating audio for a single quiz question or an entire semester’s curriculum, the service manages the queue. This architecture supports edtech startups that need to scale audio production without managing complex backend infrastructure.
How it Works
The TTS API converts text into audio through a simple programmatic workflow. Developers send a POST request to the endpoint with the desired text payload, specifying parameters like voice, speed, and language in the JSON body.
The system processes the input and returns the synthesized audio file directly in the response. This eliminates the need for local rendering engines, allowing LMS platforms to generate voice-overs on demand without managing server resources.
Send text via POST request
You initiate synthesis by sending a POST request to https://api.t46.net/v1/audio/speech. The request body must include the text (up to 4096 characters), a model identifier ("tts-1" or "tts-1-hd"), and a voice preset. Authentication is handled via a Bearer token in the header.
- Endpoint: POST https://api.t46.net/v1/audio/speech
- Input: JSON body with
input,voice, andmodelfields - Auth:
Authorization: Bearer tts-...header
Receive audio file
Upon successful processing, the API returns the audio file directly in the response body. You can save this data as a static asset. Failed requests incur no charge and return a status error instead of audio data.
Support for multiple formats
Specify the desired output format using the response_format field. Available options include mp3, wav, opus, flac, and pcm. This flexibility allows you to balance file size and quality based on your LMS player capabilities and bandwidth constraints.
- mp3: Standard for web playback
- wav: Lossless quality
- opus/flac: Efficient compression
- pcm: Raw uncompressed data
Benefits for LMS Platforms
Replacing manual voice-over workflows with programmatic speech generation allows edtech startups to scale course production without hiring additional talent. A TTS API provides a consistent vocal identity across all modules, ensuring learners experience the same narrator tone whether they are listening to a beginner lesson or an advanced certification track.
Consistent voice quality
Programmatic generation eliminates the variability of different human voice actors. Each module maintains the same vocal timbre and pacing, creating a unified brand experience for your learners. This consistency is critical for maintaining engagement across long course series.
- Uniform narration across all course modules
- No variability between different voice actors
- Professional, clear audio output every time
Multi-language support
Generate audio in 23 languages without negotiating separate contracts with international voice talent. Any voice preset can speak any supported language, allowing you to localize courses rapidly. Set the ISO language code explicitly to avoid guess errors with similar scripts.
- Support for 23 languages including Arabic, Chinese, and Spanish
- All 8 voices can speak any supported language
- Instant localization without hiring new talent
Reduced production time
Replace days of studio recording with seconds of API calls. Longer texts are split into 4096-character chunks and joined automatically. This workflow allows course creators to update content quickly without re-recording entire segments, keeping your LMS content fresh and accurate.
- Generation takes seconds for short phrases
- Automatic splitting for longer texts up to 4096 characters
- Quick updates without re-recording studio sessions
Comparison with Local Libraries
Local libraries like GTTS offer a quick way to generate audio without an internet connection, but they lack the reliability needed for production LMS environments. Running a local Python process means you manage dependencies, handle network drops during downloads, and deal with inconsistent voice quality across different machines.
An API decouples generation from your application server. This ensures that your LMS remains responsive even during peak usage, as the heavy lifting happens on dedicated infrastructure. You get consistent outputs regardless of where your code runs.
GTTS python limitations
GTTS relies on Google’s web service behind the scenes, meaning it still requires an internet connection and a Python environment. It offers limited voice control, no speed adjustment, and often fails silently if the external service is slow. Managing retries and timeouts in a local script adds complexity to your course generation pipeline.
API reliability
Our API provides a stable endpoint that handles queuing and retries internally. Unlike local libraries that might crash or return incomplete audio files, our system guarantees a complete audio file or a clear error code. This reliability is critical when auto-generating hundreds of lesson files overnight.
Server management
With a local library, you must update Python packages and handle OS-level dependencies on every server. An API requires no maintenance on your side. Your LMS simply sends JSON and receives audio, keeping your infrastructure light and reducing the risk of version conflicts in your development environment.
Voice Selection
LMS Voice Lab provides eight distinct voice presets designed for clear, professional narration. Each voice is optimized for educational content, ensuring consistent audio quality across your course modules.
8 preset voices
The available voices are aria, nova, luna, and sage for female tones, and felix, milo, atlas, and orion for male tones. You select one by name in the voice parameter of your API request.
Gender and tone variety
Voices range from warm and clear to neutral and deep. This variety allows you to match the tone of your course, whether it is an instructional lecture or a storytelling module.
Licensing details
All voices are based on licensed recordings from LibriTTS-R (CC BY 4.0), derived from LibriVox public-domain audiobook readings. Every generated audio file includes an inaudible watermark identifying it as synthetic speech.
Language Support
A TTS API simplifies multilingual course creation by supporting 23 languages, from Arabic to Turkish. This allows edtech startups to localize content without hiring separate voice actors for each region.
The system ensures accurate pronunciation by either detecting the script automatically or using explicit language codes. This precision is critical for maintaining professional audio quality across diverse learner bases.
23 languages available
Our API supports a broad range of languages, including English, Chinese, French, German, Japanese, Korean, Spanish, and Hindi. This variety covers most major global markets, enabling creators to reach students in their preferred language without complex integrations.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Automatic detection
If you do not specify a language, the API guesses it based on the script. Latin text defaults to English, which works well for most English courses. This reduces the number of parameters you need to manage in your Python scripts.
Explicit language setting
For non-English Latin-script text, you should set the language parameter explicitly to avoid mispronunciation. For example, setting language='fr' ensures correct accent for French text, even if it uses Latin characters. This guarantees clarity for learners.
Audio Formats
Choosing the right audio format ensures your LMS delivers the best balance of quality, compatibility, and bandwidth efficiency. Our API allows you to select the output type that best fits your platform’s constraints.
MP3 for web
MP3 is the standard for web delivery, offering broad compatibility with all modern browsers and LMS players. It provides a compact file size while maintaining clear speech intelligibility, making it ideal for general course narration where storage and load times matter.
- Widely supported by all LMS video players
- Optimal balance of quality and file size
- Ideal for on-demand audio lessons
WAV for quality
WAV provides uncompressed, high-fidelity audio, preserving every nuance of the voice model. This format is best when you need the highest possible audio quality for premium content or when your LMS supports lossless playback without significant bandwidth penalties.
- Lossless, uncompressed audio quality
- Preserves full voice model nuance
- Best for high-end course modules
FLAC/OPUS for size
For efficient storage and streaming, FLAC and OPUS offer superior compression ratios with minimal quality loss. OPUS and FLAC offer efficient compression. These formats reduce server costs and improve playback speed for users on slower connections.
- FLAC: Lossless compression for smaller files
- OPUS: Efficient for variable bitrate streaming
- Reduces server storage and bandwidth costs
Data Usage
When you send text to our TTS API, the input is used exclusively for generating the audio file. We do not use your course content, lesson scripts, or quiz questions to train or improve our speech models. Your intellectual property remains yours, and the audio generation process is isolated from any data training pipelines.
Generated audio is returned directly in the API response and is not stored on our servers after delivery. This ensures that your educational materials are not retained for long-term analysis. Only the metadata required for billing—such as request time, character count, and status—is kept to ensure accurate charges and transparency.
Input text not trained
Your input text is processed solely to create the audio output. It is not used for model training or fine-tuning. This means your unique course content remains distinct from the data used to shape the voice models, preserving the integrity of your proprietary educational materials.
No persistent storage
Audio files are delivered in the response and are not stored by us after generation. This minimizes data retention risks and ensures that your audio assets are ephemeral unless you choose to save them. This approach is ideal for dynamic LMS environments where content is frequently updated.
Billing metadata
We retain minimal request metadata, including timestamp, character count, and status, strictly for billing purposes. This ensures accurate charges for each 1,000 characters processed. No other personal or content data is kept beyond what is necessary to verify usage and process payments.
This limited retention policy supports privacy compliance without compromising your ability to audit your API usage or reconcile invoices with precision.

Rate Limits
A TTS API processes text into speech via HTTP requests, but your usage is governed by strict rate limits to ensure stability. For LMS platforms generating course audio at scale, understanding these boundaries prevents bottlenecks during peak enrollment periods or batch processing.
The system allows 60 requests per minute per API key. This limit applies uniformly, meaning high-volume educational content generation must be paced accordingly. Requests exceeding this threshold are queued rather than rejected, ensuring no data loss but potentially increasing latency during heavy loads.
60 requests per minute
Your API key permits up to 60 synthesis requests within a one-minute window. This applies to all endpoints, including voice and model queries. New accounts start with a lower limit of 10 requests per minute until the first top-up is processed.
- Limit resets every 60 seconds
- Applies per API key
- New accounts start at 10 req/min
Queue behavior
If you exceed the 60 req/min limit, requests are queued and processed sequentially. Short phrases may take a few seconds to generate, while longer texts take longer due to real-time synthesis speeds. Under heavy load, queue wait times increase proportionally.
Load management
To maintain consistent performance, distribute requests evenly. Split large texts into chunks under 4096 characters and process them sequentially or with slight delays. Avoid burst traffic if real-time playback is critical, as queued requests introduce latency.
- Process sequentially under load
- Split texts into 4096-char chunks
- Avoid burst traffic for real-time needs
Pricing Model
Our pricing model is straightforward: you pay only for what you use, with no hidden fees or mandatory commitments. The cost is $10 per 1 million characters, which breaks down to $0.01 per 1,000 characters. Spaces and punctuation count toward this total. If a synthesis request fails, you are not charged, ensuring you only pay for successful audio generation.
This pay-as-you-go structure eliminates the need for complex enterprise contracts or minimum spend requirements. It allows edtech startups to scale their audio production costs directly in line with their content output, making it easy to predict expenses for course libraries or quiz banks without worrying about unused monthly allocations.
Pay per character
The rate is fixed at $10 per 1 million characters ($0.01 per 1,000 characters). This includes all characters, even spaces and punctuation. Failed requests are free, so you never pay for errors.
Billing metadata tracks every request for transparency, but input text is not stored or used for training, keeping your data secure and your costs predictable.
- $0.01 per 1,000 characters
- Failed requests are free
- No hidden fees
No subscription
There are no monthly plans, seats, or minimum spend requirements. You top up your balance when needed, and credits never expire. This flexibility supports variable production cycles common in course creation.
We accept USDT (TRC-20) on the TRON network for top-ups. There are no credit cards, PayPal, or invoices. Balances do not expire, allowing you to pause and resume usage without penalty.
- No monthly plans
- No minimum spend
- Credits never expire
Free trial
New accounts signed in with Google receive a $0.50 trial credit, valid for 7 days. This covers approximately 50,000 characters, enough to test multiple voices and formats before committing.
Accounts created with email and password start without this trial credit. You can begin using the API immediately after topping up your balance via USDT transfer.
- $0.50 trial credit for Google sign-ins
- Valid for 7 days
- ~50,000 characters included
Integration with Python
LMS developers can integrate voice synthesis directly into Python workflows using the official OpenAI SDK, simply by redirecting the base URL to our API. This allows you to leverage familiar libraries while accessing our TTS engine without rewriting core logic.
The process is straightforward: send a POST request with your text, voice selection, and desired format. The API returns the audio file immediately, enabling seamless integration into course generation pipelines or LMS media libraries.
OpenAI SDK compatibility
By updating the base_url to https://api.t46.net/v1, you can use the standard OpenAI Python client. This ensures consistent request shapes for models like tts-1 and tts-1-hd, making migration from other providers or standard implementations trivial.
- Use standard OpenAI SDK for Python
- Change
base_urltohttps://api.t46.net/v1 - Supports
tts-1andtts-1-hdmodels
Simple code examples
A basic integration requires passing your API key, the text input, and the selected voice. The SDK handles the JSON serialization and HTTP request, returning the audio content directly to your application for storage or playback.
- Initialize client with
base_url - Pass
inputtext andvoicepreset - Receive audio in
mp3,wav,opus,flac, orpcm
Error handling
Implement standard retry logic for network issues or rate limits. Failed synthesis requests are free, ensuring you only pay for successful audio generation. Check response status codes to handle character limit exceeded errors gracefully.
- Retry on 429 Too Many Requests
- Failed requests incur no charge
- Validate character count (<4096) before sending
Use Cases in EdTech
Text-to-speech APIs transform static course materials into dynamic audio experiences. By programmatically generating speech, edtech startups can replace expensive voice-over workflows with scalable, consistent narration that integrates directly into their Learning Management System.
This approach ensures that learning modules remain accessible and engaging without the logistical overhead of recording studios or managing multiple freelance talent contracts.
Course narration
Generate full course modules from text scripts in seconds. The API handles up to 4096 characters per request, allowing you to split longer lessons into manageable audio segments that play seamlessly in your LMS player.
- Replace manual recording with automated generation
- Maintain consistent tone across all modules
- Scale content production without hiring new talent
Quiz audio
Instantly convert multiple-choice questions and answers into audio format. This reduces production time for assessments, allowing educators to update quiz content dynamically without re-recording voice-overs for every variation.
- Dynamic audio generation for test banks
- Support for rapid content updates
- Consistent voice across question sets
Accessibility features
Provide audio versions of reading materials for diverse learners. With support for 23 languages and adjustable speeds (0.25–4.0), the API helps create inclusive content that meets various accessibility standards without manual intervention.
- Multi-language support for global reach
- Adjustable playback speeds for comprehension
- Inclusive design for varied learning needs
Technical Requirements
To use the LMS Voice Lab API, your server or integration layer requires a stable internet connection. Since audio synthesis is processed in our cloud, local processing power is not a bottleneck. Requests are processed sequentially, so under heavy load, synthesis may queue briefly.
Internet connection
A reliable connection ensures consistent delivery of audio files. While the API handles the heavy lifting of speech generation, your system must remain online to receive the binary audio data or receive error codes if the connection drops during the POST request.
API key authentication
Every request must include your unique API key in the Authorization: Bearer header. You can generate this key on the /get-api-key/ page. The key grants access to your account balance and usage limits. If you suspect a leak, you can issue a new key instantly, invalidating the old one immediately.
- Include key in HTTP header as
Bearer tts-... - One active key per account
- Invalidate old key instantly by issuing a new one
Character limits
Each API request accepts up to 4,096 characters of text. This limit applies to the input field in the JSON body. For longer course scripts, you must split the text into smaller chunks, synthesize each part, and join the resulting audio files programmatically.
Support and Contact
When technical issues arise or you need clarification on integration details, our support team is available via email. We prioritize clear, actionable responses to help you resolve API connectivity or billing questions efficiently.
Unlike platforms with 24/7 live chat windows, we rely on asynchronous communication to ensure every query receives thorough attention from engineers familiar with the TTS engine’s architecture.
Our documentation provides comprehensive guides for Python integration, endpoint specifications, and common error codes, reducing the need for direct contact for standard implementation questions.
Email support
Send your inquiries to [email protected]. We aim to respond within one business day with specific solutions or code adjustments tailored to your LMS setup.
No live chat
We do not offer real-time live chat or phone support. This allows us to maintain focused engineering resources for API reliability and continuous improvement of the speech synthesis engine.
Documentation
The /docs/ page covers all endpoint behaviors, rate limit explanations, and Python SDK examples. It is regularly updated to reflect the latest API specifications and voice model details.
- API endpoint reference
- Python integration examples
- Rate limit guidelines
- Voice model specifications
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. From warm narrators to energetic promotional voices, the selection covers most common eduse scenarios.
23 languages
Any voice speaks any of these languages.
