Integrate Text-to-Speech into Android Applications via API

By VoxApp editorial team · Updated 2026-11-19

VoxApp provides a reliable, cost-effective text-to-speech API engineered for integration into Android applications. Our platform enables indie developers to implement high-quality voice features without managing complex infrastructure. This page details the technical architecture, pricing structure, and integration workflows necessary to deploy synthetic speech within your mobile environment.

You will find specific information on supported voices, audio formats, and rate limits relevant to mobile development. The guide covers authentication, character constraints, and data privacy policies to ensure seamless compliance. Use this resource to understand how VoxApp’s RESTful API delivers consistent audio output for accessibility features, audiobook readers, and interactive voice responses in your Android projects.

Integrate Text-to-Speech into Android Applications via API

Frequently asked questions

Is this a native Android app?

No. This is a cloud text-to-speech API designed for integration into Android applications. You send text via HTTP POST requests and receive an audio file in the response body. It is not a standalone mobile application but an infrastructure component that indie developers implement directly into their apps using standard HTTP libraries.

How do I get the API key?

Sign up on the /get-api-key/ page using Google or an email and password. The page shows the key, balance, trial, characters left, usage and a ready curl example. You can issue a new key at any time; the previous key stops working immediately. One active key is permitted per account.

What is the character limit per request?

The maximum input length is 4096 characters per request. For longer texts, you must split the content into parts of up to 4096 characters and join the resulting audio files. Spaces and punctuation count toward this character limit.

Can I use my own voice?

No. We do not offer custom voice cloning or the ability to upload your own voice recordings. The service provides eight preset voices based on licensed recordings from LibriTTS-R and LibriVox public-domain audiobook readings. You select from these existing options.

Does it support SSML?

No. The API does not support SSML, phoneme dictionaries, or custom pronunciation lexicons. You control pacing and tone by adjusting the speed parameter between 0.25 and 4.0. There are no emotion tags or structural markup options available in the request body.

Is there a streaming option?

No. There is no WebSocket or real-time partial audio streaming. The API processes requests synchronously and returns the complete audio file in the response. You must wait for the full synthesis to complete before receiving the audio data.

What happens if the API fails?

Failed requests are free. If synthesis fails, the charge is returned in full to your account balance. You can retry the request or adjust parameters without incurring additional costs for the failed attempt. This applies to all request types.

How are characters counted?

Characters are counted exactly as provided in the input text, including spaces and punctuation. The cost is $0.01 per 1,000 characters. For example, a 4096-character request costs approximately $0.04. Each character in your string contributes to the total usage.

Can I change my API key?

Yes. You can issue a new API key at any time from your dashboard. When a new key is generated, the old one stops working immediately. This allows you to revoke access instantly without waiting for a manual deactivation process.

Is there a monthly subscription?

No. There are no monthly plans, seats, or minimum spend requirements. You pay only for the characters you consume. Balance does not expire, and you can top up as needed. Pricing is strictly usage-based at $10 per million characters.

Do I need a credit card?

No. We do not accept credit cards, PayPal, or invoices. Top-ups are made using USDT on the TRON network (TRC-20). The minimum top-up amount is $5. Credits are credited automatically within minutes after the blockchain transfer is confirmed.

What languages are supported?

We support 23 languages: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages. Other languages are not supported.

Is the audio quality high?

The audio is generated using licensed recordings from LibriTTS-R and LibriVox. Every file carries an inaudible watermark marking it as synthetic speech. We do not claim to be the best or most realistic, but the output is clear and suitable for app integration.

How long does generation take?

Generation takes roughly real time, averaging 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. The rate limit is 60 requests per minute per key.

First request

curl

curl https://api.ace65.info/v1/audio/speech \
  -H "Authorization: Bearer $TTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"tts-1","voice":"aria","input":"Hello from the API.","response_format":"mp3"}' \
  --output hello.mp3

API Architecture for Mobile Apps

Sound wave illustration for: API Architecture for Mobile Apps

The API accepts standard JSON payloads via POST requests, enabling seamless integration into Android backend services or local processing modules. Each request contains the text input, voice selection, and output format specifications in a structured body.

Developers can leverage existing OpenAI SDKs by updating the base URL, reducing integration overhead. This compatibility ensures that standard HTTP clients and libraries function without custom wrappers.

Standard JSON Request Body

Standard JSON Request Body

Requests are submitted as JSON objects containing the input string (max 4096 characters), model identifier, voice preset, and response_format. The endpoint processes these parameters to generate audio files asynchronously.

The payload structure mirrors industry standards, allowing predictable serialization and deserialization within Android’s networking libraries like OkHttp or Retrofit.

  • Supports text inputs up to 4096 characters per request
  • Fields include model, input, voice, response_format, and optional speed/language

OpenAI SDK Compatibility

By modifying the base_url parameter, the official OpenAI SDKs route requests to our infrastructure. This allows developers to use familiar method signatures without rewriting HTTP logic.

This approach minimizes boilerplate code for Android apps already utilizing standard TTS client patterns.

  • Compatible with official OpenAI SDKs via base_url override
  • Standardized request shape reduces custom implementation effort

Base URL Configuration

Configure the API base URL to https://api.ace65.info/v1 to direct requests to the correct service endpoint. Authentication headers must include the generated Bearer token.

Correct configuration ensures low-latency communication between the Android client and the synthesis engine.

  • Base URL: https://api.ace65.info/v1
  • Requires Bearer token authentication in headers

Voice Selection and Localization

Sound wave illustration for: Voice Selection and Localization

The API provides eight distinct voice presets, categorized by gender and tonal quality, allowing developers to select the optimal audio profile for their application's context. Each voice is derived from licensed recordings, ensuring consistent and high-quality synthetic speech output without the need for manual voice direction.

Localization is handled through support for 23 languages, with any preset voice capable of speaking any of the supported languages. This flexibility allows for consistent branding across different regional markets while maintaining a uniform voice character across the entire application ecosystem.

8 Preset Voice Options

Developers can choose from four female voices: Aria (warm narrator), Nova (upbeat), Luna (soft storyteller), and Sage (calm instructor). The male options include Felix (energetic), Milo (conversational), Atlas (neutral news), and Orion (deep documentary). These presets cover common use cases from audiobooks to interactive voice response systems.

All voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. Each generated audio file includes an inaudible watermark identifying it as synthetic speech, ensuring transparency in audio provenance for compliance and auditing purposes.

  • Aria: warm, clear narrator
  • Nova: bright, upbeat
  • Luna: soft, storytelling
  • Sage: calm, instructional
  • Felix: energetic, promo
  • Milo: friendly, conversational
  • Atlas: neutral, news
  • Orion: deep, documentary

23 Supported Languages

The system supports 23 languages, including Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages, enabling consistent voice branding across diverse linguistic markets.

Languages not in this list, such as Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, and Bengali, are not supported. Developers must verify language requirements before deployment to avoid unexpected audio generation failures or default language behaviors.

Automatic Language Detection

If the language field is not explicitly set in the request, the API attempts to guess the language from the text script. Latin-script text defaults to English if the language is not detected. For non-English Latin-script text, such as German or Spanish, the language parameter should be set explicitly to ensure accurate pronunciation.

Audio Formats and Delivery

Sound wave illustration for: Audio Formats and Delivery

The API supports multiple audio formats to ensure compatibility with various Android media players and storage constraints. Clients can request output in MP3, WAV, Opus, FLAC, or PCM. The response_format parameter in the JSON body determines the encoding of the returned audio file, allowing precise control over file size and quality based on application needs.

MP3 and WAV Support

MP3 provides compressed audio suitable for network transmission, while WAV offers uncompressed lossless quality. Both formats are widely supported by Android’s ExoPlayer and MediaPlayer classes. Selecting the appropriate format balances bandwidth usage against audio fidelity for your specific use case.

Opus and FLAC Options

Opus delivers high-quality audio at low bitrates, ideal for efficient mobile data usage. FLAC provides lossless compression, preserving original audio fidelity while reducing file size compared to WAV. These options are accessible by setting response_format to "opus" or "flac" in the request payload.

PCM Raw Audio Access

PCM (Pulse Code Modulation) returns raw, uncompressed audio data. This format is useful for applications requiring direct processing of audio samples without decoding overhead. The resulting file contains linear pulse-code modulation data, suitable for real-time audio manipulation or specialized playback engines.

Pricing Structure for Developers

Sound wave illustration for: Pricing Structure for Developers

The VoxApp API charges $10 per 1 million characters, equating to $0.01 per 1,000 characters. This flat rate applies to all model variants, with spaces and punctuation counted as characters. Failed synthesis requests incur no cost, ensuring you pay only for successful audio generation.

Per-Character Billing

Billing is straightforward: $10 per 1,000,000 characters ($0.01 per 1,000 characters). This rate applies uniformly across the tts-1 and tts-1-hd models. Every character, including spaces and punctuation, is counted toward your usage total.

  • Rate: $10 / 1,000,000 characters
  • Models: tts-1 and tts-1-hd at identical pricing
  • Inclusions: Spaces and punctuation count as characters

Free Trial Credit

New accounts created via Google sign-in receive $0.50 in trial credit, sufficient for approximately 50,000 characters. This credit is valid for seven days. Accounts established with email and password start without this initial trial balance.

  • Google sign-up: $0.50 credit (~50,000 chars)
  • Validity: 7 days
  • Email/password accounts: No trial credit

Zero Cost for Failures

If a synthesis request fails, the charge is returned in full. You are billed only for successfully processed audio outputs. This ensures accurate cost tracking without penalties for transient API issues.

Rate Limits and Performance

Sound wave illustration for: Rate Limits and Performance

The API enforces a strict rate limit of 60 requests per minute per key. New accounts start with a lower threshold of 10 requests per minute until the first top-up is processed.

60 Requests Per Minute

Each API key is capped at 60 requests per minute. This limit applies uniformly regardless of the account type or tier. Exceeding this threshold will result in immediate rejection of subsequent requests until the window resets.

Processing Queue Behavior

Requests are processed one after another, so under load a request may wait in a queue. Unlike synchronous streaming systems, the API does not return partial audio chunks. Clients must handle the wait time appropriately in their Android background services to avoid timeout errors during peak usage.

  • Sequential processing ensures consistent audio quality.
  • Queue delays increase with concurrent requests.
  • No partial audio stream is returned.

Real-Time Speed Metrics

Generation speed is roughly real time, processing approximately 25 characters of text per second of generated audio. Short phrases may take a few seconds to complete due to initialization overhead. Longer texts are split internally into parts of up to 4096 characters and joined seamlessly.

Rate Limits and Performance

Data Privacy and Usage

Sound wave illustration for: Data Privacy and Usage

We process input text solely to generate the requested audio file. The content you submit is not used for model training or to improve our voice engines, ensuring your app's proprietary content remains distinct from our training data.

No Training Data Usage

Your text is used exclusively for the immediate synthesis of the audio response. Once the file is generated, the input text is not stored for future training purposes, maintaining a clear boundary between your application data and our engine's development.

Synthetic Audio Watermarking

Every audio file produced by our API contains an inaudible watermark. This digital signature explicitly marks the output as synthetic speech, providing transparency regarding the audio's origin without affecting playback quality or file size.

Metadata Retention Policy

We retain request metadata, including timestamp, character count, and status, strictly for billing and usage verification. The generated audio itself is returned in the response and is not stored on our servers after delivery, minimizing long-term data storage.

Technical Requirements

Sound wave illustration for: Technical Requirements

Developers must ensure input text does not exceed 4096 characters per request. Requests exceeding this limit require client-side splitting and subsequent audio file joining to maintain continuity.

Audio playback speed is adjustable between 0.25 and 4.0, allowing precise control over speech rate without altering pitch or quality. This parameter applies to all supported models.

Character Limit Constraints

Each API call accepts a maximum of 4096 characters, including spaces and punctuation. For longer content, implement logic to segment the input text and concatenate the resulting audio segments seamlessly.

Speed Adjustment Parameters

The speed parameter accepts values from 0.25 to 4.0. This allows developers to optimize audio duration for specific use cases, such as rapid information delivery or slower, clearer narration.

Authentication Keys

Access requires a valid API key passed via the Authorization header. Each account maintains one active key; issuing a new key immediately invalidates the previous one, ensuring secure access control for mobile deployments.

Use Cases for Indie Apps

Sound wave illustration for: Use Cases for Indie Apps

VoxApp provides a reliable, cost-effective text-to-speech API engineered for integration into Android applications. Our platform enables indie developers to implement high-quality voice features without managing complex infrastructure.

Audiobook Integration

Indie developers can utilize the 8 preset voices to narrate public domain texts directly within their apps. With support for up to 4096 characters per request, long-form content is processed by splitting and joining audio files seamlessly.

  • Supports 23 languages including English, Spanish, and Japanese for global reach.
  • Low cost of $0.01 per 1,000 characters allows for affordable premium features.

Accessibility Features

Applications can enhance usability by converting static text into synthetic speech for visually impaired users. The API offers diverse voice options, such as the calm Sage for instructional content or the warm Aria for narrative reading.

  • Generates standard audio formats like MP3 and WAV for easy playback.
  • No official SDK of our own; use the OpenAI SDK or plain HTTP.

Interactive Voice Response

Developers can implement dynamic IVR systems that read menu options or confirmations in real-time. With a speed range of 0.25–4.0, the audio can be adjusted to match the pace of user interaction without requiring custom voice design or emotion tags.

  • Handles up to 60 requests per minute for moderate traffic volumes.
  • Automatic language detection simplifies implementation for multilingual user bases.

Integration Workflow

Sound wave illustration for: Integration Workflow

Begin by generating an authentication key via the /get-api-key/ page. Select Google or email registration to establish your account. The system issues a single active key, allowing immediate issuance of a replacement if needed.

Configure your Android client with the base URL https://api.ace65.info/v1. Use the official OpenAI SDK or standard HTTP libraries. Pass the key in the Authorization header to initiate synthesis requests.

API Key Generation

Access the /get-api-key/ page to register. Choose Google sign-in for immediate trial credit or email/password for standard accounts. The dashboard displays your active key, balance, and usage statistics.

  • Single active key per account
  • Instant replacement with immediate old key invalidation
  • Visible balance and character count

Curl Example Execution

Execute a POST request to /v1/audio/speech with a JSON body. Include the model, input text, voice preset, and response format. The API processes the request synchronously.

  • POST https://api.ace65.info/v1/audio/speech
  • JSON body with model, input, voice, format
  • Bearer token authentication

Response Handling

The API returns the audio file directly in the response body. Handle binary data or base64 encoded audio as required by your Android media player. Failed requests return zero charge.

  • Direct audio file response
  • Support for MP3, WAV, OPUS, FLAC, PCM
  • No storage of generated audio

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Understanding these distinctions helps developers select the right tool for their app’s audio needs without over-engineering the solution.

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. MDN: Web Speech API
  3. LibriTTS-R corpus (OpenSLR 141)
  4. openai-python on GitHub
  5. IETF RFC 7845: Ogg Opus
  6. FFmpeg documentation
  7. Python documentation
  8. Node.js documentation
  9. LibriVox public-domain audiobooks
  10. TRON developer hub: TRC-20
  11. W3C WAI: making audio and video accessible
  12. OpenAI API reference: create speech

More on this site