> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beyondwords.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Syndication

> Reuse audio across content items and projects to save credits

Syndication lets publishers reuse audio across different projects — such as multiple websites — without generating new audio for each content item. Credits are only consumed when audio is **generated**. A syndicated copy reuses an existing audio file, so you are not charged again for TTS on that item.

<Info>This feature must be enabled by the BeyondWords team. [Contact us](/docs-and-guides/support/get-support) to discuss enabling it for your account.</Info>

## Why use syndication

| Benefit                      | Detail                                                                                                                                             |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Save credits**             | The first content item with a given `source_id` generates audio as usual. Subsequent items in other projects reuse that audio and skip generation. |
| **Consistency**              | The same spoken audio plays across every site or project that syndicates the item.                                                                 |
| **Per-project distribution** | Each project still gets its own content item, so you can use different `source_url`, `metadata`, playlists, and analytics per site.                |

## Example

A publisher runs two websites (separate projects) and publishes the same article on both:

1. **Project A** — [Create content](/api-reference/content/create) with `source_id: "shared-article-001"`. Audio is generated and credits are consumed.
2. **Project B** — Create content with the same `source_id`. A new content item is created, but it references Project A's audio file. No new audio is generated and no additional TTS credits are used.

## How it works

When you POST to [Create content](/api-reference/content/create) with a `source_id`:

1. If no item with that `source_id` exists in your organization, audio is generated as usual.
2. If an item with that `source_id` exists in another project, the existing audio file is reused. A new content item is still created in the target project.

Matching is by `source_id` across projects within your organization.

## Constraints

Syndication trades flexibility for credit savings. Keep these limitations in mind:

* **Feature gate** — Syndication must be enabled on your account before it takes effect.
* **Matching key** — Reuse only happens when the `source_id` matches an existing item in another project. Different IDs always trigger new generation.
* **Locked audio content** — Syndicated copies cannot have different spoken content. Inherited fields cannot be overwritten on the child item (see below).
* **Parent updates** — Changes to the parent item's audio or text flow to syndicated copies. You cannot independently edit title, body, summary, or segments on a child.
* **Project-scoped metadata only** — You can set project-specific values such as `source_url` and `metadata`, but not the core audio-bearing fields.

## Identifying copies

Use `is_copy` in the API response or the [`audio.updated`](/docs-and-guides/integrations/webhooks#audio-updated-payload) webhook payload:

| Value            | Meaning                                                             |
| ---------------- | ------------------------------------------------------------------- |
| `is_copy: false` | Original item that generated the audio. Credits were consumed here. |
| `is_copy: true`  | Child item that reuses existing audio. No TTS credits consumed.     |

## Inherited fields

When audio is reused, these fields are inherited from the parent and **cannot be overwritten** on the child:

* `status`, `title`, `type`, `summary`, `body`, `audio`, `video`, `summarization`, `segments`

You can still set project-specific fields such as `source_url` and `metadata` in the create request.