Text to Speech for Newsletters and Email Content
Give subscribers an audio edition of every issue. Paste the URL, get an MP3. Or automate it via the API on each send.
Why it matters.
Subscribers read less but listen more
Newsletter open rates are 30–40%; audio podcast consumption runs closer to 80% episode completion. Adding an audio edition increases total content consumption without requiring you to actually record anything.
Manual recording per issue is not repeatable at scale
Recording a 10-minute audio edition manually takes 30–60 minutes of production time per issue. Automating with the Audexum API reduces that to a single POST request triggered by your email platform's publish webhook.
Paywalled audio needs to stay behind authentication
Generate the MP3 server-side, store it in your protected file store, and serve it via a signed URL. The Audexum API call happens on your server: no subscriber-facing keys, no CORS issues, no external audio player dependency.
The Article-to-Audio tool handles non-technical newsletters
If you use Substack, Beehiiv, or a standard CMS and don't want to write code, paste your article URL into the Article-to-Audio tool. It scrapes the content, renders audio in your chosen voice, and gives you a downloadable MP3 in under 30 seconds.
First audio in 60 seconds.
No SDK. One POST request, binary audio in the response body.
// webhook.js: Express route called by Beehiiv (or any newsletter platform)
// on each new post publication. Generates an MP3 and uploads to S3.
import express from "express";
import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";
const app = express();
app.use(express.json());
const s3 = new S3Client({ region: "eu-central-1" });
app.post("/hooks/newsletter-publish", async (req, res) => {
const { slug, body_text, lang = "en" } = req.body;
// Generate audio edition
const ttsRes = await fetch("https://audexum.com/api/synthesize", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.AUDEXUM_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ text: body_text, voice: "F1", lang, format: "mp3" }),
});
if (!ttsRes.ok) {
return res.status(502).json({ error: await ttsRes.text() });
}
const audioBuffer = Buffer.from(await ttsRes.arrayBuffer());
// Upload to S3, serve via signed URL or CDN
await s3.send(new PutObjectCommand({
Bucket: process.env.AUDIO_BUCKET,
Key: `newsletters/${slug}.mp3`,
Body: audioBuffer,
ContentType: "audio/mpeg",
}));
res.json({ ok: true, key: `newsletters/${slug}.mp3` });
});
app.listen(3000);Full parameter reference: audexum.com/docs. Formats: wav, mp3, ogg. Voices: F1 to F5, M1 to M5 (43 voices total). Languages: 33.
No per-use-case surcharge.
Every plan covers every use case at the same credit rate. Pack credits never expire, and dictation uses the same balance.
Full pricing details- Free
- €0
- 2,000 + 250/day
- Creator
- €12/mo
- 480,000 / mo
- Pro
- €29/mo
- 1,200,000 / mo
- Scale
- €49/mo
- 4,000,000 / mo
- Business
- €149/mo
- 15,000,000 / mo
- Credit packs
- €7
- 250,000, never expire
Questions, answered.
Can I use the Article-to-Audio tool without an API key?
How do I automate audio generation on each newsletter send?
What is the character cost for a typical newsletter issue?
Can I offer audio in multiple languages for a translated newsletter?
Tools and guides for this use case.
Same API, every use case.
One endpoint handles Discord bots, podcast narration, e-learning courses, accessibility audio, and newsletter editions.