← Blog · 13 July 2026

Offering an audio version of your articles should never become a technical project. If the newsroom has to change its habits, or if integration ties up a developer for weeks, the project stalls before the first episode. That's why WeDispatch offers three distinct integration modes, from simplest to most flexible. This guide describes the concrete steps of each, so you know exactly what to expect before you start.

Which method for which site?

The choice comes down to three questions. Does your site run on WordPress? Take the plugin. Do you have a custom CMS and a technical team? The API gives you full control. Neither, or no developer on hand? RSS-feed discovery requires no code at all.

WordPress plugin: the simplest

Installation follows the classic WordPress plugin path: you install it, then activate it with your licence key. One choice remains — the generation mode.

In automatic mode, audio generates the moment the article is published, with the voice tied to each author. Your journalists change nothing about how they work: they publish, the player appears.

In manual mode, the author keeps control: they choose the voice and trigger generation from the article, before publishing. This mode suits newsrooms that want to hear the result before going live.

API: for custom CMSes

If your publishing chain is developed in-house, integration comes down to one HTTP call at publication time:

```
POST https://wedispatch.fr/api/v1/podcasts
Authorization: Bearer wd_live_...

{ "text": "…", "external_id": "12345", "wait": true }
```

With "wait": true, the response contains the audio URL directly: the article goes live with its player, with no intermediate step. The external_id — your CMS's — guarantees deduplication: sending the same article twice doesn't create two audios. Webhooks and article updates are handled, so you don't have to build that logic yourself. A single hook in your code is enough: where you publish.

RSS feed: zero development

The third path, the lightest: you give us the URL of your RSS feed or sitemap. New articles are detected automatically, the text is extracted, the audio is generated. No change to your CMS, no technical work — it's the option for newsrooms that want to test audio without touching their site.

The player: one line in your template

Whatever the mode, displaying the player is a single line of script to paste into your article template:

``
<script src="https://wedispatch.fr/player.js"
data-article="ARTICLE_ID" defer></script>
``

By default, the player inserts before the first paragraph. To place it elsewhere, add <div data-wedispatch></div> exactly where you want it. Optionally, guided reading shows the text and highlights it word by word along with the audio — a real plus for accessibility, especially for dyslexic or visually impaired readers.

And when an article is corrected?

It's newsroom daily life: a published article is later amended. Send the same id with the corrected text: the live audio keeps being served, and the article goes "to regenerate." You trigger regeneration when the text has settled, and successive corrections are never re-billed. You correct as much as needed, without watching a counter.

Where to start?

The right integration mode is the one that changes nothing about your habits: plugin if you're on WordPress, API if you control your publishing chain, RSS if you want to start with no development. The full technical details — API reference, webhooks, player placement — are in the documentation, and the plans by article volume on the pricing page. WeDispatch is built by the studio Tout est Faisable, which designs custom tools for businesses.

The fastest way to choose is still to see the product running on your own articles: book a demo, and leave with your first audio article.