Syndicated articles

Syndicated articles let publishers reuse audio articles across different projects - such as multiple websites - without needing to generate new audio for each one. If you publish the same article on several sites (each represented as a separate project), you can simply reuse the original audio, ensuring consistency and reducing costs.

​

Example use case

A publisher has multiple websites (each as a separate project) and wants to publish the same article on all of them. Instead of generating new audio for each website, they can reuse the audio article from the first project.

By using the same source_id in both requests:

Project A (Website 1) will generate the audio.

Project B (Website 2) will create a new audio article that reuses Project A’s audio file.

​

How it works

A user submits a POST request with a source_id:

1. If no audio article exists with that source_id, a new audio file is generated.

2. If an audio article with that source_id exists in any of your other projects, the existing audio file is reused.
   
   A new article is still created in the new project, but it references the existing audio file.

​

Identifying duplicates via the API

You can distinguish between original and reused audio articles via the is_copy property that is returned in the response or the audio.updated payload:

is_copy: false → The original (parent) article that generated the audio.

is_copy: true → A duplicated (child) article that reuses the audio.

​

Inherited fields

When creating a new audio article using an existing source_id, certain fields are automatically inherited from the original (parent) article. These fields cannot be overwritten in the new (child) article:

• status
• title
• type
• summary
• body
• audio
• video
• summarization
• segments

Other fields, such as source_url can be modified as needed in the POST request.

This ensures that core audio content remains consistent across projects.