Audexum
Audexum
Text-to-speech REST API with 43 voices and 33 languages.
Supports 43 distinct voices
Check the docs depth and real endpoint shape before assuming production fit.
Obtain an API key to authenticate requests. Use the REST endpoints documented on the website to send text and receive speech audio.
Uptime · 30-day window
About this API
Audexum provides a text-to-speech service accessible via a REST API. It supports a wide variety of voices and languages, making it suitable for applications requiring natural-sounding speech output in multiple languages.
Developers can integrate Audexum to convert written text into spoken audio, enabling use cases such as accessibility tools, audio content generation, and multilingual voice interfaces. The API requires an API key for authentication and offers a straightforward RESTful interface.
With support for 43 voices and 33 languages, Audexum aims to offer flexibility and broad language coverage for diverse user needs. Its simplicity and multilingual capabilities make it relevant for developers looking to add speech synthesis features to their applications.
What you can build
- 1Convert text content to speech audio
- 2Generate multilingual voice outputs
- 3Create audio versions of articles
- 4Build accessibility features with speech
Strengths & limitations
Strengths
- Supports 43 distinct voices
- Covers 33 different languages
- Simple REST API interface
Official quickstart
Read the official quickstart at audexum.com.
Getting started
Obtain an API key to authenticate requests. Use the REST endpoints documented on the website to send text and receive speech audio.
FAQ
Do I need an API key to use Audexum?+
Yes, an API key is required to authenticate all requests.
What protocol does Audexum use?+
Audexum uses a REST API protocol for communication.
Can I convert text to speech in multiple languages?+
Yes, the API supports 33 different languages.
Are there multiple voice options available?+
Yes, there are 43 distinct voices to choose from.
Is HTTPS required to use the API?+
While not explicitly stated, HTTPS is generally recommended for API security.
Technical details
- Auth type
- api_key
- Pricing
- free
- Protocols
- REST
- Response time
- 742 ms
- Last health check
- 5/31/2026, 8:01:35 AM