Frequently asked questions
Is this a direct replacement for NaturalReader?
It is an API alternative, not a web interface replacement. You send text via HTTP and receive audio files. Unlike NaturalReader’s consumer app, Lectera provides a simple REST API for developers to integrate directly into your own applications or LMS workflows without using a browser-based player.
Can I use this for educational content?
Yes. The API accepts up to 4096 characters per request, ideal for lesson segments. Audio is returned as standard files like MP3 or WAV. Since input text is not used for training, your course material remains private. You can generate high-quality narration for thousands of students efficiently.
How does pricing compare to NaturalReader?
Lectera charges $10 per million characters, or $0.01 per 1,000 characters. There are no monthly subscriptions or seat fees. You only pay for what you generate. Failed requests are free. This predictable per-character model often costs less than subscription-based alternatives for high-volume educational teams.
Is technical knowledge required?
Basic API knowledge is needed. You use standard HTTP POST requests with a JSON body. If you know how to use the OpenAI SDK, you can integrate immediately by changing the base URL. No complex infrastructure setup is required; just send text and receive audio files.
Can large teams use this simultaneously?
Yes. The API handles concurrent requests, though they are processed sequentially under load. Each team member uses the same API key, limited to 60 requests per minute. For larger teams, you can issue additional keys or manage queueing in your application to handle high-volume generation needs.
Do I need to install software?
No software installation is required. Lectera is a cloud-based API. You interact with it via standard HTTP requests from any device or server. You can use the official OpenAI SDKs or simple cURL commands to generate speech directly from your existing LMS or content management system.
What is the difference between API and web interface?
Lectera provides an API, not a web interface. You programmatically send text and receive audio files. This allows seamless integration into your LMS workflow. Unlike a web app, you do not listen to audio in a browser; you receive the generated audio file directly in the response.
Is the quality comparable to premium services?
Voices are based on licensed recordings from LibriVox, offering clear, natural speech. The engine supports two models: tts-1 and tts-1-hd. The voices are distinct and professional, suitable for educational content, with no artificial emotion tags or SSML complexity.
Can I automate my LMS with this?
Yes. The API is designed for automation. You can script text-to-speech generation for course modules. Since responses are audio files, you can automatically attach them to LMS lessons. The predictable pricing and simple JSON request format make it ideal for batch processing large volumes of course content.
Are there limits on concurrent users?
Limits are on API requests, not users. Each API key allows 60 requests per minute. Multiple team members can share one key, but they must coordinate to stay within the limit. For higher throughput, you can issue new keys, as each account can have one active key at a time.
How do I handle multiple languages?
The API supports 23 languages, including English, Spanish, German, and Japanese. You can specify the language via an optional ISO code in the request. If omitted, the system guesses the language from the script. All 8 voices can speak any of the supported languages with equal quality.
Is the API reliable for bulk jobs?
Yes, but requests are processed sequentially. Long texts should be split into parts of 4096 characters and joined. Speed is roughly real-time. Under load, requests may queue. Failed requests are free, ensuring you only pay for successful audio generation, making it cost-effective for bulk educational content creation.
What if I have a complex workflow?
The API is simple: send text, get audio. It does not support SSML, phoneme dictionaries, or custom pronunciation lexicons. If your workflow requires fine-grained control over pauses or emphasis, you may need to split text manually. The focus is on straightforward, high-volume text-to-speech integration without complex markup.
How do I migrate from another service?
Migration is straightforward if you use the OpenAI SDK. Change the base URL to https://api.play78e.com/v1 and use your Lectera API key. The request shape is identical. You may need to adjust voice names from your previous provider to one of our 8 presets and handle character limits manually.
Understanding Text to Speech APIs
Text-to-Speech (TTS) APIs are cloud-based services that convert written text into audio files via simple HTTP requests. Instead of manual recording, teams send text and receive audio, enabling rapid content production for online courses.
In digital learning, TTS APIs automate the creation of audio versions for course materials, making content accessible and engaging without the logistical burden of studio bookings or voice actor scheduling for every module.
Definition of TTS APIs
A TTS API is a programmatic interface that accepts text input and returns synthesized audio. It abstracts the complex neural network processes into a simple POST request, allowing your LMS or backend systems to generate speech on demand.
This definition focuses on the functional output: text in, audio out. It removes the need for users to understand the underlying AI models, providing a reliable utility for content delivery.
- Cloud-based infrastructure
- Programmatic text-to-audio conversion
- Simple HTTP integration
Role in Digital Learning
For large course teams, TTS APIs transform static text into dynamic audio, supporting diverse learning styles. They enable the creation of multimodal content where students can listen to lessons while commuting or working.
This role is critical for scalability. As course catalogs grow, manual narration becomes a bottleneck. APIs allow teams to produce audio at scale, ensuring consistent voice quality across thousands of modules.
- Multimodal content creation
- Accessibility support
- Scalable content production
Automation Benefits
Automation eliminates the repetitive manual steps of recording, editing, and uploading audio files. By integrating the API into your workflow, you can trigger audio generation directly from your content management system.
This leads to faster time-to-market for new courses. Teams can update text and instantly regenerate audio, ensuring that corrections or improvements are reflected immediately without re-recording entire sections.
The automation also reduces human error and fatigue, maintaining consistent audio quality across all generated content.
- Reduced manual workload
- Faster content updates
- Consistent quality control
NaturalReader vs. Our API
NaturalReader is designed for individual users who need a graphical interface to listen to documents. Our API is built for teams that need to programmatically convert large volumes of course text into audio files via code. This distinction means you can automate your entire LMS workflow without manual steps.
Interface vs. Programmatic Access
While NaturalReader offers a browser-based player for single-file listening, our API provides a standard POST endpoint that accepts text and returns audio files. This programmatic access allows your development team to integrate voice generation directly into your content pipeline, enabling bulk processing that manual interfaces cannot handle efficiently.
- No manual uploads required
- Automated file generation
- Direct LMS integration
Pricing Model Differences
NaturalReader typically relies on monthly subscriptions per user seat. In contrast, we charge strictly per character used, with no monthly fees or seat limits. This model is more cost-effective for large teams where usage varies, ensuring you only pay for the audio actually generated rather than paying for inactive seats.
Integration Complexity
Our API uses the same request shape as major industry standards, making it easy to integrate using existing SDKs. You simply change the base URL and use your API key. This reduces the learning curve for your developers, who can start sending synthesis requests immediately without learning a proprietary system.

Key Features for LMS Teams
For online course teams, converting large volumes of text into audio is a common bottleneck. Our API handles bulk processing by accepting texts up to 4,096 characters per request. You can split longer scripts, generate the audio files, and join them seamlessly, ensuring consistent narration across entire modules without manual intervention.
The standardized request format mirrors the OpenAI speech endpoint, making it easy to integrate into existing LMS workflows. Send a JSON payload with your text, voice selection, and language code, and receive the audio file directly. This predictability reduces integration complexity and speeds up content deployment.
Bulk Processing Capability
Process extensive course materials efficiently by breaking them into 4,096-character chunks. The API returns audio files that you can concatenate, maintaining narrative flow across long lessons or chapters without losing quality or consistency.
- Handle texts up to 4,096 characters per request
- Split and join audio for longer content
- Maintain consistent voice across modules
Standardized Request Format
Use a familiar JSON structure with fields like model, input, voice, and response_format. This standardization allows your developers to use existing HTTP clients or the OpenAI SDK with a simple base URL change, minimizing code adjustments.
- JSON body with standard fields
- Compatible with OpenAI SDKs
- Predictable request structure
Developer-Friendly Design
Designed for developers, the API requires only an API key for authentication. You can test endpoints directly via curl or any HTTP client. The consistent endpoint structure simplifies debugging and allows for quick integration into your LMS automation pipelines.
- Bearer token authentication
- curl examples provided
- No custom SDK required
Voice Quality and Variety
Lectera’s text-to-speech API offers eight distinct voice presets, ensuring your course content sounds professional and engaging. Each voice is designed for specific tones, from warm narration to energetic promos, giving your team precise control over the audio experience without needing complex design tools.
8 Distinct Presets
We provide eight curated voices: Aria, Nova, Luna, and Sage for female tones, plus Felix, Milo, Atlas, and Orion for male voices. These presets cover a range of styles, from clear instructional delivery to deep documentary narration, allowing you to match the audio to your course’s mood.
- 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
Licensing Source
Our voices are built from licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. This foundation ensures high-quality, natural-sounding speech that is legally cleared for commercial use in your educational content.
Audio Consistency
Every generated audio file includes an inaudible watermark marking it as synthetic speech. This ensures transparency and helps maintain consistent branding across your LMS. The API returns audio directly, so you can integrate these files seamlessly into your existing course workflows without worrying about storage or versioning.
Language Support Capabilities
Lectera supports 23 languages, including Arabic, Chinese, English, French, German, Hindi, Japanese, Korean, Spanish, and more. Any voice can speak any of these languages, allowing course teams to produce consistent audio for global learners without managing multiple voice providers. This flexibility simplifies localization for diverse educational markets.
23 Supported Languages
We support Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Each voice handles all supported languages naturally, ensuring consistent quality across your entire curriculum.
Multi-Language Course Content
Generate diverse course materials in multiple languages using the same API endpoint. Whether you are creating Spanish business modules or Japanese technical tutorials, the engine maintains audio quality and pacing standards across all supported tongues without requiring separate integrations.
Detection Accuracy
The API automatically guesses the language from the script if you do not specify one. Latin script defaults to English, so set the language parameter for non-English Latin text to ensure accurate pronunciation. Note that Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, and Bengali are not supported.
Scalability for Large Teams
Scaling your course production doesn't require adding individual licenses. Our API supports unlimited concurrent usage without seat limits, allowing every team member to generate audio independently. This structure removes the friction of managing user quotas, ensuring that large educational teams can operate efficiently as they grow.
No Seat Limits
You pay for character volume, not headcount. Whether your team has five or five hundred educators, the pricing model remains consistent. This eliminates the administrative overhead of monitoring seat usage and allows flexible access for contractors or rotating staff without additional license costs.
High Volume Handling
Each API key supports 60 requests per minute, sufficient for most bulk processing workflows. For texts exceeding 4,000 characters, split the input into smaller parts and join the resulting audio files. This approach ensures reliable delivery even for lengthy course modules or full textbook narrations.
Concurrent Requests
Requests are processed sequentially per key, so under heavy load a request may wait in a queue. This sequential processing guarantees stable performance and predictable costs without sudden infrastructure spikes during peak creation hours, ensuring consistent delivery times for your educational content.

Cost Efficiency for Education
Lectera’s pricing model is built for the variable consumption patterns of educational content. Instead of locking teams into rigid monthly plans, we charge strictly on usage. This approach ensures that large course teams only pay for the audio they actually generate, eliminating waste from unused seats or unused tiers.
Pay Per Character
The cost is fixed at $10 per 1 million characters, which equals just $0.01 per 1,000 characters. Spaces and punctuation count toward this total, providing a precise metric for budgeting. Failed requests are free, so you never pay for errors.
- $0.01 per 1,000 characters
- Spaces and punctuation count
- Failed requests are free
No Subscription Fees
There are no monthly plans, no seat limits, and no minimum spend requirements. You can scale up or down instantly without administrative overhead. Accounts start with a $0.50 free trial for seven days when signing in with Google.
Predictable Budgeting
Top-ups are handled via USDT (TRC-20) with a $5 minimum, credited automatically within minutes. Since balance does not expire, you can purchase volume during budget cycles and use it over time without worrying about subscription renewals or sudden rate hikes.
Technical Integration Steps
Integrating Lectera’s TTS API into your LMS workflow is straightforward, leveraging familiar tools. Because the endpoint mirrors the OpenAI speech API, your existing developer team can adopt it with minimal learning curve. This compatibility means you can use the official OpenAI SDK or simple HTTP requests, ensuring seamless code reuse for audio generation tasks within your course production pipelines.
API Key Setup
Navigate to /get-api-key/ on play78e.com to create your account via Google or email. Your unique API key will be displayed alongside your balance and usage statistics. Store this key securely in your environment variables, passing it via the Authorization: Bearer header in every request. Remember that issuing a new key immediately invalidates the old one, so update your systems promptly if you rotate credentials.
- Sign up via Google or email on the /get-api-key/ page
- Copy the generated Bearer token and store it securely
- Issue a new key anytime; the previous one stops immediately
SDK Configuration
Configure your preferred SDK by setting the base_url to https://api.play78e.com/v1. Pass your API key using the standard authentication header. The request body structure matches the OpenAI speech endpoint exactly, meaning you can use the same Python, JavaScript, or cURL examples provided in our documentation. This consistency allows you to swap in our service without rewriting your core audio generation logic.
- Set base_url to https://api.play78e.com/v1
- Use standard Bearer token authentication
- Match request body to OpenAI speech endpoint format
Testing Workflow
Start with a simple cURL command to verify connectivity and voice selection. Use the tts-1 model for standard quality or tts-1-hd for higher fidelity. Send a short text sample to confirm the audio response format (mp3, wav, opus, flac, or pcm) is correctly received. Once verified, integrate the call into your bulk processing script, ensuring you handle the 60 requests-per-minute rate limit by implementing basic retry logic with exponential backoff for queue waits.
Data Privacy Considerations
Lectera prioritizes data integrity for educational teams. Your input text is processed solely to generate the audio file and is never repurposed for model training. This ensures that proprietary course content remains distinct from our engine's development data.
Text Usage Policy
We do not use your source text to train our voice models. The text exists only for the duration of synthesis and is discarded immediately after the audio response is generated.
Storage Practices
Generated audio files are returned directly in the API response and are not stored on our servers. We retain only request metadata—such as timestamp, character count, and status—for accurate billing and usage monitoring.
Compliance Readiness
Our minimal data retention supports easier compliance with institutional policies. Since we hold no long-term content archives, you retain full control over your educational assets.
- No long-term content storage
- Metadata kept only for billing
- Text not used for training
Support and Resources
Support is available via email for all inquiries, from technical integration questions to billing clarifications. There is no phone line or live chat, so responses depend on email volume.
Documentation is comprehensive and directly accessible through the /docs/ page, providing code examples and endpoint details for seamless developer integration.
Email Support
All support requests are handled exclusively through email. We do not offer phone support or live chat, so please include your API key and account details in your message for faster resolution.
Documentation Access
Full technical documentation is available at /docs/, including endpoint references, SDK examples, and troubleshooting guides. The docs are updated regularly to reflect current API capabilities and pricing structures.
Community Resources
We currently do not maintain public community forums or dedicated user groups. For integration patterns, refer to the code examples in our documentation or contact support via email.

Getting Started Guide
Start by creating an account on play78e.com using Google or email. You will receive a unique API key immediately, granting access to the speech endpoint and a $0.50 trial credit valid for seven days.
Account Creation
Navigate to the /get-api-key/ page to sign up. Your dashboard displays your active key, current balance, and usage statistics, allowing you to manage access for your team without complex infrastructure.
- Sign up via Google or email/password
- Receive a unique Bearer token instantly
- Access $0.50 trial credit (7 days)
- View key and balance on dashboard
First API Call
Send a POST request to https://api.play78e.com/v1/audio/speech with your text and chosen voice. The system processes standard formats like mp3 or wav, returning the audio file directly in the response.
- Use POST /v1/audio/speech endpoint
- Send JSON body with 'input' and 'voice'
- Include 'Authorization: Bearer tts-...' header
- Receive audio file in response
Monitoring Usage
Track your character consumption and balance in real-time. Since pricing is $0.01 per 1,000 characters, you can predict costs accurately. Failed requests are free, ensuring you only pay for successful synthesis.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Our scalable platform streamlines employee onboarding and continuous learning across your entire global workforce.
23 languages
Any voice speaks any of these languages.
