This feature must be enabled by the BeyondWords team. Please contact us if you’d like to discuss enabling it for your account.
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 samesource_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:-
If no audio article exists with that
source_id
, a new audio file is generated. -
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 theis_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 existingsource_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
source_url
can be modified as needed in the POST
request.
This ensures that core audio content remains consistent across projects.