What is the SynthLogic Text-to-Speech API?

By SynthLogic editorial team · Updated 2026-11-18

This page defines the SynthLogic TTS API, a cloud service that converts text into synthetic audio via HTTP POST requests. We provide a reliable, high-volume solution designed specifically for startups integrating voice into SaaS notifications, interface audio, and automated voice interfaces. You will learn how to structure JSON payloads, select from eight preset voices, and manage billing through per-character usage.

Readers will find details on technical requirements, latency expectations, and data privacy policies. We clarify how the API handles language detection, format options, and rate limits. This guide helps developers understand the integration workflow, from authentication to audio delivery, ensuring predictable performance for automated voice interfaces without the complexity of legacy recording methods.

What is the SynthLogic Text-to-Speech API?

Frequently asked questions

What is the difference between TTS and STT?

Text-to-speech (TTS) converts written text into audio files, whereas speech-to-text (STT) converts spoken audio into written text. SynthLogic provides only a TTS API: you send text and receive an audio file. We do not offer speech-to-text, translation, or dubbing pipelines in our current product suite.

Do I need a backend to use the API?

No. The API accepts standard HTTP POST requests with JSON bodies. You can call the endpoint directly from any environment that supports HTTP, including mobile apps or serverless functions. We do not require a dedicated backend layer, though one may help manage your API key securely.

Can the API generate audio in real-time?

No. The API returns complete audio files after synthesis finishes. It does not support streaming, WebSocket connections, or real-time partial audio delivery. Typical generation speed is roughly real-time for long texts, but short phrases may take a few seconds. Requests are processed sequentially.

Is the audio file stored on your servers?

No. Generated audio is returned directly in the API response and is not stored on our servers. Input text is used only to produce the audio and is not used for training. We retain request metadata, such as time, character count, and status, solely for billing purposes.

How do I choose the right voice?

Select from eight presets based on your use case: Aria for narration, Nova for upbeat content, Luna for storytelling, Sage for instruction, Felix for promos, Milo for conversation, Atlas for news, or Orion for documentaries. You can test voices via the /v1/voices endpoint or the dashboard.

What is the difference between tts-1 and tts-1-hd?

Both models use the same underlying engine and pricing structure. The distinction is purely in the model identifier sent in the request body. There is no difference in price or performance characteristics between tts-1 and tts-1-hd; they use the same engine.

Can I change the speed of the speech?

Yes. The API accepts a speed parameter ranging from 0.25 to 4.0. This allows you to adjust the playback rate of the generated audio to suit your application’s needs, such as speeding up notifications or slowing down instructional content, without re-synthesizing the text.

Does the API support multiple languages?

Yes. We support 23 languages, including English, Spanish, German, French, Japanese, and Arabic. Any voice can speak any supported language. If the language field is omitted, the system guesses the language from the script, defaulting to English for Latin text. Set the language explicitly for non-English Latin scripts.

What is a Bearer token?

A Bearer token is your API key, formatted as tts-..., used to authenticate your requests. You include it in the HTTP header as Authorization: Bearer tts-.... Each account has one active key at a time; issuing a new key immediately invalidates the previous one.

Can I use the API in a mobile app?

Yes. The API is accessible via standard HTTP requests, making it suitable for mobile applications. We do not provide a dedicated mobile SDK, but you can use the official OpenAI SDK by changing the base URL or implement direct HTTP calls using your preferred mobile networking library.

Is the API accessible globally?

Yes. The API is hosted on the cloud and accessible from anywhere with an internet connection. There are no specific data-center choices or regional restrictions. Latency depends on your network connection and the current queue status, as requests are processed sequentially under load.

Do I need to know coding to use it?

Basic coding knowledge is helpful but not strictly required. The API uses standard JSON and HTTP, so you can use tools like cURL or Postman to test it. For production integration, you will need to write code to handle the request, response, and error handling.

What happens if the API goes down?

We do not provide an SLA or uptime guarantee. If the API is unavailable, requests will fail. Failed requests are free, and any charge is returned in full. We do not offer an SLA, so there is no financial compensation for downtime beyond the refund of failed requests.

Can I use the audio commercially?

Yes. The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings. Generated files carry an inaudible watermark indicating synthetic speech. You can use the audio in commercial products, notifications, and interfaces without additional licensing fees beyond the API usage costs.

Definition and Function

Sound wave illustration for: Definition and Function

The SynthLogic TTS API is a cloud service that converts text into audio files via a standard HTTP endpoint. It accepts JSON payloads and returns synthetic speech, enabling automated audio generation for SaaS platforms without manual intervention.

Text Input Processing

Input text is validated against a 4,096-character limit per request. The system processes the string, optionally applying a language code to ensure accurate pronunciation for non-English scripts, before passing it to the synthesis engine.

Synthetic Audio Generation

The API selects a voice model (e.g., Aria, Felix) and applies the specified speed and format settings. The engine generates audio in real-time, producing files that carry an inaudible watermark to identify them as synthetic speech.

Binary Audio Delivery

Once synthesis is complete, the system returns the audio file in the requested format (MP3, WAV, FLAC, OPUS, or PCM). The response contains the binary data directly, allowing immediate playback or storage by the calling application.

API vs Web Interface

Sound wave illustration for: API vs Web Interface

The SynthLogic TTS API operates as a programmatic service rather than a manual web interface. Developers interact directly with the system via standard HTTP endpoints, enabling automated text-to-speech conversion without human intervention in the generation loop.

Programmatic Access

Access is granted through API keys, allowing applications to send text payloads and receive audio files directly. This method supports integration with existing backend systems, ensuring that speech generation becomes a transparent component of the software architecture rather than a manual step.

Automated Workflows

Unlike static web pages where users manually request audio, the API enables continuous, high-volume generation. Systems can trigger speech synthesis automatically based on events, such as sending a notification or updating a user status, without requiring a browser session or user input.

Integration Capabilities

The API uses a JSON request structure compatible with standard OpenAI SDKs, simplifying integration into SaaS products. This compatibility allows developers to leverage existing code libraries for authentication and data handling, reducing the effort required to embed synthetic voice features into their applications.

API vs Web Interface

Use Cases in SaaS

Sound wave illustration for: Use Cases in SaaS

SynthLogic enables automated SaaS notifications by converting system events into audible alerts. This ensures critical updates reach users via voice, enhancing accessibility for mobile or background usage scenarios.

For voice interfaces, the API generates synthetic speech directly from application logic. This allows startups to build interactive voice response systems without managing complex audio libraries or hiring voice talent.

Audio summaries convert long-form text data, such as daily reports or news digests, into concise audio files. Users can consume this information hands-free, improving engagement in productivity and content-driven applications.

Notification Alerts

SynthLogic converts system events into audible alerts. This ensures critical updates reach users via voice, enhancing accessibility for mobile or background usage scenarios without requiring visual attention.

  • Real-time alert generation
  • Background audio playback support

Voice Interfaces

The API generates synthetic speech directly from application logic. This allows startups to build interactive voice response systems without managing complex audio libraries or hiring voice talent for every new feature.

  • Dynamic voice generation
  • Standard SDK integration

Audio Summaries

Convert long-form text data, such as daily reports or news digests, into concise audio files. Users can consume this information hands-free, improving engagement in productivity and content-driven applications.

  • Text-to-audio conversion
  • Hands-free consumption

Technical Requirements

Sound wave illustration for: Technical Requirements

The SynthLogic TTS API requires a standard internet connection to process requests. Each submission triggers a server-side synthesis job, returning binary audio data upon completion. This HTTP-based architecture ensures compatibility with existing SaaS infrastructure without requiring specialized network protocols.

Internet Connectivity

A stable connection is necessary to transmit the JSON payload and receive the audio file. The service operates over standard HTTPS ports, allowing integration within most corporate firewalls without custom port configurations.

JSON Payload Structure

Requests must follow a strict JSON structure containing the model, input text, voice, and optional parameters like response_format and speed. The input text is limited to 4096 characters per request, requiring splitting for longer notifications.

  • Required fields: model, input, voice
  • Optional: response_format, speed, language

HTTP POST Method

All synthesis jobs are initiated via POST requests to /v1/audio/speech. The endpoint accepts JSON bodies and returns audio files directly in the response stream, enabling seamless integration with standard HTTP clients and OpenAI-compatible SDKs.

Voice and Language Selection

Sound wave illustration for: Voice and Language Selection

The SynthLogic API provides eight distinct voice presets categorized by gender and tonal quality, ranging from the warm narration of Aria to the deep documentary style of Orion. Each voice is derived from licensed recordings, ensuring consistent synthetic speech output for your application.

Preset Voice Models

Select from eight specific voices, including female options like Aria and Luna, and male options such as Felix and Atlas. These presets cover a range of tones from upbeat to instructional, allowing you to match the audio output to your specific SaaS interface or notification needs.

Language Code Specification

Support covers 23 languages, including English, Spanish, German, and Japanese. While the system guesses the language for Latin-script text by default, you must explicitly set the language parameter for non-English Latin texts to ensure accurate pronunciation and avoid misinterpretation.

Accent and Tone Variation

Variation is achieved through the selection of different voice presets rather than dynamic accent adjustments. Each voice maintains a consistent character across all supported languages, ensuring predictable audio quality for automated voice interfaces and notifications without requiring manual tone configuration.

Latency and Performance

Sound wave illustration for: Latency and Performance

SynthLogic processes text-to-speech requests sequentially, meaning performance depends on current system load. Understanding these metrics helps SaaS teams estimate end-user experience for interface audio or automated notifications.

Requests are queued and processed one after another. Under heavy load, individual synthesis tasks may experience delays before beginning generation, affecting real-time responsiveness.

Generation Time

Synthesis speed averages roughly real-time, generating approximately 25 characters of text per second of audio. Short phrases typically require a few seconds to complete, while longer texts scale linearly with duration.

Queue Wait Times

Requests are processed sequentially. If the system is under load, a request may wait in a queue before synthesis begins. This introduces variable latency before the audio generation starts, distinct from the generation time itself.

Real-Time Approximation

For extended texts, the total generation time is roughly real-time (about 25 characters of text per second of generation). However, because requests are not parallelized, total throughput is limited by sequential processing, making this suitable for background tasks rather than strict real-time streaming.

Cost Structure

Sound wave illustration for: Cost Structure

SynthLogic charges $0.01 per 1,000 characters, with spaces and punctuation counted toward the total. Failed synthesis requests incur no charge, ensuring you only pay for successful audio generation. This per-character model allows precise cost forecasting for notification systems.

Billing scales linearly with volume. Accounts start with a free trial credit of $0.50 (valid for 7 days) when signing in with Google. Top-ups via USDT (TRC-20) are processed automatically, with no monthly fees or minimum spend requirements.

Per-Character Billing

The rate is fixed at $10 per million characters. Every character in your input text, including spaces, contributes to the usage count. This predictable structure eliminates hidden fees for standard API calls.

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

Volume Scaling

Pricing remains consistent regardless of request volume. There are no tiered discounts or enterprise contracts. You can scale from a few hundred characters to millions without changing the base rate, making it ideal for variable SaaS workloads.

  • No tiered pricing
  • No minimum spend
  • No monthly subscriptions

Trial Credit Usage

Google sign-ins receive $0.50 in trial credit, covering approximately 50,000 characters for 7 days. Email/password accounts start with zero balance. Top-ups via TRC-20 USDT are credited within minutes, allowing immediate production use.

Balance does not expire. You pay only for what you generate, with no recurring costs for the API access itself.

  • $0.50 trial for Google sign-ins
  • 7-day validity
  • TRC-20 USDT top-ups
Cost Structure

Data Privacy

Sound wave illustration for: Data Privacy

SynthLogic processes input text solely for audio synthesis without retaining the source content. Generated audio is delivered via the response stream and is not stored on our servers after delivery.

We retain request metadata—specifically timestamp, character count, and status—for billing verification purposes. This data is not used to train the underlying speech models.

Input Text Retention

Your input text is processed in memory to generate the audio file and is not archived after synthesis. This ensures that sensitive notification content or interface instructions remain transient.

Audio Storage Policy

Synthesized audio is returned directly in the API response and is not stored by SynthLogic. Clients are responsible for storing generated files if needed for their SaaS applications.

Training Data Usage

Input text and generated audio are not used to improve or train the TTS engine. Only request metadata is retained for billing accuracy.

Format Options

Sound wave illustration for: Format Options

The SynthLogic API supports five standard audio formats: mp3, wav, opus, flac, and pcm. Format selection allows developers to balance file size, quality, and compatibility requirements for their specific SaaS infrastructure.

Each format serves distinct technical needs within automated voice interfaces and notification systems, ensuring optimal delivery across various client environments without compromising audio integrity.

MP3 Compression

MP3 is the default and most widely supported format for web delivery. It offers significant file size reduction, making it ideal for mobile notifications and low-bandwidth environments where storage costs matter.

This format maintains sufficient clarity for voice interfaces while minimizing data transfer requirements for high-volume SaaS applications.

  • Default format for most integrations
  • Optimized for web and mobile delivery

WAV Quality

WAV provides uncompressed, high-fidelity audio suitable for professional voice interfaces and archival purposes. It preserves the full spectral content of the synthetic speech without lossy compression artifacts.

Use this format when audio processing pipelines require raw data or when maximum compatibility with legacy systems is necessary.

  • Uncompressed audio data
  • Ideal for professional voice interfaces

FLAC Lossless

FLAC offers lossless compression, reducing file size by approximately 50-60% compared to WAV while retaining 100% of the audio data. This is optimal for archival storage of generated audio assets.

Choose FLAC when you need to preserve perfect audio quality for future re-encoding or analysis without the storage overhead of uncompressed WAV.

  • Lossless compression
  • Best balance of quality and storage efficiency

Integration Complexity

Sound wave illustration for: Integration Complexity

The SynthLogic TTS API is designed for straightforward integration into existing SaaS infrastructure. By mirroring the standard OpenAI request structure, the API allows teams to utilize familiar OpenAI SDKs with a simple base_url configuration change, eliminating the need for custom client libraries or complex protocol adapters.

SDK Compatibility

Integration relies on the official OpenAI SDKs, which work by changing the base URL to https://api.play76d.com/v1. Developers simply point the client to https://api.play76d.com/v1 and supply the tts-... bearer key. This ensures consistent authentication and error handling without requiring proprietary codebases.

  • Compatible with standard OpenAI SDKs
  • Standard Bearer token authentication
  • Supports Python, JavaScript, and Go

Code Example Availability

Ready-to-use curl examples are provided on the /get-api-key/ dashboard, allowing immediate testing without writing initial code. These examples demonstrate the exact JSON payload structure required for POST requests, reducing the trial-and-error phase for new integrations.

Developer Documentation

The /docs/ page outlines the precise request fields, including model, voice, and response_format options. It details the rate limits (60 requests per minute) and character constraints, ensuring developers can configure their applications to handle quotas and errors predictively.

Limitations

Sound wave illustration for: Limitations

The SynthLogic API imposes a strict 4096-character limit per request, requiring applications to split longer texts and concatenate resulting audio files. This constraint ensures consistent processing but demands client-side logic for extended content delivery.

Character Count Limits

Each POST request accepts a maximum of 4096 characters, including spaces and punctuation. Text exceeding this threshold must be segmented by the client application before submission to avoid input errors.

  • Maximum input: 4096 characters per request
  • Spaces and punctuation count toward the limit
  • Long texts require manual segmentation and audio joining

No Streaming Support

The API does not support WebSocket or streaming protocols. Audio is generated entirely server-side and returned as a complete binary file upon completion. Clients must wait for the full response before playback can begin.

  • No real-time partial audio generation
  • Standard HTTP POST response only
  • Full file download required before playback

Fixed Voice Presets

SynthLogic offers eight static voice presets without custom cloning or real-time voice design. Users select from predefined male and female models, which remain constant across all integrations and do not adapt to specific brand guidelines.

  • Eight preset voices (e.g., Aria, Felix, Atlas)
  • No custom voice cloning available
  • Static voice models for all accounts
Limitations

Comparison with Legacy Methods

Sound wave illustration for: Comparison with Legacy Methods

SynthLogic replaces manual audio workflows with an automated API, eliminating the need for separate file uploads and manual synchronization. This shift enables dynamic audio generation directly within SaaS applications, ensuring content updates instantly without reprocessing entire media libraries.

Unlike static audio files stored on servers, the API generates unique audio on demand. This approach scales efficiently with user growth, removing the storage overhead and latency associated with pre-rendered media assets.

Manual Upload vs API

Traditional workflows require uploading pre-recorded audio files, which creates version control issues and storage costs. The SynthLogic API accepts text input and returns audio instantly, integrating directly into application logic without manual media management.

  • Eliminates manual file uploads
  • Removes version control overhead
  • Reduces server storage costs

Static Files vs Dynamic

Static audio files remain unchanged until manually replaced. SynthLogic generates audio dynamically based on current data, allowing real-time updates to notifications and interface audio without deploying new media assets.

  • Real-time content updates
  • No static file caching issues
  • Instant content synchronization

Human Recording vs Synthetic

Human recordings are limited by studio availability and scheduling. Synthetic voices provide consistent quality and immediate availability, enabling scalable voice interfaces for notifications and automated systems without human labor constraints.

  • Consistent voice quality
  • Immediate availability
  • Scalable without labor limits

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Transform your startup's user experience with seamless notifications and intuitive interfaces that keep teams connected and informed.

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. Python documentation
  3. LibriVox public-domain audiobooks
  4. LibriTTS-R corpus (OpenSLR 141)
  5. curl documentation
  6. LibriTTS-R paper (arXiv 2305.18802)
  7. OpenAI API reference: create speech
  8. Node.js documentation
  9. openai-node on GitHub
  10. Tether (USDT)
  11. IETF RFC 7845: Ogg Opus
  12. openai-python on GitHub

More on this site