What is the Free Text to Speech API for Mobile Apps?

By EchoLoom editorial team · Updated 2026-11-18

EchoLoom is a cloud-based text-to-speech API designed for mobile app startups. Instead of managing complex infrastructure, you send JSON requests to our endpoint and receive generated audio files. This service handles voice synthesis, formatting, and billing, allowing your team to focus on user experience rather than server maintenance.

This page explains how our API works, from text input to audio output, and details the technical requirements for integration. We outline the benefits for mobile development, including scalability and cost efficiency, while clarifying what features are included and what is not. Read on to understand how EchoLoom fits into your app’s architecture.

What is the Free Text to Speech API for Mobile Apps?

Frequently asked questions

What is a text to speech API?

It is a cloud service that converts written text into audio files. You send a POST request with your text, and the API returns synthesized speech. This allows mobile apps to generate voiceovers programmatically without managing complex audio infrastructure or hardware.

How does TTS work?

You send text via a JSON POST request to the speech endpoint. The system processes the input using selected voices and formats, then returns the audio file. For long texts, split the input into 4096-character chunks and join the resulting audio files.

Is the API free?

It offers a free trial with $0.50 credit (approx. 50,000 characters) valid for 7 days when signing in with Google. Standard pricing is $10 per million characters. Failed requests are free, and balances do not expire.

Do I need a backend for TTS?

You can call the API directly from your mobile app using the provided SDK or HTTP requests. However, managing API keys securely often requires a backend proxy. The API handles voice generation, formatting, and billing so your team focuses on UX.

Can I use TTS in offline mode?

No, this is a cloud API. You must send text to the endpoint to receive audio. There is no offline SDK or local voice model included. Audio is generated on the server and returned in the response.

What is SSML?

SSML is a markup language for controlling speech synthesis. Our API does not support SSML tags, phoneme dictionaries, or custom pronunciation lexicons. You control speech by adjusting the speed parameter (0.25–4.0) or selecting different voice presets. There is no emotion tagging or manual phoneme adjustment available.

Do I need a voice model?

You select one of eight preset voices (e.g., aria, nova, felix) via the voice parameter. These are based on licensed recordings from LibriTTS-R and LibriVox. You do not need to train or manage custom voice models yourself.

Is the audio copyright-free?

The voices are based on licensed recordings (LibriTTS-R, CC BY 4.0) and public-domain audiobooks. Generated files carry an inaudible watermark marking them as synthetic speech. Input text is not used for training, and generated audio is not stored.

How is quality ensured?

Quality is determined by the selected model (tts-1 or tts-1-hd) and voice preset. The system processes requests sequentially, so load may affect speed. Typical generation is roughly real-time, though short phrases may take a few seconds.

What is a voice preset?

A voice preset is a predefined voice profile, such as aria (warm, clear narrator) or atlas (neutral, news). You select one of eight options via the API. Each voice can speak any of the 23 supported languages.

Can I clone a voice?

No, custom voice cloning is not offered. You cannot upload your own voice or design custom voices. The API provides eight fixed presets based on licensed recordings. You cannot clone real people’s voices or celebrities.

Does the API support emotional tone?

No, there are no emotion tags or controls. Emotion is inherent to the voice preset’s character (e.g., nova is upbeat, sage is calm). You cannot dynamically adjust emotional tone during generation.

Is the API scalable?

Yes, it is a cloud API designed for startups. You can send up to 60 requests per minute per key. For longer texts, split into chunks. There are no monthly plans or seats, allowing flexible usage based on demand.

What is the latency like?

Typical speed is roughly real-time (25 characters per second). Short phrases may take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue. Latency depends on current server load.

Definition

Sound wave illustration for: Definition

EchoLoom is a cloud-based text-to-speech API designed for mobile app startups. It offloads voice synthesis infrastructure, allowing your team to focus on user experience. By sending a simple request, you receive generated audio without managing servers or codecs.

Cloud-Based Service

Unlike local TTS engines that consume device storage and CPU, EchoLoom processes requests on remote servers. This ensures consistent voice quality across all iOS and Android devices without requiring large model downloads or updates on the client side.

JSON API

The service exposes a standard REST endpoint at https://api.playtt39.com/v1. It accepts JSON payloads with fields like model, input, and voice, compatible with the OpenAI SDK structure. This simplicity enables rapid integration into existing backend services or direct frontend calls.

Audio Generation

You send text (up to 4096 characters) and receive an audio file. The system handles voice selection, language detection, and format conversion, returning ready-to-play MP3, WAV, OPUS, FLAC, or PCM directly in the response.

How It Works

Sound wave illustration for: How It Works

The API accepts plain text via a standard JSON body. You send up to 4,096 characters per request, with spaces and punctuation counting toward the limit. For longer content, your mobile app splits the text into segments before sending them sequentially.

Text Input

Send the text payload with your chosen voice and language parameters. The system accepts ISO language codes or auto-detects the script, defaulting to English for Latin text if unspecified.

  • Supports up to 4,096 characters per request
  • Counts spaces and punctuation as characters

Synthesis Process

Requests are processed in a queue. Generation speed is roughly real-time (about 25 characters per second); short phrases take a few seconds. Under load, requests may wait, but failed synthesis returns your full credit.

  • 60 requests per minute limit
  • Real-time processing speed

Audio Output

Receive the audio file directly in the response. Supported formats include MP3, WAV, OPUS, FLAC, and PCM. Each file includes an inaudible watermark marking it as synthetic speech.

  • MP3, WAV, OPUS, FLAC, PCM
  • Includes synthetic speech watermark

Benefits for Mobile Apps

Sound wave illustration for: Benefits for Mobile Apps

EchoLoom’s cloud API handles voice generation, formatting, and billing so your mobile team can focus on user experience. This separation of concerns lets you scale usage without managing infrastructure.

Scalability

The service processes requests sequentially (up to 60 per minute) without requiring you to manage server capacity. Whether you have 10 or 10,000 users, the API handles the load, allowing you to split longer texts into parts seamlessly.

Cost Efficiency

Pay only for what you use at $10 per 1 million characters. Failed requests are free, and there are no monthly plans, seats, or minimum spend. Your balance does not expire, making it ideal for variable mobile app traffic.

Ease of Integration

Use the standard OpenAI SDK by changing the base URL to https://api.playtt39.com/v1. Send JSON and receive audio files in formats like mp3 or opus. This familiar workflow means your developers can integrate speech synthesis quickly without learning new tools.

Technical Requirements

Sound wave illustration for: Technical Requirements

The API requires a stable internet connection to transmit text and receive audio files. Mobile apps must handle network variability gracefully, as synthesis occurs in the cloud rather than on-device.

Authentication is managed via a single active API key, issued upon account creation. This key authorizes requests and tracks usage limits, with the ability to rotate keys instantly if needed.

Internet Connection

A reliable connection is essential for sending requests to https://api.playtt39.com/v1. Since processing happens server-side, offline generation is not supported. Apps should implement retry logic for transient network failures.

  • Supports standard HTTP/2 connections
  • Handles latency variations in mobile networks

API Key

Each account holds one active Bearer key starting with tts-. This key authenticates all requests and is tied to your usage balance. You can generate a new key at any time; the old one stops immediately.

  • Starts with tts-
  • One active key per account
  • Instant revocation on rotation

JSON Format

Requests use standard JSON bodies, compatible with OpenAI SDKs by changing the base URL. You send parameters like model, input, and voice to receive audio files in formats like MP3 or WAV.

  • POST to /v1/audio/speech
  • Standard JSON structure
  • Compatible with existing OpenAI clients

Voice Options

Sound wave illustration for: Voice Options

Multiple Voices

Choose from eight distinct presets to match your app’s tone. Options range from warm narrators and bright upbeat voices to deep documentary styles and neutral news readers. Each voice is generated from licensed recordings, ensuring consistent quality without the need for complex audio engineering.

  • Female: aria, nova, luna, sage
  • Male: felix, milo, atlas, orion

Language Support

The API supports 23 languages, allowing any voice to speak any supported language. If you do not specify a language, the system guesses from the script, defaulting to English for Latin text. For non-English Latin-script inputs, explicitly set the language parameter to ensure accuracy.

  • English, Spanish, French, German, Chinese, Japanese, Korean, Arabic, Hindi, Russian, Portuguese, Italian, Dutch, Swedish, Norwegian, Danish, Finnish, Polish, Turkish, Greek, Hebrew, Malay, Swahili

Voice Customization

Adjust speech speed between 0.25 and 4.0 to fit your app’s pacing. This allows you to create faster notifications or slower, clearer instructions without generating multiple audio files. Note that customization is limited to speed; there is no SSML, emotion tagging, or voice cloning available.

Pricing Models

Sound wave illustration for: Pricing Models

EchoLoom uses a straightforward pay-per-use model with no monthly plans or seats. You pay $10 per million characters ($0.01 per 1,000 characters), with spaces and punctuation counted. Failed requests are free, and your balance never expires.

There are no subscription tiers or hybrid commitments. Startups pay only for what they generate, making it easy to predict costs for mobile app features like notifications or accessibility tools without managing complex billing cycles.

Pay Per Use

The core pricing is $10 per 1 million characters. This applies to all models (tts-1 and tts-1-hd) and formats. You only pay for successful synthesis; failed requests incur no charge.

  • $0.01 per 1,000 characters
  • Spaces and punctuation count
  • Failed requests are free

Subscription

EchoLoom does not offer traditional monthly subscriptions or minimum spend requirements. There are no seats or enterprise contracts to manage. Your account balance remains active indefinitely until you choose to spend it.

Hybrid Models

Since there are no subscriptions, the model is purely usage-based. You can top up with USDT (TRC-20) starting at $5. This allows precise control over cash flow for agile mobile teams.

Pricing Models

Use Cases

Sound wave illustration for: Use Cases

EchoLoom’s API enables mobile apps to generate high-quality speech on demand without managing infrastructure. This is ideal for features requiring instant audio synthesis from user text.

The service handles formatting and billing, allowing your team to focus on user experience rather than audio engineering details.

Notifications

Use the API to convert push notification text into clear audio alerts. This keeps users engaged even when they cannot look at their screen.

With a speed range of 0.25–4.0, you can tailor urgency levels by adjusting playback speed for different notification types.

  • Instant audio generation for alerts
  • Adjustable speed for urgency levels
  • Supports 23 languages for global reach

Audiobooks

Generate audiobook chapters from text inputs up to 4096 characters per request. For longer texts, split and join audio files seamlessly.

Voices like Luna offer a soft, storytelling tone perfect for narrative content, while Atlas provides a neutral news style.

  • Supports up to 4096 characters per request
  • Split and join audio for longer texts
  • Various voices for different narratives

Accessibility

Provide audio alternatives for text content, improving accessibility for visually impaired users. The API supports multiple languages including English, Spanish, and French.

Each generated file carries an inaudible watermark marking it as synthetic speech, ensuring transparency.

  • Supports 23 languages
  • Inaudible watermark for synthetic speech
  • Easy integration for accessibility features

Comparison

Sound wave illustration for: Comparison

Local TTS engines run on-device but lack vocal nuance and require manual updates. Traditional APIs often charge per seat or month, adding overhead for small teams. Human recording is high-quality but expensive and slow to scale.

Vs Local TTS

Local engines save bandwidth but sound robotic and drain battery. Our cloud API delivers richer voices without installing heavy models on every device.

  • No storage overhead on user devices
  • Consistent voice quality across all versions

Vs Traditional APIs

Many competitors lock you into monthly subscriptions with unused credits. We charge $0.01 per 1,000 characters, so you only pay for what you generate.

  • Pay-per-use billing
  • No minimum monthly spend

Vs Human Recording

Hiring voice actors costs hundreds per script and requires studio time. Our API generates audio in seconds at a fraction of the cost.

Integration

Sound wave illustration for: Integration

Integrating EchoLoom into your mobile app is straightforward. You can call the API directly from your frontend or route requests through a lightweight backend service to keep your API key secure. Both approaches leverage standard HTTP methods.

We do not provide a proprietary mobile SDK. Instead, use the official OpenAI SDK by updating the base_url to https://api.playtt39.com/v1. This allows you to use existing SDKs for iOS or Android without learning new libraries.

Mobile SDK

We do not provide a proprietary mobile SDK. Instead, use the official OpenAI SDK by updating the base_url to https://api.playtt39.com/v1.

This approach lets you leverage existing iOS or Android SDKs, reducing integration time and maintaining familiar development workflows for your team.

  • Use official OpenAI SDKs
  • Update base_url to https://api.playtt39.com/v1
  • No custom library required

Backend Service

Route requests through a lightweight backend to keep your API key secure. This method is ideal for apps requiring strict key management or additional preprocessing before synthesis.

The backend handles authentication and forwards the JSON body to our endpoint, ensuring your credentials remain hidden from the end user.

Frontend Direct

Call the API directly from your mobile app for simple use cases. This reduces latency by eliminating the middleman server.

Ensure your API key is stored securely, as it is exposed in the client-side code. Use this method for prototypes or low-volume features.

Security

Sound wave illustration for: Security

EchoLoom secures access via a single active API key per account, issued through your dashboard. You can rotate this key instantly if needed, immediately invalidating the previous one. Requests are authenticated using the standard Authorization: Bearer header, ensuring simple integration with mobile backends or frontend clients.

API Keys

Authentication relies on a Bearer token passed in the request header. Each account holds one active key, which can be regenerated at any time via the /get-api-key/ page. Regeneration instantly stops the old key, providing immediate security control without downtime.

  • Single active key per account
  • Instant invalidation upon regeneration
  • Standard Bearer token authentication

Data Privacy

Input text is used solely for synthesis and is not used to train our models. Generated audio files are returned in the response and are not stored on our servers after delivery. We retain only request metadata—such as timestamp, character count, and status—strictly for billing purposes.

  • Input text not used for training
  • Audio not stored post-delivery
  • Billing metadata retained only

Audio Watermarks

Every generated audio file contains an inaudible watermark identifying it as synthetic speech. This mark is embedded directly into the audio data, allowing downstream applications to distinguish machine-generated voice from human recording without affecting playback quality or user experience.

  • Inaudible synthetic marker
  • Embedded in all outputs
  • Enables source verification

Future Trends

Sound wave illustration for: Future Trends

The text-to-speech landscape is evolving rapidly, driven by the need for more natural and efficient audio generation in mobile applications. As demand grows, providers are focusing on enhancing voice quality and reducing latency to meet user expectations for seamless interactions.

Future developments will likely center on refining existing models to deliver even more human-like speech while keeping costs low. This allows mobile app developers to integrate high-quality audio without significant infrastructure overhead.

AI Improvements

Advances in neural network architectures are enabling more expressive and emotionally resonant speech synthesis. These improvements allow for better intonation and pacing, making synthetic voices sound less robotic and more engaging for end-users.

Enhanced context understanding will enable voices to handle complex sentences more naturally, reducing the need for manual SSML markup or phoneme adjustments.

  • More natural intonation and pacing
  • Better handling of complex sentences
  • Reduced need for manual markup

Cost Reduction

As computational efficiency improves, the cost per character is expected to decrease. This trend makes high-quality TTS more accessible for startups and smaller apps, allowing them to offer rich audio experiences without high operational costs.

Optimized encoding formats and faster generation speeds will further reduce infrastructure expenses, passing savings on to developers.

  • Lower cost per character
  • Faster generation speeds
  • Reduced infrastructure expenses

New Languages

Support for additional languages is a key focus, expanding the reach of TTS-enabled apps globally. This includes less commonly supported languages, providing more options for diverse user bases.

Current support includes 23 languages, with plans to add more to cater to a wider audience, ensuring that mobile apps can communicate effectively with users worldwide.

  • Support for 23 languages
  • Expansion to less common languages
  • Global reach for mobile apps

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. OPUS offers efficient compression for mobile data, while WAV provides uncompressed quality for high-fidelity needs.

Avatar of the voice aria
ariafemale
Avatar of the voice nova
novafemale
Avatar of the voice luna
lunafemale
Avatar of the voice sage
sagefemale
Avatar of the voice felix
felixmale
Avatar of the voice milo
milomale
Avatar of the voice atlas
atlasmale
Avatar of the voice orion
orionmale

23 languages

Any voice speaks any of these languages.

Sources and further reading

  1. Wikipedia
  2. openai-python on GitHub
  3. Creative Commons Attribution 4.0
  4. LibriTTS-R paper (arXiv 2305.18802)
  5. curl documentation
  6. FFmpeg documentation
  7. Python documentation
  8. Tether (USDT)
  9. LibriVox public-domain audiobooks
  10. Node.js documentation
  11. openai-node on GitHub
  12. W3C WAI: making audio and video accessible

More on this site