How to Use Our TTS API for Employee Onboarding Materials?

By LinguaSync editorial team · Updated 2026-11-18

This guide shows HR teams and instructional designers how to convert onboarding documents into professional audio using our TTS API. You will learn to select appropriate voices, structure text for clarity, and integrate MP3 or OPUS files directly into your LMS. By leveraging multilingual support and consistent synthetic voices, you ensure every new hire receives the same clear message, whether they are listening during a commute or reducing screen fatigue at their desk. Note that audio is generated on demand, so there is no real-time streaming.

We cover practical workflows for scaling audio generation across large cohorts without the overhead of studio recording. You will discover how to manage character limits, handle sensitive HR data securely, and troubleshoot common API issues. This page is designed for teams who need reliable, cost-efficient audio content that integrates seamlessly with their existing training materials and compliance updates.

How to Use Our TTS API for Employee Onboarding Materials?

Frequently asked questions

What is the best voice for employee onboarding?

Q: Which voice is best for employee onboarding? A: Sage offers a calm, instructional tone ideal for clear instructions, while Luna provides a soft, storytelling style for engaging narratives. You can choose any of the eight presets based on your content’s mood. Each voice supports all 23 languages, ensuring consistent delivery across diverse teams without needing multiple voice actors.

How do I specify the language for onboarding materials?

Include the optional language field with an ISO code in your request. If omitted, the system guesses the language, defaulting to English for Latin script. For non-English Latin text, always set the language explicitly to ensure accurate pronunciation across the 23 supported languages.

Can I use text-to-speech for compliance training?

Yes, the API handles compliance text effectively. Use Atlas for neutral, news-style delivery or Sage for calm instructions. Input text up to 4096 characters per request. Failed requests are free, ensuring you only pay for successful audio generation of your compliance materials.

How do I handle proper nouns in the text?

The API uses standard pronunciation rules. Since there is no custom pronunciation lexicon, ensure proper nouns are spelled phonetically in your input text. For example, write 'Google' as 'Goo-gul' if needed. Test short phrases to verify accuracy before generating full guides.

Is it better to use MP3 or WAV for LMS?

MP3 is generally preferred for LMS integration due to smaller file sizes and broad compatibility. WAV offers higher quality but larger files. Both are supported alongside Opus, FLAC, and PCM. Choose MP3 for efficient bandwidth usage while maintaining clear audio quality for employees.

How do I split long onboarding guides?

Split text into parts of up to 4096 characters per request. Generate audio for each part separately, then join the audio files. This ensures each request stays within limits. Process requests sequentially, as they are handled one after another, to maintain logical flow.

What is the character limit per request?

Each request accepts up to 4096 characters of input text. Spaces and punctuation count toward this limit. For longer guides, split the text into multiple requests. This ensures consistent processing and allows you to manage audio generation efficiently across different sections of your content.

Can I change the voice after generation?

No, the voice is fixed once the audio is generated. You must regenerate the audio with the desired voice setting. Use the voice parameter in your request to select from the eight presets. This allows flexibility during planning but requires regeneration for changes.

How do I integrate audio with my LMS?

Download the generated audio file from the API response. Upload the file (MP3, WAV, etc.) to your LMS as a standard media asset. Since there is no official SDK, use plain HTTP or the OpenAI SDK with your base URL to fetch the audio for integration.

Is the free trial enough for small onboarding batches?

The free trial provides $0.50 credit, valid for 7 days, covering about 50,000 characters. This is sufficient for small batches or testing. For larger needs, top up with USDT on TRON. The trial is available when signing in with Google, not email/password accounts.

Do I need to pay for each new hire's audio?

You pay for character usage, not per hire. Generate audio once and distribute it to multiple hires. The cost is $0.01 per 1,000 characters. If the audio is reused, you incur no additional fees. Failed requests are also free, ensuring you only pay for usable content.

How do I update audio when policies change?

Regenerate the audio for the updated text section. Split the guide if necessary, update the changed part, and replace the old audio file in your LMS. Since input is not stored, you must resend the text. This ensures employees hear the latest policy information.

What happens if the API is down during onboarding?

There is no SLA or uptime guarantee. If the API is unavailable, requests may fail or queue. Failed requests are free. You can retry later. For critical onboarding, plan for potential delays and have a backup plan, such as pre-generated audio files stored locally.

Why Audio Enhances Onboarding

Sound wave illustration for: Why Audio Enhances Onboarding

Audio transforms static onboarding documents into accessible content that new hires can consume flexibly. By converting text to speech, you enable employees to absorb critical information during their commute, lunch breaks, or while handling other tasks, making learning less rigid and more integrated into their daily routine.

Allows learning during commute or breaks

Listening to onboarding materials allows new hires to utilize otherwise idle time effectively. Whether they are traveling to work or taking a short break, audio ensures that important company information is absorbed without requiring dedicated screen time, keeping engagement high throughout the day.

Reduces screen fatigue for new hires

New employees often face a barrage of emails, videos, and PDFs during their first week. Offering audio options gives their eyes a rest while still delivering the same high-quality educational content, reducing visual strain and helping them retain information more comfortably over longer periods.

Ensures consistent message delivery

Unlike human-led sessions which may vary in tone or detail, our API generates uniform audio for every employee. This guarantees that every new hire hears the exact same pronunciation, pacing, and emphasis on key policies, eliminating variations that can occur when multiple trainers deliver the same material.

Choosing the Right Voice for New Hires

Sound wave illustration for: Choosing the Right Voice for New Hires

Selecting the correct voice sets the tone for your onboarding experience. Our eight presets allow you to match the emotional context of each segment, ensuring new hires feel welcomed rather than just informed. The voices are based on licensed recordings from LibriTTS-R, providing a natural quality without the overhead of studio recording.

Use Milo for friendly, conversational intros

Milo’s friendly, conversational tone is ideal for introductory modules. Use him to explain company culture or welcome new team members, creating a sense of immediate connection. His natural cadence helps reduce the anxiety new hires often feel on their first day.

Use Atlas for neutral company policy updates

For compliance and policy documents, Atlas provides a neutral, news-style delivery. His clear, steady voice ensures that critical information is conveyed without emotional bias, making complex rules easier to digest. This consistency helps maintain clarity across large teams.

Use Aria for warm welcome messages

Aria’s warm, clear narration is perfect for welcome messages and mission statements. Her tone strikes a balance between professional and approachable, helping new employees feel valued. Use her for high-level overviews that set the emotional stage for deeper training content.

Structuring Onboarding Text for Audio

Sound wave illustration for: Structuring Onboarding Text for Audio

To ensure clear pronunciation and natural pacing in onboarding audio, keep your source text concise. Break long, complex sentences into shorter, direct statements. This helps the TTS engine deliver crisp audio without awkward pauses or rushed delivery, which is critical for new hires absorbing new information during their commute or breaks.

Keep sentences short for clear pronunciation

Short sentences reduce cognitive load for listeners. They also allow the API to generate audio with consistent intonation. Avoid nested clauses that might confuse the speech synthesis engine.

  • Use active voice for direct instructions.
  • Avoid nested clauses that might confuse the speech synthesis engine.

Remove formatting codes and special characters

Strip out HTML tags, markdown, and complex symbols before sending text to the API. The engine reads plain text, so remove things like bullet points, bold markers, or special punctuation that don’t translate well to speech. This prevents robotic pauses or mispronunciations of symbols like ‘&’ or ‘@’.

  • Convert ‘&’ to ‘and’.
  • Remove markdown symbols like ** or #.

Split long documents into logical chapters

Since the API accepts up to 4,096 characters per request, divide lengthy onboarding guides into smaller, logical chunks. Process each chapter separately to generate distinct audio files. This makes it easier to manage playback in your LMS and allows new hires to skip sections they already know.

Setting Appropriate Playback Speed

Sound wave illustration for: Setting Appropriate Playback Speed

Adjusting playback speed is essential for optimizing employee onboarding materials. The API supports speeds from 0.25 to 4.0, allowing you to tailor audio pacing to specific content types. This flexibility ensures that new hires can absorb information effectively without fatigue, whether they are listening during a commute or reviewing detailed policies.

Proper speed selection enhances retention and comprehension. By aligning voice speed with content complexity, you create a more engaging learning experience. This approach helps maintain focus and ensures that critical information is delivered clearly without overwhelming the listener.

Default speed works for most content

The default speed provides a natural rhythm suitable for general onboarding content. This setting balances clarity and pacing, making it ideal for introductory materials, company overviews, and standard procedural guides. Most new hires find this speed comfortable for initial listening sessions.

Increase speed for familiar procedural steps

For repetitive or well-understood tasks, increasing the speed to 1.5 or 2.0 can save time. This is particularly useful for routine instructions that new hires already grasp. Faster playback keeps the energy up and reduces the time spent on familiar steps.

  • Ideal for routine tasks
  • Reduces listening time
  • Maintains engagement

Reduce speed for complex compliance details

For complex compliance details, reducing the speed to 0.75 or 0.5 ensures clarity. This allows new hires to process intricate information without missing key points. Slower playback aids in understanding nuanced policies and regulatory requirements.

  • Improves comprehension
  • Aids in processing nuanced information
  • Reduces errors in understanding

Integrating Audio into Your LMS

Sound wave illustration for: Integrating Audio into Your LMS

Integrating audio into your Learning Management System (LMS) transforms static onboarding documents into accessible, engaging content. By converting text to speech, you allow new hires to absorb critical information during commutes or breaks, reducing screen fatigue and ensuring consistent message delivery across all departments.

The API returns standard audio files that integrate with most modern LMS platforms. You can upload these files as media attachments or link them directly to existing course materials, creating a richer learning experience without requiring complex new infrastructure.

Upload MP3 files as attachments or media

MP3 is the most widely supported format for LMS media players. Generate your onboarding audio using the response_format: mp3 parameter and upload the resulting files directly as course resources. This ensures broad compatibility with both desktop and mobile LMS apps.

Most platforms allow you to attach audio files to specific modules or lessons. This approach keeps the audio tied to the relevant learning objective, making it easy for new employees to navigate the material sequentially.

  • Ensure MP3 files are clearly named for easy tracking.
  • Test playback on mobile devices before full deployment.

Link audio tracks to PDF handouts

Many HR teams provide PDF policy documents alongside audio versions. You can hyperlink the text within the PDF to the corresponding audio file URL or uploaded asset. This allows employees to read along while listening, reinforcing retention and accessibility.

This hybrid approach is particularly effective for complex compliance guidelines. New hires can skim the text for key points and listen to the detailed explanation when they have more time, ensuring they grasp the nuances of company policies.

Use OPUS format to save bandwidth

For large onboarding cohorts, file size matters. The OPUS format offers excellent compression while maintaining high audio quality, significantly reducing bandwidth usage and download times for users on slower connections.

Generate audio in OPUS by setting response_format: opus. This is ideal for mobile-first LMS platforms where data usage is a concern, ensuring smooth playback even for lengthy onboarding modules.

Optional: Consider PCM for raw audio needs

If your LMS requires uncompressed audio for specific editing workflows, use the PCM format. It provides raw audio data but results in larger file sizes, so use it only when necessary.

PCM files are larger but lossless, making them suitable for archival purposes or if your platform requires specific audio codecs for playback.

Generating Audio for Multiple Languages

Sound wave illustration for: Generating Audio for Multiple Languages

Audio onboarding ensures consistency across global teams. Use the language parameter to specify ISO codes like de or es, preventing automatic English defaults for Latin-script text. This guarantees accurate pronunciation for non-English content.

Generate separate audio files for each locale to respect local nuances. This approach allows HR to maintain distinct audio assets for different regions without mixing languages in a single track.

Use the language parameter for non-English text

Explicitly setting the language field prevents the API from guessing English for Latin-script texts like German or Spanish. This ensures correct accent and intonation.

The API supports 23 languages, including Arabic, Chinese, French, and Japanese. Always specify the code to avoid misinterpretation of script.

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

Generate separate files for each locale

Create distinct audio files for each language version of your onboarding guide. This keeps your LMS organized and allows hires to select their preferred language track.

Separate files simplify updates. If a policy changes in German, regenerate only that specific file without touching English or Spanish versions.

Ensure correct voice selection per language

Match voices to cultural context. Use Milo for conversational intros or Atlas for neutral policy updates. All 8 voices can speak any of the 23 supported languages.

Verify that your chosen voice sounds natural in the target language. For example, Aria’s warm tone works well for welcome messages in multiple languages.

Testing and Quality Assurance

Sound wave illustration for: Testing and Quality Assurance

Quality assurance ensures your onboarding audio sounds professional and clear before rolling it out to the entire cohort. By testing small segments first, you can catch pronunciation errors or pacing issues early, saving time and character credits on large-scale generations.

Listen to samples before full generation

Generate short audio clips of key sections using the API to verify tone and clarity. This step helps you confirm that the voice matches your company’s culture before committing to longer documents.

  • Test the first paragraph of each onboarding module
  • Verify that the selected voice aligns with the content type

Check pronunciation of proper nouns

Custom names, acronyms, or industry-specific terms may not be pronounced correctly by default. Review these segments manually or adjust the text spelling to guide the TTS engine toward accurate pronunciation.

  • Test names like 'LinguaSync' or 'HR' for clarity
  • Adjust spelling if the voice mispronounces a term

Verify audio clarity on mobile devices

Many new hires will listen on smartphones during their commute. Ensure the audio is clear and not too fast for mobile speakers, adjusting the speed parameter if necessary for better comprehension.

  • Play samples on a smartphone speaker
  • Adjust speed if audio sounds rushed on small devices
Testing and Quality Assurance

Updating Onboarding Content Dynamically

Sound wave illustration for: Updating Onboarding Content Dynamically

Onboarding documents evolve as company policies shift, making static audio files quickly outdated. Regenerating audio ensures new hires always hear the most current information, maintaining consistency across the cohort.

By keeping text files version-controlled, you can track exactly which policy version generated which audio file. This audit trail simplifies compliance reviews and helps you pinpoint exactly when a voiceover needs updating.

Regenerate audio when policies change

When a policy document is updated, simply re-run the TTS API call with the new text. Requests are processed one after another, so under load a request may wait in a queue. Ensure you trigger regeneration only after the previous version is confirmed obsolete.

This approach guarantees that every new hire receives the accurate, latest version of your guidelines without manual intervention or version confusion.

Keep text files version-controlled

Store your source text in a version control system like Git alongside your LMS content. This allows you to correlate specific audio assets with precise text versions, ensuring traceability for HR audits.

It also enables quick rollbacks if a new policy text contains errors, allowing you to revert to the previous stable text and regenerate the audio swiftly.

Automate regeneration via API scripts

Use simple scripts to monitor changes in your text repository and trigger the POST /v1/audio/speech endpoint automatically. This eliminates the need for manual uploads or LMS refreshes when policies update.

Integrate these scripts into your CI/CD pipeline to ensure that any text change results in an updated audio file within minutes, keeping your onboarding materials always fresh.

Managing Character Limits for Long Guides

Sound wave illustration for: Managing Character Limits for Long Guides

Long onboarding guides often exceed the 4,096 character limit per request. By splitting your text into logical blocks, you ensure every section is processed accurately without truncation.

Split content into 4,096 character blocks

Divide your HR documents into segments of up to 4,096 characters. Spaces and punctuation count toward this limit. This ensures consistent audio quality across all parts of your guide.

  • Count characters including spaces and punctuation
  • Split at natural pauses or chapter breaks

Generate audio for each block sequentially

Send each block to the POST /v1/audio/speech endpoint. Process requests one after another; requests are processed sequentially and may wait in a queue under load, but you are limited to 60 requests per minute per key. This prevents queue delays during bulk generation.

  • Use tts-1 or tts-1-hd models
  • Monitor queue status for long texts

Merge files for seamless playback

Combine the resulting audio files into a single track. This allows new hires to listen to the entire guide without manual intervention. Use standard audio tools to join MP3 or WAV files.

Cost-Efficient Scaling for Large Cohorts

Sound wave illustration for: Cost-Efficient Scaling for Large Cohorts

Large onboarding cohorts generate repetitive audio needs. By reusing synthesized files for each new hire, you avoid redundant API calls and reduce overall character consumption.

Store these files on your LMS server to serve them directly to employees, ensuring consistent playback without repeated network requests or additional API costs.

Reuse generated audio files across hires

Generate the audio once and distribute it to all new employees in the same cohort. This approach eliminates duplicate processing for identical onboarding materials, such as welcome messages or standard policy overviews.

Reuse is particularly effective for static content that rarely changes, allowing your team to focus API usage on personalized or updated sections only.

  • Generate once, distribute many times
  • Ideal for static welcome messages
  • Reduces redundant API requests

Cache files on your LMS server

Store the generated MP3 or WAV files directly in your Learning Management System. This removes the dependency on real-time API calls for playback, improving load times and user experience.

Caching also protects against rate limits, ensuring that onboarding proceeds smoothly even if API traffic spikes during peak hiring seasons.

  • Serve audio locally from LMS
  • Improves playback performance
  • Bypasses rate limits for playback

Monitor usage to optimize character spend

Track your character consumption through the dashboard to identify which onboarding modules consume the most credits. Use this data to refine text length or split strategies.

Since each character counts toward your $0.01 per 1,000 characters rate, optimizing text precision directly lowers costs for large-scale deployments.

  • Track character usage per module
  • Optimize text length
  • Align spend with high-value content

Handling Sensitive HR Information

Sound wave illustration for: Handling Sensitive HR Information

When sharing onboarding documents, you often include personal details like home addresses or internal IDs. Our API processes this input strictly for synthesis, ensuring it is not used to train or improve the underlying voice models. This distinction provides an additional layer of data privacy for sensitive HR records.

Once the audio file is generated and returned in the response, it is not stored by our API. This means your generated voiceovers do not linger in our systems, reducing the risk of data retention issues common with third-party TTS providers.

Input text is not used for model training

Your input text is used only to produce the audio and is not used for training.

This ensures that specific employee details or company policies in your text remain isolated from model development.

Generated audio is not stored by the API

Generated audio is returned in the response and not stored.

You maintain full control over where the audio files are saved, whether in your LMS or secure server.

Data is used only for immediate synthesis

Request metadata (time, characters, status) is kept for billing.

All other data is processed for immediate synthesis and cleared from active memory.

Support and Troubleshooting

Sound wave illustration for: Support and Troubleshooting

Support is handled exclusively via email, ensuring your queries are documented and addressed by our team without the noise of live chat. For API-specific issues, please provide your request ID and error logs to help us diagnose the problem quickly.

Contact support via email for API issues

Send details to our support address. We prioritize clarity and resolution over speed, so allow time for a thorough review of your specific case.

Check rate limits if generating bulk content

New keys start with 10 requests per minute, increasing to 60 after a top-up. If you are generating onboarding materials for a large cohort, monitor your queue to avoid delays during peak generation times.

  • Limit: 60 requests/minute per key.
  • Initial limit: 10 requests/minute.
  • No SLA or uptime guarantee.

Verify balance before starting large projects

Ensure your USDT balance is sufficient before initiating bulk audio generation. Failed requests are refunded, but successful synthesis charges are immediate. Check your dashboard to see current usage and remaining characters.

  • Balance does not expire.
  • Minimum top-up: $5.
  • Supported network: TRON (TRC-20).

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. This preset is particularly effective for delivering consistent audio content across large teams and diverse departments.

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. IETF RFC 7845: Ogg Opus
  3. openai-node on GitHub
  4. LibriTTS-R paper (arXiv 2305.18802)
  5. Creative Commons Attribution 4.0
  6. OpenAI API reference: create speech
  7. openai-python on GitHub
  8. Node.js documentation
  9. curl documentation
  10. LibriTTS-R corpus (OpenSLR 141)
  11. Python documentation
  12. TRON developer hub: TRC-20

More on this site